STRING_LITERAL_LONG_SINGLE_QUOTE, or
STRING_LITERAL_LONG_QUOTE,
and continue to the end of line (marked by
- LF, or
- CR),
+ LFs, or
+ CRs),
or end of file if there is no end of line after the comment marker.
Comments are treated as white space.
@@ -613,7 +618,7 @@ | production | type | procedure |
|---|---|---|
| IRIREF | IRI | The characters between "<" and ">" are taken, after the numeric escape sequences are processed, to form the Unicode string of the IRI. Relative IRI reference resolution is performed per . |
| PNAME_NS | prefix | When used in a prefixID or sparqlPrefix production, the prefix is the potentially empty Unicode string matching the first argument of the rule is a key into the namespaces map. |
| IRIREF | IRI | The characters between < and > are taken, with the numeric escape sequences unescaped, to form the IRI. Relative IRI reference resolution is performed per Section 6.3. The resulting IRI MUST comply with the syntactic restrictions of generic IRI syntax, and SHOULD conform to section 3.3 of [[RFC3986]] and comply with any narrower restrictions imposed by the corresponding IRI scheme specification. |
| PNAME_NS | prefix | When used in a prefixID or sparqlPrefix production, the prefix is the potentially empty RDF string that matches the first argument of the rule. That string serves as a key in the namespaces map; the expanded second argument is stored under that key for future lookup. |
| IRI | When used in a PrefixedName production, the iri is the value in the namespaces map corresponding to the first argument of the rule. | |
| PNAME_LN | IRI | A potentially empty prefix is identified by the first sequence, PNAME_NS. The namespaces map MUST have a corresponding namespace. The Unicode string of the IRI is formed by unescaping the reserved characters in the second argument, PN_LOCAL, and concatenating this onto the namespace. |
| VersionSpecifier | literal | The |curVersion| is taken from a literal using the matched RDF string lexical form and `xsd:string` datatype. |
| PNAME_LN | IRI | A potentially empty prefix is identified by the first sequence, PNAME_NS. The namespaces map MUST have a corresponding namespace. The RDF string of the IRI is formed by unescaping the reserved characters in the second argument, PN_LOCAL, and concatenating this onto the namespace. The resulting IRI MUST comply with the syntactic restrictions of generic IRI syntax, and SHOULD comply with any narrower restrictions imposed by the corresponding IRI scheme specification. |
| VersionSpecifier | literal | The |curVersion| is taken from a literal using the matched RDF string lexical form and `xsd:string` datatype. |
| STRING_LITERAL_SINGLE_QUOTE | lexical form | The characters between the outermost 's are taken, with numeric and string escape sequences unescaped, to form the Unicode string of a lexical form. |
| STRING_LITERAL_QUOTE | lexical form | The characters between the outermost "s are taken, with numeric and string escape sequences unescaped, to form the Unicode string of a lexical form. |
| STRING_LITERAL_LONG_SINGLE_QUOTE | lexical form | The characters between the outermost '''s are taken, with numeric and string escape sequences unescaped, to form the unicode string of a lexical form. |
| STRING_LITERAL_LONG_QUOTE. | lexical form | The characters between the outermost """s are taken, with numeric and string escape sequences unescaped, to form the Unicode string of a lexical form. |
| LANG_DIR | language tag | The characters following the @ form the language tag and optionally the initial text direction, if the matched characters include --. |
| RDFLiteral | literal | The literal has a lexical form of the first rule argument, String. If the '^^' iri rule is matched, the datatype IRI is derived from the iri, and the literal has no language tag. If the LANG_DIR rule is matched, the language tag and initial text direction are taken from LANG_DIR. If there is no initial text direction, the datatype is rdf:langString. If there is an initial text direction, the datatype is rdf:dirLangString. If neither matched, the datatype is xsd:string, and the literal has no language tag. |
| INTEGER | literal | The literal has a lexical form of the input string, and a datatype of xsd:integer. |
| DECIMAL | literal | The literal has a lexical form of the input string, and a datatype of xsd:decimal. |
| DOUBLE | literal | The literal has a lexical form of the input string, and a datatype of xsd:double. |
| BooleanLiteral | literal | The literal has a lexical form of the true or false, depending on which matched the input, and a datatype of xsd:boolean. |
| LANG_DIR | language tag | The characters following the @ form the language tag and optionally the initial text direction, if the matched characters include --. The language tag MUST be well-formed according to section 2.2.9 of [[!BCP47]]. If present, the initial text direction MUST be either `ltr` or `rtl`. |
| RDFLiteral | literal | The literal has a lexical form of the first rule argument, String. If the '^^' iri rule is matched, the datatype IRI is derived from the iri, and the literal has no language tag. If the LANG_DIR rule is matched, the language tag and initial text direction are taken from LANG_DIR. If there is no initial text direction, the datatype is rdf:langString. If there is an initial text direction, the datatype is rdf:dirLangString. If neither matched, the datatype is xsd:string, and the literal has no language tag. |
| INTEGER | literal | The literal has a lexical form of the input string, and a datatype of xsd:integer. |
| DECIMAL | literal | The literal has a lexical form of the input string, and a datatype of xsd:decimal. |
| DOUBLE | literal | The literal has a lexical form of the input string, and a datatype of xsd:double. |
| BooleanLiteral | literal | The literal has a lexical form of the true or false, depending on which matched the input, and a datatype of xsd:boolean. |
| BLANK_NODE_LABEL | blank node | The string matching the second argument, PN_LOCAL, is a key in bnodeLabels. If there is no corresponding blank node in the map, one is allocated. |
| ANON | blank node | A blank node is generated. |
| blankNodePropertyList | blank node | A blank node is generated. Note the rules for blankNodePropertyList in the next section. |
As processors which detect errors on input can result in + graphs which contain fewer triples than are described in the input + (including no triples whatsoever), + consumers should consider information of any errors signaled + when using the output triples, + which may be incomplete and/or include + ill-typed + or ill-formed terms.
+ + + +