- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Thu, 3 Jul 2014 22:53:53 +0200
- To: <public-hydra@w3.org>
On 3 Jul 2014 at 21:25, Gregg Kellogg wrote: > While it would be good to define the range of hydra:manages, and > make sure subject/property/object have that thing in their domain, > in practice, I don't expect serializations to include it, and > clients shouldn't depend on that type being asserted. Good point but I think Ruben is more concerned about the name we use to describe the "manages block" in the specification. Having a good name for that purpose would be very valuable, minting an IRI for that concept is less important, I agree. > Regarding giving it an IRI, vs using a BNode, I think this comes > down to publisher preference. I don't have any problems using a > BNode for such a block. If a publisher wants to give it an IRI, I > have no problem with that. However, a best practice should be that a > Collection serialization include the hydra:manages block inline, > rather than requiring an additional GET. +1 that clearly affects performance and should be properly documented in the spec. -- Markus Lanthaler @markuslanthaler
Received on Thursday, 3 July 2014 20:54:23 UTC