- From: Stian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
- Date: Thu, 16 Apr 2015 11:00:42 +0100
- To: "Wallis,Richard" <Richard.Wallis@oclc.org>
- Cc: "public-schemaorg@w3.org" <public-schemaorg@w3.org>
Thanks for a great blog post! I I agree it could be massaged into the documentation. It is indeed very useful way to do qualified relationships, in a way similar to how we did in PROV-O [1], but with schema roles it is generic, as you simply reuse the same property on both sides. Hence you don't need to specialize schema:Role unless you start building up a set of specific attributes. [1] http://www.w3.org/TR/prov-o/#description-qualified-terms What can be bit confusing is the mixing in of provenance attributes like start/end/rolename which seem very activity-related, and the big overlap with events and actions, e.g. http://schema.org/JoinAction On 15 April 2015 at 18:40, Wallis,Richard <Richard.Wallis@oclc.org> wrote: > The role of Role in Schema.org > > An explanation of this very useful feature that turned into a blog post. > http://dataliberate.com/2015/04/the-role-of-role-in-schema-org/ > > An obvious candidate for the documentation being discussed here recently. > More than happy to copy it in once we have decided what we are doing. > > ~Richard > -- Stian Soiland-Reyes, eScience Lab School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/ http://orcid.org/0000-0001-9842-9718
Received on Thursday, 16 April 2015 10:01:31 UTC