-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support Named Graphs #51
Comments
I am not sure a What about a Your example would be encoded: <rdf:Graph rdf:about="http://inria.fr/graph1">
<rdf:Description rdf:about="http://www.w3.org/TR/rdf-syntax-grammar">
<ex:editor rdf:resource="http://purl.org/net/dajobe/#me" />
<dc:title>RDF 1.2 XML Syntax</dc:title>
</rdf:Description>
</rdf:Graph>
<rdf:Graph rdf:graph="http://inria.fr/graph2">
<rdf:Description rdf:about="http://purl.org/net/dajobe/#me">
<ex:homePage rdf:resource="http://purl.org/net/dajobe/" />
<ex:fullName>Dave Beckett</ex:fullName>
</rdf:Description>
</rdf:Graph>
</rdf:RDF> we might even have anonymous named graphs similar to N3: <rdf:Description rdf:about="http://example.com/alice">
<ex:state>
<rdf:Graph>
<rdf:Description rdf:about="http://example.com/bob">
<ex:eat rdf:resource="http://example.com/apple" />
</rdf:Description>
</rdf:Graph>
</rdf:Description> to encode the TriG:
|
+1 to an alternative having a top-level-only element This style is more like an RDF dataset, less like a graph with annotated triple. While nested |
+1 to the proposed alternative of an |
I also favour the graph element option (which also sets it apart from #52 if we do that). We need to take care not to do it in a way that confuses named graphs in datasets with possible graph terms (which is beyond RDF 1.2). But also doesn't get in the way of such a possible future feature. I think these graph elements should only be allowed either as child elements of |
This issue is to discuss adding minimal support for named graphs in RDF/XML and inspired by the "RDF/XML Source Declaration
W3C Member Submission, 5 September 2007"
One option would be to introduce an
rdf:graph
attribute and, as suggested for other attributes, the propagation rules would be likexml:lang
, with the attribute defining the named graphs of the parsed triples for the descendant elements.Also, as mentioned in other issues, I believe that it would be a good practice (from now own) to encourage the explicit mention of the RDF version as in
rdf:version="1.2"
For instance Example 4 could be adapted as
parsed as N-quads:
The text was updated successfully, but these errors were encountered: