2008
DOI: 10.17487/rfc5147
|View full text |Cite
|
Sign up to set email alerts
|

URI Fragment Identifiers for the text/plain Media Type

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

2012
2012
2023
2023

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 13 publications
(12 citation statements)
references
References 9 publications
0
12
0
Order By: Relevance
“…Similar to application/pdf [RFC3778] and text/plain [RFC5147], this registration permits a parameter syntax for fragment identifiers. The syntax is a parameter name, the equals sign "=" (which MUST NOT be percent-encoded), and a parameter value.…”
Section: Parametersmentioning
confidence: 99%
See 1 more Smart Citation
“…Similar to application/pdf [RFC3778] and text/plain [RFC5147], this registration permits a parameter syntax for fragment identifiers. The syntax is a parameter name, the equals sign "=" (which MUST NOT be percent-encoded), and a parameter value.…”
Section: Parametersmentioning
confidence: 99%
“…The only parameter defined in this registration is "line", which has the same meaning as in [RFC5147], i.e., counting is zero-based. For example: "#line=10" identifies the eleventh line of Markdown input.…”
Section: Parametersmentioning
confidence: 99%
“…Templates can contain any wikitext expansion, HTML rendering instructions and placeholders for arguments. In the example page in Figure 4, the senseid template 32 is used, which does nothing being visible on the rendered page, but adds an id attribute to the HTML li-tag (which is created by using #). If the English Wiktionary community decides to change the layout of senseid definitions at some point in the future , only a single change to the template definition is required.…”
Section: Processing Wiki Syntaxmentioning
confidence: 99%
“…The offset-based URI scheme focuses on ease of implementation and is compatible with the position and range definition of RFC 5147 by [32] (esp. Section 2.1.1) and builds upon it in terms of encoding and counting character positions (See [14] for a discussion).…”
Section: Offset-based Urismentioning
confidence: 99%
“…Offset-based URIs The offset-based URI scheme focuses on ease of implementation and is compatible with the position and range definition of RFC 5147 [6] (esp. Section 2.1.1) and builds upon it in terms of encoding and counting character positions (See Section 4 for a discussion).…”
Section: Nif Uri Schemesmentioning
confidence: 99%