Re: some GRAPHS strawpolls for today (agenda?)

On 25 Apr 2012, at 15:08, Sandro Hawke wrote:
> 1. The default graph is asserted
>  "{<a> <b> <c>}" entails turtle("<a> <b> <c>")


> 2. Named graphs are not asserted
>  "<u> {<a> <b> <c>}" does not entail turtle("<a> <b> <c>")


> 3. Named graphs are opaque
>  "<u> {<a> <b> <c>}"  does not entail "<u> {<a> <b> _:x}"

-1, I think. If you have partial-graph semantics rather than complete-graph semantics, and you want to ascribe truth values to these IRI-graph-pairs, then I don't see any way how the former can be true and the latter false.

> 4. Graph labels denote just like in RDF

I wouldn't put it that way.

>  "{<u1> owl:sameAs <u2>} <u1> {<a> <b> <c>}"
>  owl-entails
>  "<u2> {<a> <b> <c>}"

You're presuming that the owl:sameAs triple is asserted?

+1 to the example anyways.

> 5. Blank nodes labels have file scope
>   See SPARQL queries in 
>   or Skolemization example in

I'm not sure yet how I feel about this.

> 6. In trig, @union can be used in place of the default graph
>   "@union <u> {<a> <b> <c>}" entails turtle "<a> <b> <c>"


> 7. Datasets only say which triples are known to be in a named graph,
>   not which triples are *not* in that named graph.
>   The merge of "<u> {<a> <b> <c>}" and "<u> {<a> <b> <d>}" is 
>   "<u> {<a> <b> <c>,<d>}".  
>   Also "<u> {<a> <b> <c>,<d>}" entails "<u> {<a> <b> <c>}".

A not-very-confident +1. Might still change my opinion.

Received on Wednesday, 25 April 2012 14:40:30 UTC