| Modification dateThis property is a special property in this wiki.
|
13 November 2008 19:15:50 +
|
| Question answer
|
My best guess is that they allow an unname … My best guess is that they allow an unnamed graph in TriX in order to be compatible with the existing RDF standard. If one wanted to convert a graph from RDF/XML representation to TriX, what would one put as the name of the graph (since there is no equivalent in RDF/XML)? I believe the statement "each graph should be named with a URIref" is just a recommendation in order to comply with the named graphs approach presented in the paper (which does not include an unnamed graph). So, in short, unnamed graphs are probably allowed for compatibility with RDF, but they are not recommended so that such a TriX/TriG representation will comply with the named graphs approach. ill comply with the named graphs approach.
|
| Question asked
|
After discussing in section 4.3 SPARQL's u … After discussing in section 4.3 SPARQL's use of a default (unnamed) dataset, and suggesting that such a set "may have the side effect of reintroducing some of the difficulties that named graphs address, section 5.2 identifies the graph element in TriX as having an "optional uri child element which names the graph." Why should this be optional if the authors believe default or unnamed graphs mixed with named graphs causes problems? Similarly, in discussing TriG, section 5.3 says "each graph should be named with a URIref." Is "should" meant to be read as having normative force? If not, why? ad as having normative force? If not, why?
|
| Question asked by
|
Gregory Todd Williams +
|
| Question for the Presentation
|
Jesse Weaver Presents Named Graphs +
|
| Categories |
Presentation Questions
|
