- From: John Walker <john.walker@semaku.com>
- Date: Wed, 7 Oct 2015 23:26:28 +0200 (CEST)
- To: Ruben Verborgh <ruben.verborgh@ugent.be>
- Cc: Hydra <public-hydra@w3.org>, Melvin Carvalho <melvincarvalho@gmail.com>
Hi Ruben > > However there is plenty of interesting stuff in <link> elements. > > Interesting stuff that is not in <body>? Links to stylesheets that define how to present the body :) > > Another point I'd like to raise is the use of quads rather than triples. > > As you are most likely aware there are no agreed formal semantics for RDF > > datasets [1]. > > Yes and that's quite horrible… > anybody knows why the graph IRI is only a syntactical construct? Assume because of the origins in SPARQL whereby it's an internal thing to the store > > Seemed much more logical to make it the name of the graph, > would give the term "named graph" a more logical meaning. +1 > And if you want a graph that has nothing to do with the name, > just pick a different name then anyway. > > > But do you think that using quads would come at the risk of interoperability > > issues? > > Hard to predict, but I don't think so. > > > What would happen if someone did a LOAD operation of one of these quads > > documents into a store? > > Nothing bad, it seems. Do you think of scenarios where things go wrong? One would expect the store would make the request to the resource with Accept header indicating it expects triple-based serialization, so as long as server responds as such, hopefully no issues. Only corner case I can think of is JSON-LD where same MIME type is used for both triples and quads formats, so server could respond with triples or quads (perhaps the profile parameter could be used to express such a preference). It's not at all specified in SPARQL 1.1 what should happen when loading quads into a store. Should all the statements get loaded into the target named graph, or into the graph determined by the graph name in the source document? > > > Would it make sense to state the metadata graph is a subgraph of the main > > graph? > > I wouldn't do that; the main graph is data for me. > > > http://breweryld.semaku.com/beer/8GpObe > > identifies the document (information resource) and URI like > > http://breweryld.semaku.com/beer/8GpObe#id > > identifies the thing described in the document. > > Yes, we certainly need to distinguish. !!!! httpRange-14 alert !!!! ↓↓↓↓ here be dragons ↓↓↓↓ How would you do this for the items in your examples? So if I request the resource </items/10268448>, would you serve the document from this URI? Personally I like the idea to skip that whole discussion and use a Content-location header in the response to give the 'canonical' location for the representation. So </items/10268448.ttl> and </items/10268448.jsonld> for the Turtle and JSON-LD respectively. John
Received on Wednesday, 7 October 2015 21:27:00 UTC