- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Tue, 11 Jun 2013 21:01:41 +0200
- To: "'RDF Working Group'" <public-rdf-wg@w3.org>
> OPTION 1 - (Have People Make Assumptions) Alice puts { <> a
> rdf:BoundDataset } in the default graph. Bob assumes that if that's
> in the default graph, that's probably what's intended, even though the
> specifications license no such assumption.
>
> OPTION 2 - (Simple Bootstrap Semantics) We give some minimalist
> semantics to datasets, saying the default graph of a dataset carries
> the same meaning as an RDF graph. Now Alice puts { <> a
> rdf:BoundDataset } in the default graph and the specs tell Bob that's
> what's intended.
+1
> OPTION 3 - (Type-Only Bootstrap Semantics) We give some tightly-
> minimalist semantics to datasets, saying that triples in the default
> graph of the form { <> a ?x } carry the same meaning as if they were in
> an RDF graph in the same situation. Again, Alice puts { <> a
> rdf:BoundDataset } in the default graph and the specs tell Bob that's
> what's intended. Oddly, unlike with OPTION 2 if she puts in { <>
> cc:license cc:by }, Bob is not licensed by the specs to act on that
> information. If Alice wants to convey a legal license, she'll have to
> also add a triple like { <> a rdf:DefaultIsAssertedDataset } (for some
> suitably defined class).
That would be very very *very* confusing
> OPTION 4 - (Out-of-band Link Header) Alice uses an HTTP Link header
> like this: Link: <http://www.w3.org/1999/02/22-rdf-syntax-
> ns#BoundDataset> rel="http://www.w3.org/1999/02/22-rdf-syntax-ns#type"
How would that information be preserved when the data is put in a quad-store?
> OPTION 5 - (Out-of-band RDF) Alice makes sure that however she gives
> Bob the URL for D, perhaps in some other RDF linking to D, she includes
> the triple { <D> a rdf:BoundDataset }.
Can't really see how that would work in practice, i.e., IMO this is exactly the same as OPTION 1.
--
Markus Lanthaler
@markuslanthaler
Received on Tuesday, 11 June 2013 19:02:12 UTC