Skip to content

Roledependentnames Pattern

Source: ODP portal  ·  Published by: kastle-labl.org  ·  Category: structural  ·  Domain: general

An ontology design pattern for modeling Names as part of Roles, to capture scenarios where an Agent performs different Roles using different Names associated with the different Roles. Examples of an Agent performing a Role using different Names are rather ubiq- uitous, e.g., authors...

What it answers

  • Under which name does someone act when they take on a particular role, such as the name an author publishes under?
  • Given a name, who is behind it and which role were they acting in under that name?
  • Who or what makes a given role available, and under which names is that role held?

The pattern

The graph is the axioms the pattern asserts; nothing here is inferred. Drag to rearrange, scroll to zoom, and use the graph's own search box to find a term inside it.

Opens at level of detail 3: classes, individuals, properties and restrictions, without the literals. Raise it with the LOD control in the graph's own toolbar to see annotation values and anything a reasoner adds.

Download the pattern

Should you use this one?
Size 4 classes, 5 properties, 34 axioms
Brings in nothing - it stands on its own
Reasoning HermiT refuses this pattern rather than answering about it: it falls outside OWL 2 DL, so no DL reasoner can draw conclusions from it. You can still borrow its terms and its shape, but do not expect a reasoner to work with the pattern as published.

A reasoner objects to this pattern: outside OWL 2 DL

HermiT refuses this pattern rather than answering about it: it falls outside OWL 2 DL, so no DL reasoner can draw conclusions from it. You can still borrow its terms and its shape, but do not expect a reasoner to work with the pattern as published.

This is how its authors published it. OntoBoard reports it rather than silently repairing somebody else's pattern. See Choosing a pattern for what to do about it.

Check it yourself: the published pattern  ·  an archived copy  ·  the ontology itself.

If a link does not open

ontologydesignpatterns.org, which publishes most of this library, does not currently answer over HTTPS, and its wiki redirects submission pages to its front page. The archived copy is there for exactly that reason. The ontology files themselves are still served over plain HTTP.

Terms it declares

The 9 classes and properties this pattern models, as the recommender scores them. Annotation properties and built-ins are excluded, because an annotation property is not modelling.

  • https://kastle-labl.org/lod/ontology/Agent
  • https://kastle-labl.org/lod/ontology/AgentRole
  • https://kastle-labl.org/lod/ontology/Name
  • https://kastle-labl.org/lod/ontology/assumesAgentRole
  • https://kastle-labl.org/lod/ontology/hasName
  • https://kastle-labl.org/lod/ontology/hasNameAsString
  • https://kastle-labl.org/lod/ontology/hasRoleUnderName
  • https://kastle-labl.org/lod/ontology/providesAgentRole
  • https://kastle-labl.org/lod/ontology/xsd:string

An example of it in use

The pattern says what may be asserted; this says it. The graph below is a small set of individuals that instantiate the classes above and are connected by its properties, so the shape the pattern describes is visible as data rather than as a schema.

Download the example

Import this pattern into your own ontology from inside Protégé: OntoBoard → Reuse → Pattern library…, which hands it to Import terms… and writes the term list, the module, the import and the catalog entry the way ODK expects. See Working with ODK.

Something wrong with this pattern, its example or this page? Report a problem with this pattern - the form opens with the pattern filled in, and a title and a sentence are all it needs.