…arised as follows: prefix := NCName reference := irelative-ref (as defined in [ RFC3987 ]) curie := [ [ prefix ] ':' ] reference safe_curie := '[' [ [ prefix ] ':' ] reference ']' The production safe_curie is not required, even in situations where an attribute value is permitted …

…e outgoing edge. IRI An Internationalized Resource Identifier as described in [ RFC3987 ]). object A node in a linked data graph with at least one incoming edge. property An edge of the linked data graph literal An object with a label that is not an IRI quad A piece of informatio…

…labeled with an IRI (an Internationalized Resource Identifier as described in [ RFC3987 ]). An object is a node in a linked data graph with at least one incoming edge. An object may be labeled with an IRI or a label that is not an IRI such as plain text, internationalized text, o…

… (URI): Generic Syntax , T. Berners-Lee, R. Fielding, L. Masinter January 2005 [RFC3987] RFC 3987 , "Internationalized Resource Identifiers (IRIs)", M. Dürst , M. Suignard [UNISEC] Unicode Security Considerations , Mark Davis, Michel Suignard [UNICODE] The Unicode Standard, Versi…

… to a Universal Resource Identifier as defined in [ RFC3986 ] and extended in [ RFC3987 ] with the new name IRI. The term URI has been retained in preference to IRI to avoid introducing new names for concepts such as "Base URI" that are defined or referenced across the whole fami…

…and discussed in the Internationalized Resource Identifier (IRI) specification [RFC3987] may need to be modified when this work is completed and standardized. Klensin & Ko Informational [Page 11] RFC 4952 EAI Framework July 2007 6.2. Interaction with Delivery Notifications The ad…

…s are not allowed but ASCII URIs are, this is called out explicitly. [RFC3986] [RFC3987] The term root element , when not qualified to explicitly refer to the document's root element, means the furthest ancestor element node of whatever node is being discussed, or the node itself…

…acters to be used in the IRI character string. IRIs are specified in RFC 3987 [ RFC3987 ]. IRIs can appear in all three positions of a triple. As mentioned, IRIs are used to identify resources such as documents, people, physical objects, and abstract concepts. For example, the IR…

… See Section 7 of [RFC3986] . SPARQL query results uses IRIs. See Section 8 of [RFC3987] . As this media type uses the "+xml" convention, it shares the same security considerations as described in [RFC3023] , section 10. Interoperability considerations: There are no known interop…

…slating between IRIs and the equivalent encoded URI form. IRIs are defined by [ rfc3987 ]. Resource An item of interest that MAY be identified by an IRI . Web Resource A Resource that MUST be identified by an IRI , as described in the Web Architecture [ webarch ]. Web Resources M…

…ned with comparison rules established in current RFCs, including [ RFC3490 ], [ RFC3987 ], and [ RFC4518 ]. * Sections 4.1.2.4 and 4.1.2.6 incorporate the conditions for continued use of legacy text encoding schemes that were specified in [ RFC4630 ]. Where in use by an establish…

…dentifier (URI) [ RFC3986 ] or an Internationalized Resource Identifier (IRI) [ RFC3987 ], from which the domain name is extracted. Alternately, some process not directly involving the user may read the string from a file or obtain it in some other way. Processing in this step an…

…ter string. Terms imported from Internationalized Resource Identifiers (IRIs) [ RFC3987 ] IRI The absolute form of an IRI containing a scheme along with a path and optional query and fragment segments. IRI reference Denotes the common usage of an Internationalized Resource Identi…

…acters to be used in the IRI character string. IRIs are specified in RFC 3987 [ RFC3987 ]. IRIs can appear in all three positions of a triple. As mentioned, IRIs are used to identify resources such as documents, people, physical objects, and abstract concepts. For example, the IR…

…tifiers (IRIs) must be normalized to URIs by the SASL client, as specified in [ RFC3987 ], prior to transmitting them to the SASL server. 6. The SASL client now sends a response consisting of "=" to the server, to indicate that authentication continues via the normal OpenID flow.…