- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Sat, 19 Apr 2014 18:19:22 +0200
- To: "'Gregg Kellogg'" <gregg@greggkellogg.net>, <public-hydra@w3.org>
Hi Gregg, On Sunday, April 13, 2014 12:03 AM, Gregg Kellogg wrote: > I think this has come up before is how to avoid the anti-pattern of defining an inverse > property for each property. For example, schema:Organization has a > schema:subOrganization property, but no subOrganizationOf property [...] > How can I define this as a supported property in Hydra? Perhaps something like the > following: > > :SportsTeam a hydra:Class; > hydra:supportedProperty [ > a hydra:InverseProperty > hydra:property schema:subOrganization > ] . > > hydra:InverseProperty could then be defined to describe the relationship of hydra:property > to be reversed, although this might not hang together if reasoning is involved. Perhaps we > also need a hydra:inverseProperty predicate. Thoughts? I'll send a mail to the list in a minute. That mail includes a proposed solution. Lets further discuss it from there. -- Markus Lanthaler @markuslanthaler
Received on Saturday, 19 April 2014 16:19:51 UTC