Skip to content

matwerkta

Source: NFDI MatWerk  ·  Published by: nfdi.fiz-karlsruhe.de  ·  Category: information  ·  Domain: research-data

An organisational work unit is modelled as an objective specification (obo:IAO_0000005) that is decomposed into work-package textual entities with obo:BFO_0000051 and is the subject of the processes carrying it out via nfdi:NFDI_0000226. The unit is thus represented by what it specifies rather than as an opaque organisational node.

What it answers

  • Which task areas comprise NFDI-MatWerk, and what responsibilities does each hold?
  • Which researchers and organizations participate in a specified task area?
  • What infrastructure use cases and participant projects does a task area encompass?

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 10 classes, 4 properties, 111 axioms
Brings in nothing - it stands on its own
Reasoning HermiT finds this pattern consistent, with no unsatisfiable class, and its worked example consistent with the pattern.

Its IRI is https://ontoboard.org/patterns/nfdi-task-area-objective.owl - a name rather than an address: nothing answers there, so the download link above is the file.

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

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 14 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.

  • http://purl.obolibrary.org/obo/BFO_0000001
  • http://purl.obolibrary.org/obo/BFO_0000002
  • http://purl.obolibrary.org/obo/BFO_0000003
  • http://purl.obolibrary.org/obo/BFO_0000015
  • http://purl.obolibrary.org/obo/BFO_0000031
  • http://purl.obolibrary.org/obo/BFO_0000051
  • http://purl.obolibrary.org/obo/IAO_0000005
  • http://purl.obolibrary.org/obo/IAO_0000030
  • http://purl.obolibrary.org/obo/IAO_0000033
  • http://purl.obolibrary.org/obo/IAO_0000235
  • http://purl.obolibrary.org/obo/IAO_0000300
  • http://purl.obolibrary.org/obo/RO_0000056
  • https://nfdi.fiz-karlsruhe.de/ontology/NFDI_0000226
  • https://nfdi.fiz-karlsruhe.de/ontology/NFDI_0001035

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.