Difference between revisions of "WebSchemas/RolesPattern"

From W3C Wiki
Jump to: navigation, search
m
(added rdfa example)
Line 8: Line 8:
  
 
* [https://www.w3.org/wiki/images/2/22/RolesinSchema.orgMar26.pdf PDF] (Mar 26th draft), also available as a google [https://docs.google.com/document/d/1Cg-LZHHte1dDtkCZEQgo5WOrozzffQK8qLv83PyEZV4/edit?usp=sharing doc].
 
* [https://www.w3.org/wiki/images/2/22/RolesinSchema.orgMar26.pdf PDF] (Mar 26th draft), also available as a google [https://docs.google.com/document/d/1Cg-LZHHte1dDtkCZEQgo5WOrozzffQK8qLv83PyEZV4/edit?usp=sharing doc].
 +
 +
 +
==Examples==
 +
 +
The original design circulated March 26th had a complication: it wanted a role-oriented property linking the Movie to the Role, and also the Person to the Role. To achieve this, local identifiers for the role were used (in JSON-LD syntax). Commentators on the list noted that this introduced new complexities for publishers. However it is hard to represent a complex graph structured without ID-based references. This example shows that it can be done in RDFa 1.1 notation, although this is also complex in a different way:
 +
 +
<syntaxhighlight lang="html4strict">
 +
<div vocab="http://schema.org/" typeof="Movie">
 +
  <span property="name">Ghostbusters</span>
 +
  <div property="hasRole" typeof="MovieRole">
 +
    <span property="characterName">Dr. Peter Venkman</span>
 +
    <div property="actor" rev="inRole" typeof="Person">
 +
      <span property="name">Bill Murray</span>
 +
    </div>
 +
  </div>
 +
</div>
 +
</syntaxhighlight>

Revision as of 14:00, 27 March 2014


This is a WebSchemas proposal RolesPattern for schema.org. See Proposals listing for more. Status: Proposal



This page tracks a proposal from the schema.org team for modeling various kinds of roles and contributions in a way that allows rich qualification. For example, when we say that a Person was an actor in a Movie, we might want to mention their characterName too. When we say that a SportsTeam has a Person as an athlete, we might want to mention the position that they play, or the time period in which they fulfilled that role.

To achieve this, a type "Role" is proposed, alongside a new property, "hasRole".

Full details:

  • PDF (Mar 26th draft), also available as a google doc.


Examples

The original design circulated March 26th had a complication: it wanted a role-oriented property linking the Movie to the Role, and also the Person to the Role. To achieve this, local identifiers for the role were used (in JSON-LD syntax). Commentators on the list noted that this introduced new complexities for publishers. However it is hard to represent a complex graph structured without ID-based references. This example shows that it can be done in RDFa 1.1 notation, although this is also complex in a different way:

<div vocab="http://schema.org/" typeof="Movie">
  <span property="name">Ghostbusters</span>
  <div property="hasRole" typeof="MovieRole">
    <span property="characterName">Dr. Peter Venkman</span>
    <div property="actor" rev="inRole" typeof="Person">
      <span property="name">Bill Murray</span>
    </div>
  </div>
</div>