RoleBehavior values
This is to sharpen up what values we want for RoleBehavior, which is "hard-coded" data for role types. Currently we have:
vf:member a owl:NamedIndividual ,
vf:RoleBehavior ;
rdfs:comment "The role is a member type role in relation to an organization. An agent can be a member of many organizations."@en ;
rdfs:label "member"@en ;
vs:term_status "testing" ;
.
vf:subOrganization a owl:NamedIndividual ,
vf:RoleBehavior ;
rdfs:comment "The role is a sub-organization type role in relation to an organization. An agent can be a sub-organization of no more than one organization."@en ;
rdfs:label "sub-organization"@en ;
vs:term_status "testing" ;
.
vf:peer a owl:NamedIndividual ,
vf:RoleBehavior ;
rdfs:comment "The role is a peer type role in relation to an agent. Examples are trading partners or mentors."@en ;
rdfs:label "peer"@en ;
vs:term_status "unstable" ;
I think member and subOrganization are reasonable to keep and implement, while peer might be too broad. We should consider tradingPartner and try some examples to make sure customer and supplier roles can work well with that. And then look around at previous and in-process projects more systematically to see what they need.