- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Mon, 9 Nov 2015 23:05:02 +0100
- To: John Walker <john.walker@semaku.com>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, Hydra <public-hydra@w3.org>
Hi John,
> All it misses are some triples to link the retrieved resource to
> the items
> in the collection.
>
> <> hydra:member </items/45158567#id> , </items/35235179#id> ,
> </items/10268448#id> .
Yes, but suppose there is then also
</items/45158567#id> :x :y
and even
:y :z :q.
q: :r :s.
Are these part of the data?
And if they are (not), how can I express that?
This example shows that it is hard to put a border around a member.
> Basically seems like you are searching for recommendations/principles for
> publishing RDF data sets on the web.
Not just datasets; mainly hypermedia responses, really (which may contain parts of datasets).
> Unfortunately I think the ship has already sailed here in the
> broader RDF/SPARQL user base
I wouldn't say that–many ships are leaking, and people are looking around ;-)
> - relate a named graph to the containing document using rdfg:subGraphOf property
Yeah; but the problem remains that, strictly speaking
<g> rdfg:subGraphOf <>.
and
<a> <b> <c> <g>.
are talking about different <g>s, according to the RDF 1.1 spec.
So we're still looking for a mechanism to say:
when I name a graph <g>, and use it in subject/object position,
I really mean the same thing.
Best,
Ruben
Received on Monday, 9 November 2015 22:05:34 UTC