- From: Marc Twagirumukiza <marc.twagirumukiza@agfa.com>
- Date: Tue, 10 Jun 2014 15:05:25 +0200
- To: wac@rdas.dk
- Cc: "public-vocabs@w3.org" <public-vocabs@w3.org>
- Message-ID: <OF56B42916.2969D9AD-ONC1257CF3.00445EA8-C1257CF3.0047E88B@agfa.com>
I would take this in broad discussion and hoarmonize with other
predicates/suggested predicates.
Somewhere in medicalEntity proposal we were suggesting having a predicate
like 'playsRole':
<div typeof="rdf:Property" resource="http://schema.org/playsRole">
<span class="h" property="rdfs:label">playsRole</span>
<span property="rdfs:comment">Specifying the role played by an agent
</span>
<span>Domain: <a property="http://schema.org/domainIncludes" href="
http://schema.org/Thing">Thing</a></span>
<span>Range: <a property="http://schema.org/rangeIncludes" href="
http://schema.org/Thing">Thing</a></span>
</div>
Maybe can this be better than 'hasRole/hasRoles'. This is something needed
in several model but I will comment again on this later, ... am still
investigating the new 'Role' proposal to see how it fits there.
Kind Regards,
Marc Twagirumukiza | Agfa HealthCare
Senior Clinical Researcher | HE/Advanced Clinical Applications Research
T +32 3444 8188 | M +32 499 713 300
http://www.agfahealthcare.com
http://blog.agfahealthcare.com
Click on link to read important disclaimer:
http://www.agfahealthcare.com/maildisclaimer
From: "William A. Coolidge" <wac@rdas.dk>
To: "public-vocabs@w3.org" <public-vocabs@w3.org>
Date: 10/06/2014 14:10
Subject: Re: schema.org Roles design
Hi Dan,
I was hoping for a schema for Role that is capable of modeling an entity's
role with a service.
For example, a schema that could handle the various Roles (such as
contributor, guest, etc ) for the users of the service that is behind this
very discussion.
This would be useful for policies on the service that can for example,
automatically reject user actions (such as this post) according to the
policy for the role of the user on the service.
In this scenario, an agent has multiple roles that are likely to be
different for each service.
Thus, my suggestion is to:
consider hasRoles i.e. multiple Roles for each entity
consider examples of Roles associated with services
Regards,
Will Coolidge
Århus Denmark
Received on Tuesday, 10 June 2014 13:06:07 UTC