…ost [ ":" port ] scheme = "stun" / "stuns" <host> and <port> are specified in [ RFC3986 ]. While these two ABNF productions are defined in [ RFC3986 ] as components of the generic hierarchical URI, this does not imply that the "stun" and "stuns" URI Nandakumar, et al. Standards T…

…not include a fragment identifier [ RFC3987 , section 3.1]. IRIs include URIs [ RFC3986 ] and URLs. The abbreviated forms ( relative IRIs and prefixed names ) in the SPARQL syntax are resolved to produce absolute IRIs. The following terms are defined in RDF Concepts and Abstract …

…ost [ ":" port ] scheme = "stun" / "stuns" <host> and <port> are specified in [ RFC3986 ]. While these two ABNF productions are defined in [ RFC3986 ] as components of the generic hierarchical URI, this does not imply that the "stun" and "stuns" URI Nandakumar, et al. Standards T…

…esolved with base IRIs as per Uniform Resource Identifier (URI): Generic Syntax RFC3986 ] using only the basic algorithm in section 5.2. Neither Syntax-Based Normalization nor Scheme-Based Normalization (described in sections 6.2.2 and 6.2.3 of RFC3986) are performed. Characters …

… as a bitmap or a vector drawing, using a URI ("Uniform Resource Identifier") [ RFC3986 ]. In this case, the textual content acts as a fallback for output formats that do not support graphics; thus, it ought to contain either (1) a "line art" variant of the graphics or (2) prose …

…esolved with base IRIs as per Uniform Resource Identifier (URI): Generic Syntax RFC3986 ] using only the basic algorithm in section 5.2. Neither Syntax-Based Normalization nor Scheme-Based Normalization (described in sections 6.2.2 and 6.2.3 of RFC3986) are performed. Characters …

…used, it serves the function described in Section 5.1.1 of URI Generic Syntax [ RFC3986 ], by establishing the base URI (or IRI, Internationalized Resource Identifier [ RFC3987 ]) for resolving relative references found within the scope of the "xml:base" attribute. Any element de…

…used, it serves the function described in Section 5.1.1 of URI Generic Syntax [ RFC3986 ], by establishing the base URI (or IRI, Internationalized Resource Identifier [ RFC3987 ]) for resolving relative references found within the scope of the "xml:base" attribute. Any element de…

…timestamp-list / boolean / integer-list / float-list / URI ; from Section 3 of [RFC3986] / iana-valuespec ; Actual value type depends on property name and VALUE parameter. text = *TEXT-CHAR TEXT-CHAR = "\\" / "\," / "\n" / <any VALUE-CHAR except , or \> ; Backslashes, commas, and…

…not include a fragment identifier [ RFC3987 , section 3.1]. IRIs include URIs [ RFC3986 ] and URLs. The abbreviated forms ( relative IRIs and prefixed names ) in the SPARQL syntax are resolved to produce absolute IRIs. The following terms are defined in RDF Concepts and Abstract …

…not include a fragment identifier [ RFC3987 , section 3.1]. IRIs include URIs [ RFC3986 ] and URLs. The abbreviated forms ( relative IRIs and prefixed names ) in the SPARQL syntax are resolved to produce absolute IRIs. The following terms are defined in RDF Concepts and Abstract …

…e of the fields may contain URIs using percent-encoding (as per Section 2.1 of [RFC3986]). 2.1. Comments Any line beginning with the "#" (%x23) symbol MUST be interpreted as a comment. The content of the comment may contain any ASCII or Unicode characters in the %x21-7E and %x80-…

…Protocol Negotiation (ALPN) protocol name, as per [ RFC7301 ] o A host, as per [RFC3986], Section 3.2.2 o A port, as per [RFC3986], Section 3.2.3 The ALPN protocol name is used to identify the application protocol or suite of protocols used by the alternative service. Note that f…

…D provides metadata for different Protocol Bindings identified by URI schemes [ RFC3986 ] (e.g., http , coap , etc. [ IANA-URI-SCHEMES ]), content types based on media types [ RFC2046 ] (e.g., application/json , application/xml , application/cbor , application/exi , etc. [ IANA-M…

…ization 1.0 Informational All of these documents and recommendations use URIs [ RFC3986 ] to identify algorithms and keying information types. The W3C has subsequently produced updated XML Signature 1.1 [ XMLDSIG11 ], Canonical XML 1.1 [ CANON11 ], and XML Encryption 1.1 [ XMLENC…