WIP: Support for rdf:dirLangString. #54
Conversation
|
@gkellogg why the rdf:dirLangString section is non-normative? |
Those sections are all explanatory. Normative behavior is defined in the events and processing rules. |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
gkellogg
force-pushed
the
dirLangString
branch
from
945d0aa to
e0b0a44
Compare
| class="termref"><span | ||
| class="arrow">·</span>literal-direction<span | ||
| class="arrow">·</span></a> is the empty string, | ||
| the value is the concatenation of """ (1 double quote), |
There was a problem hiding this comment.
""" (1 double quote) gets rendered as """ (1 double quote). There are a number of possible ways to better present this (which should be applied to all similar instances). Probably the simplest would be <code>"</code> (one double-quote).
There was a problem hiding this comment.
I'm not happy with this general way of emitting triples (see #55), and more could be done on character presentation, similar to how it's done in Turtle. This just adapts the existing pattern; I think another pass is needed separately to clean up these things. Just changing one of them because it happened to be touched by this PR doesn't really address the problem.
Co-authored-by: Ted Thibodeau Jr <[email protected]>
| @@ -162,18 +166,18 @@ <h3>Introduction</h3> | |||
| and attribute values. | |||
| RDF/XML uses XML <a data-cite="XML-NAMES#NT-QName">QNames</a> | |||
| as defined in Namespaces in XML [[XML-NAMES]] to represent IRIs. | |||
| All QNames have a <a data-cite="XML-NAMES#dt-NSName">namespace name</a> which is an IRI | |||
| All QNames have a <dfn data-cite="XML-NAMES#dt-NSName">namespace name</dfn> which is an IRI | |||
| and a short | |||
| <a data-cite="XML-NAMES#NT-LocalPart">local name</a>. | |||
| In addition, QNames can either have a short | |||
| <a data-cite="XML-NAMES#NT-Prefix">prefix</a> | |||
| or be declared with the default namespace declaration and have none (but | |||
There was a problem hiding this comment.
Minor suggestion:
| or be declared with the default namespace declaration and have none (but | |
| or be declared with the default namespace declaration and have no prefix (but |
| @@ -1140,7 +1199,10 @@ <h2>RDF/XML Internet Media Type, File Extension, and Macintosh File Type</h2> | |||
| systems be given a file type of <code>"rdf "</code> | |||
| (all lowercase, with a space character as the fourth letter).</p> | |||
|
|
|||
| <p>The `application/rdf+xml` media type has been registered at IANA as [[RFC3870]].</p> | |||
| <p>Features introduced in RDF 1.2 require a version announcement in the | |||
There was a problem hiding this comment.
That's an independent decision?
I think "required" is a burden because to stream the whole data must be seen. Therefore, I think the version should be optional.
The majority of RDF 1.2 data will be legal RDF 1.1 .
| @@ -1867,9 +1980,12 @@ <h3>Plain Literal Event</h3> | |||
|
|
|||
| <p class="note">RDF/XML plain literals are in RDF 1.2 treated as | |||
There was a problem hiding this comment.
"plain literals" went away with RDF 1.1.
We can define "plain literal" for the purposes of RDF/XML as "no given rdf:datatype".
It does not have to be a full <dfn>.
Digression 😀
It may be useful to define "string literal" in RDF Concepts with alt "RDF string literal".
SPARQL has one because the grouping of xsd:string, rdf:langString and now rdf:dirLangString comes up repeated.
Still a Work in Progress, more work needed on the event definitions.
Fixes #50.
Preview | Diff