- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Mon, 31 Mar 2014 17:02:04 +0200
- To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, Pat Hayes <phayes@ihmc.us>, public-hydra@w3.org, public-lod@w3.org, W3C Web Schemas Task Force <public-vocabs@w3.org>, Dan Brickley <danbri@danbri.org>
Hi Peter,
> I don't see how this solves the problem.
Recall that �the problem� for Hydra clients is (in my opinion):
1. Having a way to find out the members of a specific collection
2. Not breaking the RDF model while doing so
> what you are saying is thatMarkus knows some entity, and that that entity belongs to the set.
�and I give that set a URL, too.
> It does not say which of the members of the set are friends of Markus, nor that any more than one of them has to be
�on purpose, since it is not needed at all to solve 1 and 2.
</people/markus> foaf:knows [ hydra:memberOf </people/markus/friends> ].
Gives you the URL of the set, which allows you to retrieve it.
Then if you retrieve it, it will list its members and say they are friends of Markus:
</people/markus> foaf:knows </people/Anna>.
</people/markus> foaf:knows </people/Bert>.
</people/markus> foaf:knows </people/Carl>.
This is exactly the reason I propose this approach;
I know many people want more semantics in there;
and that's totally fine and even possible with this approach
(like I said, you can further describe /people/markus/friends if you like.)
But all we need for Hydra clients is a way to get Markus' friends.
This solution offers it. No more semantics needed.
Best,
Ruben
Received on Monday, 31 March 2014 15:02:44 UTC