The ontology Metadata4Ing provides a framework for the semantic description of research data and of the whole data generation process, embracing the object of investigation, all sample and data manipulation methods and tools, the data files themselves, and the roles of persons and institutions. The structure and application of the ontology are based on the principles of modularity and inheritance.
The ontology Metadata4Ing provides a generic framework for a complete semantic description of a process for the generation of scientific data, with a particular focus on engineering sciences and neighbouring disciplines. It covers the description of the object of investigation; all sample and data manipulation procedures (generation, selection, analysis, combination); a summary of the data files and the information contained; the connection to involved persons and institutions (with specific roles) and to other related objects like projects and publications.
The ontology Metadata4Ing is developed by the homonymous workgroup (special interest subgroup) of the NFDI Consortium for Engineering Sciences (NFDI4Ing) and it evolves continuously thanks to a fruitful exchange with different potential user groups, including the archetypes of the same consortium.
The ontology Metadata4Ing is a collection of terms (classes and properties) which can be used to enrich a research data set with semantic and machine-readable metadata, in order to annotate it or to integrate it in a database or a larger knowledge graph. The metadata can be serialized in formats like JSON-LD, YAML-LD or Turtle. More details about these semantic formats and detailed instructions how to semantically describe a data set and its generation process are collected in our First Steps Guide, together with practical examples.
The collected classes and properties are organised in a logical and hierarchical structure and either self-defined within Metadata4Ing, or reused from other ontologies. Subordinate classes and relations can be built according to the two principles of inheritance and modularity. Inheritance means that a subclass inherits all properties of its superordinate class, possibly adding some new ones. Modularity means that all expansions are independent of each other; this makes possible for instance to generate expanded ontologies for any possible combinations of method × object of research. New concepts and properties are located in the namespace of Metadata4Ing (m4i:
).
Metadata4Ing does not import complete ontologies for the sake of relevance, readability, understandability and usability by and for engineers. Instead, it references single existing classes and properties on which the m4i
classes and properties are based, including either their identifiers or a relevant subset of the axioms from the original ontology. Whenever the original set of statements about an entity needed to be extended or modified (e.g. because labels and definitions in any of the supported languages were missing, or expressed with a different owl:AnnotationProperty than the rest of Metadata4Ing), the corresponding editorial changes were declared in Metadata4Ing by an annotation with skos:editorialNote at item-level. To get the original set of statements we encourage to visit the original namespace of the respective item.
Metadata4ing models a part of the world by introducing classes and properties. A class stands for a group of individuals that all share some common properties. A subclass stands for a subset of this group. For example, the class method stands for the concept of a scientific method in general; microscopy could be a subclass of method representing all microscopy methods and coherent anti-Stokes Raman microscopy is an instance of these classes, i.e. a named individual belonging to the class method and the subclass microscopy. At present the only individuals includes are instances of role in the research data management process, which are taken from the DataCite Metadata Schema, v4.4 and following.
Properties that are attributes of a class are called datatype properties. For instance, a processing step has the following datatype properties: start time, end time, usage instruction. The range of a property defines the data type of a property. A usage instruction can for example have the range literal, a start time the range date with time*. A property's domain lists the classes that have this property as an attribute.
Relations between classes that can be used to interlink instances of these classes are called object properties. A tool implements a method, so "implements" is an object property with domain tool and range method.
This documentation lists all the classes, datatype properties, object properties and individuals that are defined by m4i or reused from other ontologies.
For further informations, please have a look at our First steps guide.
bibo | <http://purl.org/ontology/bibo/> |
biro | <http://purl.org/spar/biro/> |
cr | <http://mlcommons.org/croissant/> |
dcat | <http://www.w3.org/ns/dcat#> |
dcc | <https://ptb.de/dcc/> |
dcterms | <http://purl.org/dc/terms/> |
doap | <http://usefulinc.com/ns/doap#> |
emmo | <http://emmo.info/emmo#> |
foaf | <http://xmlns.com/foaf/0.1/> |
gnd | <http://d-nb.info/gnd/> |
m4i | <http://w3id.org/nfdi4ing/metadata4ing#> |
metadata4ing | <https://w3id.org/nfdi4ing/metadata4ing/> |
mod | <https://w3id.org/mod#> |
obo | <http://purl.obolibrary.org/obo/> |
orcid | <https://orcid.org/> |
orcid5 | <https://orcid.org/0000-0001-6272-204> |
orcid6 | <https://orcid.org/0000-0002-9826-018> |
owl | <http://www.w3.org/2002/07/owl#> |
pims-ii | <http://www.molmod.info/semantics/pims-ii.ttl#> |
premis | <http://www.loc.gov/premis/rdf/v3/> |
prov | <http://www.w3.org/ns/prov#> |
qudt | <http://qudt.org/schema/qudt/> |
rdf | <http://www.w3.org/1999/02/22-rdf-syntax-ns#> |
rdfs | <http://www.w3.org/2000/01/rdf-schema#> |
ror | <https://ror.org/> |
ror1 | <https://ror.org/05558> |
ror2 | <https://ror.org/04> |
ror3 | <https://ror.org/05> |
ror4 | <https://ror.org/02> |
ror7 | <https://ror.org/010> |
schema | <https://schema.org/> |
si | <https://ptb.de/si/> |
sio | <http://semanticscience.org/resource/> |
skos | <http://www.w3.org/2004/02/skos/core#> |
ssn | <http://www.w3.org/ns/ssn/> |
vann | <http://purl.org/vocab/vann/> |
voaf | <http://purl.org/vocommons/voaf#> |
xml | <http://www.w3.org/XML/1998/namespace> |
xsd | <http://www.w3.org/2001/XMLSchema#> |
This ontology has the following classes and properties. The standard view shows all the classes and properties meant to model scientific processes with m4i. To see also parent elements introduced for interoperability, choose expert view.
One of the main goals of the Metadata4Ing ontology is to enable researchers to document the provenance of data and material objects created or modified during research processes. Metadata4Ing accomplishes this with the help of a generalized process model, centered around the class processing step. The aforementioned data and material objects are described as output of the processing step. Other relevant information like, e.g., the methods or tools used in a research process, are described in separate classes that can be linked to processing step. A series of processing steps can be used to represent complex research processes (cf. Section "Specifying complex setups and processes by using composition"). Metadata4Ing can therefore be seen as a system of building blocks that can be referred to by processing step and in their totality enable a complete description of the provenance of a dataset or material object.
The central class of Metadata4Ing is processing step, which can be used to describe all kinds of processes and does not distinguish between different types of processing steps. The pattern formed by processing step and its admissible object properties is therefore considered universal for all kinds of processes. A distinction between processes is achieved by adding further information as described in the following subsections.
One of the major roles of processing step is to connect data and material objects to the processing step they were created in or modified by. It is usually good practice to treat modified datasets and material objects as newly created instances of their respective classes instead of reusing the original instance with altered attributes. This may seem unintuitive, especially for material objects that continue to exist after modification; but it is necessary, to be able to unambiguously refer to each "state" of modified entities. Each state may have been the subject of investigation or the in- or output in previous processing steps and therefore needs to persist as an unaltered node in the knowledge graph. For processing steps representing modifications of entities, the state before the modification would therefore be specified via has input, whereas the resulting modified state of entity would be modelled as a new instance that is specified via has output.
Has input can also be used to indicate other things that acted as input in a processing step, e.g. chemical substances or datasets (cf. Section "Specifying datasets"). Both has input and has output can refer to all kinds of entites, regardless of whether they are material (e.g. physical objects) or immaterial (e.g. datasets). Note, however, that has input should not be used for specifying tools used in a processing step or the investigated object (e.g. for a measurement), both of which can be indicated with more specific properties described in the next subsections (cf. has employed tool and investigates).
Many processes (e.g. measurements or simulations) performed during research aim to investigate an object. In Metadata4Ing, this object of investigation can be specified with the investigates property, by which an arbitrary entity (both material and immaterial) can be connected to a processing step. In addition to the object itself, a specific property that is investigated (e.g. temperature, pressure) can be specified via investigates property.
Another essential element for documenting a process is information on what has been done. For this, Metadata4Ing includes the classes method and tool. Method describes the method that has been realized in the processing step (e.g. heating, numerical simulation) along with relevant parameters and can be added to the processing step via the realizes method property. In a similar fashion, tool is used to describe a tool used to perform the processing step (e.g. water bath, simulation software) and can be linked to the processing step via the has employed tool property.
In addition, Metadata4Ing includes the implements property that can be used to indicate that a specific tool implements a certain method, as well as the inverse relation implemented by. It is recommended that at least two sides of the information triangle formed by realizes method, has employed tool and implements are included when documenting a processing step.
Depending on the granularity of the processing step described, multiple methods and tools may be added to a single processing step (cf. Section "Specifying complex setups and processes by using composition").
For both method and tool, relevant parameters (e.g. duration for the method "heating" or temperature for the tool "water bath") can be specified as individuals of the class variable, connected by the has parameter property. For further information on the description of variables, cf. Section "Representation of variables".
Any person can most prominently be identified via an ORCID ID, but also via characteristics like first name, last name, personal mailbox, or title. A person typically is affiliated to an organization, which in turn can be identified via a ROR ID.
An organization may conduct research projects. These projects may be funded by other organizations. A research project is usually limited in time and has a specific start date and end date. It usually has a unique project ID, especially when it is funded by third parties like the Deutsche Forschungsgemeinschaft (DFG). A project usually has several project participants which are organizations. A processing step may be part of such a research project.
A particular processing step can involve as participants one or more agents (e.g. people, organizations, software agents). With more detail, it can be said that the processing step involves the agents with a particular role (e.g. data collector).
The overall connection between these classes can be summarized as shown in the next figure.
Oftentimes, a process performed during research consists of several substeps performed in sequence or parallel, or a tool consists of multiple components (e.g. a hardware assembly). In Metadata4Ing, these situations can be described via composition. A complex processing step and its substeps can both be modelled as instances of processing step, and the substeps can be declared as such by giving them the part of property pointing to the instance of the complex processing step. With the properties starts with, ends with and precedes, an ordering of steps is possible. In a similar fashion, part of can be used to combine components into a multi-component tool, all of which can be modelled as instances of tool.
Since each substep in the composed step can be given all attributes of a processing step (including investigates, has employed tool, has input and has output), it becomes possible to provide a detailled description, including relations between the in- and output of specific components and substeps of a complex setup.
A building element in all quantitative sciences is the concept of variable. A variable can be assigned a value (numerical, literal or logical) and can be attributed to a research object (as an intrinsic property), to a process (as technical parameter, independent regulated variable or result) or to the content of a dataset. Thus, a variable is the result of evalutating an expression, in both the mathematical and computer-science meaning of the word. A method or a tool can refer to a variable as its parameter; a processing step can investigate it. Each variable can be explained by a description, be denoted by a symbol and get assigned a value. We distinguish two subtypes of variables: text variables and numerical variables.
A text variable has a string value, while a numerical variable has a single numerical value or multiple numerical values represented by a minimum value, a maximum value and a step size.
For numerical variables further specifications can be made: A numerical variable is associated to a defined kind of quantity and its value should be expressed using the corresponding unit. Both the kinds of quantity and the units are to a large extent normed within well-established vocabularies (SI reference point, ISO 80000, IEC Common Data Directory, QUDT, EMMO); therefore we strongly recommend to refer to them via a persistent URI to the corresponding vocabulary entry from QUDT, that is, with a child of qudt:QuantityKind
or a child of qudt:Unit
, respectively. Additionaly, a numerical variable can have a an uncertainty declaration, in the form of either a coverage interval or an expanded uncertainty containing the uncertainty value, a coverage factor, the coverage probability and optionally the underlying statistical distribution.
Research data can be the output or input of a processing step in form of one or several file objects or a of similar files in a directory or a a container denoted as a file set. Additional technical information about a file object can be its name, its content size or a SHA256 checksum. The content and structure of such a data file can be further specified by a record set of fields that represent variables. See the specification of Croissant for more information.
If a set of file objects is published in a data repository, then the entry in the repository is called a published dataset, and possesses an identifier and a landing page. In this case, the content URL of a file object refers to the download link of this file object. See the documentation of DCAT for more information about datasets.
The data acquired during research activities may become part of an analysis and a concluding interpretation. Traditionally, these activities are summed up in monographs or journal articles. Scientific publications and their metadata are fortunately online and persistently identified these days, their metadata provided as a bibliographic record. A dataset can be related to another publication in both directions: either it references a bibliographic record, or it is referenced by one.
The standard view shows all the classes and properties meant to model scientific processes with m4i. To see also parent elements introduced for interoperability, choose expert view.
IRI: http://www.w3.org/ns/prov#Agent
An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
IRI: http://www.molmod.info/semantics/pims-ii.ttl#Assignment
Assignment, i.e., a data item by which a value is assigned to a variable with respect to a particular referent (e.g., T = 200 K for substance o as it was measured in a particular cognitive step); therein, T is the variable, related to the assignment by m4i:hasVariable, 200 K is the value, related to the assignment by m4i:hasValue, and o is the referent, related to the assignment by isAssignmentFor
IRI: http://www.w3.org/ns/prov#Association
An instance of prov:Association provides additional descriptions about the binary prov:wasAssociatedWith relation from an prov:Activity to some prov:Agent that had some responsiblity for it. For example, :baking prov:wasAssociatedWith :baker; prov:qualifiedssociation [ a prov:Association; prov:agent :baker; :foo :bar ].
IRI: http://purl.org/spar/biro/BibliographicRecord
A record that uniquely describes a particular textual or data publication (or a work in preparation for publication). Each bibliographic record is a set of entities describing aspects of the referenced work, including, for example, but not restricted to: authors, title, journal, publication year, DOI, ISSN, publisher and copyright information, or, in the case of a data publication: creators, title, version, archive, publication year, DOI or other identifier). The FRBR expression of a bibliographic record is a bibliographic reference, which usually contains only a sub-set of these entities, ordered in a particular way that corresponds to the house style of the publication in which it occurs.
IRI: https://ptb.de/si/CoverageInterval
Structure for stating a probabilistic-symmetric coverage interval for a real uncertainty, to be applied to an si:Real quantity value
IRI: http://www.w3.org/ns/dcat#Dataset
A collection of data, published or curated by a single source, and available for access or download in one or more representations.
IRI: http://www.w3.org/ns/dcat#DatasetSeries
A collection of datasets that are published separately, but share some common characteristics that groups them.
IRI: http://www.w3.org/ns/dcat#Distribution
A specific representation of a dataset. A dataset might be available in multiple serializations that may differ in various ways, including natural language, media-type or format, schematic organization, temporal and spatial resolution, level of detail or profiles (which might specify any or all of the above).
IRI: https://ptb.de/si/ExpandedUnc
Structure for stating an expanded measurement, model, or simulation uncertainty, e.g., to be applied to an si:Real quantity value
IRI: http://mlcommons.org/croissant/Field
A component of the structure of a RecordSet, such as a column of a table.
IRI: http://mlcommons.org/croissant/FileObject
An individual file that is part of a dataset.
IRI: http://mlcommons.org/croissant/FileSet
A set of homogeneous files extracted from a container, optionally filtered by inclusion and/or exclusion filters.
IRI: http://xmlns.com/foaf/0.1/Group
DEPRECATED A class of Agents.
IRI: http://w3id.org/nfdi4ing/metadata4ing#Method
Abstract description of a method for analysis, generation and transformation of data and material objects like, e.g., 'Fourier Transform Infrared Spectroscopy' or 'Molecular Dynamics Simulation'. Note that while values for relevant parameters should be provided, m4i:Method does not refer to the actual execution of the process that is described (use m4i:ProcessingStep for that), but rather a description of the underlying principle.
IRI: http://w3id.org/nfdi4ing/metadata4ing#NumericalAssignment
Assignment by which a variable (e.g., a physical property) is assigned an si:Real quantity value (scalar x measurement unit) in some context (e.g., applied to some object of research)
IRI: http://w3id.org/nfdi4ing/metadata4ing#NumericalVariable
A variable that expects a float or integer as a value
IRI: http://www.w3.org/ns/prov#Organization
An organization is a social or legal institution such as a company, society, etc.
IRI: http://www.w3.org/ns/prov#Person
Person agents are people.
IRI: http://w3id.org/nfdi4ing/metadata4ing#ProcessingStep
Specific action undertaken during research
IRI: https://schema.org/Project
An enterprise (potentially individual but typically collaborative), planned to achieve a particular aim
IRI: http://www.molmod.info/semantics/pims-ii.ttl#Property
Property, i.e., a variable that can be considered (as an investigated property, i.e., target property) within a processing step
IRI: http://qudt.org/schema/qudt/QuantityKind
A Quantity Kind is any observable property that can be measured and quantified numerically. Familiar examples include physical properties such as length, mass, time, force, energy, power, electric charge, etc. Less familiar examples include currency, interest rate, price to earning ratio, and information capacity.
Kind of quantity, i.e., a physical/chemical quantity from a controlled vocabulary, such as QUDT, IEC, or EMMO
IRI: http://www.molmod.info/semantics/pims-ii.ttl#QuantityValue
Quantity value, i.e., a value that has a numerical magnitude and a physical unit
IRI: https://ptb.de/si/Real
(Real value +- uncertainty) x measurement unit, i.e., a scalar value with a measurement unit and an uncertainty indication
IRI: http://mlcommons.org/croissant/RecordSet
A description of a set of structured records from one or more data sources and their structure, expressed as a set of fields.
IRI: https://schema.org/ResearchProject
A research project
IRI: http://www.w3.org/ns/prov#Role
A role is the function of an entity or agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end.
IRI: http://www.w3.org/ns/prov#SoftwareAgent
A software agent is running software.
IRI: http://w3id.org/nfdi4ing/metadata4ing#TextVariable
A variable that expects a string of characters as a value
IRI: http://w3id.org/nfdi4ing/metadata4ing#Tool
Object that helps an agent perform an action (e.g., John wrote a book with a pen), i.e., an object of the relation schema:instrument or m4i:hasTool
IRI: http://w3id.org/nfdi4ing/metadata4ing#UncertaintyDeclaration
Declaration that can be applied to an si:Real quantity value to give an assessment of uncertainty
IRI: http://qudt.org/schema/qudt/Unit
A unit of measure, or unit is a particular quantity value that has been chosen as a scale for measuring other quantities the same kind (more generally of equivalent dimension). For example, the meter is a quantity of length that has been rigorously defined and standardized by the BIPM (International Board of Weights and Measures). Any measurement of the length can be expressed as a number multiplied by the unit meter. More formally, the value of physical quanitity Q with respect to a unit (U) is expressed as the scalar multiple of a real number (n) and U, as Q = nU.
IRI: http://www.molmod.info/semantics/pims-ii.ttl#Value
Value, i.e., an articulation that is by social convention understood to be potentially assignable to a variable
IRI: http://www.molmod.info/semantics/pims-ii.ttl#Variable
Variable, i.e., a conventional that is employed for something to which values can be assigned (this may include different notations for the same variable including, e.g., computational representations); this is to be understood very generally, e.g., a variable may be an array or set of elements or have another kind of internal structure
IRI: http://w3id.org/nfdi4ing/metadata4ing#inProject
A property that connects a person or an organization with a project.
IRI: http://www.w3.org/ns/dcat#compressFormat
The compression format of the distribution in which the data is contained in a compressed form, e.g. to reduce the size of the downloadable file.
IRI: http://www.w3.org/ns/dcat#downloadURL
The URL of the downloadable file in a given format. E.g. CSV file or RDF file. The format is indicated by the distribution's dcterms:format and/or dcat:mediaType.
IRI: http://purl.obolibrary.org/obo/RO_0002230
x ends with y if and only if x has part y and the time point at which x ends is equivalent to the time point at which y ends. Formally: α(y) > α(x) ∧ ω(y) = ω(x), where α is a function that maps a process to a start point, and ω is a function that maps a process to an end point.
has characteristics: transitive
IRI: http://mlcommons.org/croissant/field
A data element that appears in the records of the RecordSet (e.g., one column of a table).
IRI: http://www.w3.org/ns/prov#hadRole
prov:hadRole references the Role (i.e. the function of an entity with respect to an activity)
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasAdmissibleUnit
redundant information: applicable unit can be deduced from quantity kind. If one wants to enforce the use of a specific unit, use a SHACL constraint.
DEPRECATED (x hasAdmissibleUnit y) means that y is a unit that can be associated with the variable x
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasAdmissibleValue
(x hasAdmissibleValue y) means that y is a value that can be assigned to the variable x
IRI: http://www.w3.org/ns/prov#agent
The prov:agent property is used to reference an agent that had a role in an activity.
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasAssignedValue
(a hasAssignedValue y) means that a: x = y is an assignment where the value y is assigned to a variable x
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasCoverageInterval
Associates an si:Real quantity value with an si:CoverageInterval
IRI: http://www.w3.org/ns/dcat#distribution
An available distribution of the dataset.
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasEmployedTool
Points to a tool that is used within a given processing step
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasExpandedUnc
Relates an si:Real to its expanded uncertainty
IRI: http://purl.obolibrary.org/obo/RO_0002233
(x has input y) means x takes specific input as y for further processes
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasKindOfQuantity
Points to the property characterization (i.e., to the kind of quantity) from a controlled vocabulary
IRI: http://purl.obolibrary.org/obo/RO_0002234
(x has output y) means x provides specific output y for the result or further processes
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasParameter
Points to a parameter of a given method or tool.
IRI: http://purl.obolibrary.org/obo/BFO_0000051
a core relation that holds between a whole and its part
has characteristics: transitive
IRI: http://purl.obolibrary.org/obo/RO_0000057
a relation between a process and a continuant, in which the continuant is somehow involved in the process
IRI: http://www.w3.org/ns/prov#wasAssociatedWith
property between some activity and an agent involved in that activity
IRI: http://www.w3.org/ns/ssn/hasProperty
Relation between an entity and a Property of that entity.
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasRuntimeAssignment
Points to an assignment that is neither input nor output
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasUncertaintyDeclaration
Associates an si:Real quantity value with its mandatory uncertainty declaration (i.e., with an expanded uncertainty or a coverage interval)
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasUnit
Represents the unit of a numerical (real) value
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasVariable
( a hasVariable x ) means that a: x = y is an assignment where the value y is assigned to a variable x
IRI: http://purl.obolibrary.org/obo/RO_0002090
X immediately precedes_Y iff: end(X) simultaneous_with start(Y)
IRI: http://w3id.org/nfdi4ing/metadata4ing#implementedByTool
Points to a tool that implements a given method
IRI: http://w3id.org/nfdi4ing/metadata4ing#implementsMethod
Points to a method that is implemented by a given tool
IRI: http://www.w3.org/ns/dcat#inSeries
Normally, child datasets in dataset series are represented as dcat:Dataset. The use of dcat:Distribution for typing child datasets is however recognized as a possible alternative, whenever it addresses more effectively the requirements of a given application scenario.
A dataset series of which the dataset is part.
IRI: http://purl.obolibrary.org/obo/RO_0002352
(x input of y) means x is a specific input of y to carry out further processes
IRI: http://w3id.org/nfdi4ing/metadata4ing#investigates
(x investigates y) means that x is about y, in the context of scientific research and development
IRI: http://w3id.org/nfdi4ing/metadata4ing#investigatesProperty
(x investigatesProperty y) means that x is about target property y, in the context of scientific research and development
IRI: http://www.molmod.info/semantics/pims-ii.ttl#isAdmissibleUnitFor
redundant information: admissible unit can be deduced from quantity kind. If one wants to enforce the use of a specific unit, use a SHACL contraint.
DEPRECATED (x isAdmissibleUnitFor y) means that x is a unit that can be associated with the variable y; subsumption under msHPIPIR is explained as follows: There is a sign z for the variable y (where z is a description of admissible values of y) of which x is constitutive (and with which x hence overlaps)
IRI: http://www.molmod.info/semantics/pims-ii.ttl#isAdmissibleValueFor
(x isAdmissibleValueFor y) means that x is a value that can be assigned to the variable y; subsumption under msIPIRIR is explained as follows: There is a sign z for the variable y (where z is the range of admissible values of y), for which in turn there is another sign z' (where z' lists members of z, explicitly including x) of which x is a part
IRI: http://www.molmod.info/semantics/pims-ii.ttl#isAssignmentFor
(o isAssignment for d) means that d: x = y is an assignment that refers to o; e.g., x may be temperature, y may be a temperature value, and o may be an object of which the temperature has been measured or some other context to which the assignment refers
IRI: http://w3id.org/nfdi4ing/metadata4ing#isEmployedToolIn
Points to a processing step the tool has been used in
IRI: http://www.w3.org/ns/ssn/isPropertyOf
Relation between a Property and the entity it belongs to.
IRI: http://semanticscience.org/resource/SIO_000001
A is related to B iff there is some relation between A and B.
IRI: http://www.molmod.info/semantics/pims-ii.ttl#isValueInAssignment
(y isValueInAssignment a) means that a: x = y is an assignment where the value y is assigned to a variable x
IRI: http://www.molmod.info/semantics/pims-ii.ttl#isVariableInAssignment
(x isVariableInAssignment a) means that a: x = y is an assignment where a value y is assigned to the variable x
IRI: http://www.w3.org/ns/dcat#mediaType
The media type of the distribution as defined by IANA.
IRI: http://purl.obolibrary.org/obo/RO_0002353
(x output of y) means x is the specific output of y as the result or further processes
IRI: http://www.w3.org/ns/dcat#packageFormat
The package format of the distribution in which one or more data files are grouped together, e.g. to enable a set of related files to be downloaded together.
IRI: http://purl.obolibrary.org/obo/BFO_0000050
a core relation that holds between a part and its whole
IRI: http://purl.obolibrary.org/obo/RO_0000056
a relation between a continuant and a process, in which the continuant is somehow involved in the process
IRI: http://www.w3.org/ns/prov#wasAssociateFor
property between an agent and an activity with which the agent was associated with or participates in
IRI: http://xmlns.com/foaf/0.1/mbox
A personal mailbox, ie. an Internet mailbox associated with exactly one owner, the first owner of this mailbox. This is a 'static inverse functional property', in that there is (across time and change) at most one individual that ever has any particular value for foaf:mbox.
has characteristics: inverse functional
IRI: http://purl.obolibrary.org/obo/BFO_0000063
x precedes y if and only if the time point at which x ends is before or equivalent to the time point at which y starts. Formally: x precedes y iff ω(x) <= α(y), where α is a function that maps a process to a start point, and ω is a function that maps a process to an end point.
has characteristics: transitive
IRI: http://w3id.org/nfdi4ing/metadata4ing#projectParticipant
A property that connects a project with a person or an organisation.
IRI: http://www.w3.org/ns/prov#qualifiedAssociation
Allows to specify more information (e.g. a role) about an association between an agent (e.g. a person) and an Activity (e.g. a processing step).
Example application in m4i: :SomeProcess a m4i:ProcessingStep; obo:RO_0000057 :SomePerson; prov:qualifiedAssociation [ a prov:Association; prov:agent :SomePerson; prov:hadRole :SomeRole; rdfs:comment ":SomePerson had the :SomeRole in this :SomeProcess"@en ] ; skos:prefLabel "has qualified association"@en , "hat qualifizierte Beziehung"@de . The direct relation between an activity and an agent expressed with 'has participant' (http://purl.obolibrary.org/obo/RO_0000057 or http://www.w3.org/ns/prov#wasAssociatedWith) does not give details about the agent's role in that activity. Using the property prov:qualifiedAssociation one can point to a blank node (cf. https://en.wikipedia.org/w/index.php?title=Blank_node) containing additional information about the participation relation.
IRI: http://purl.obolibrary.org/obo/BFO_0000054
Paraphrase of elucidation: a relation between a realizable entity and a process, where there is some material entity that is bearer of the realizable entity and participates in the process, and the realizable entity comes to be realized in the course of the process
IRI: http://purl.obolibrary.org/obo/BFO_0000055
Paraphrase of elucidation: a relation between a process and a realizable entity, where there is some material entity that is bearer of the realizable entity and participates in the process, and the realizable entity comes to be realized in the course of the process
IRI: http://w3id.org/nfdi4ing/metadata4ing#realizesMethod
Points to a method that is used within a given processing step
IRI: http://semanticscience.org/resource/SIO_000628
refers to is a relation between one entity and the entity that it makes reference to.
IRI: http://semanticscience.org/resource/SIO_000210
A represents B when A serves as a sign, symbol or model of B.
IRI: http://w3id.org/nfdi4ing/metadata4ing#representsVariable
Points to a variable that is represented through a field within a recordset
IRI: http://mlcommons.org/croissant/source
The data source of the field. This will generally reference a FileObject or FileSet's contents (e.g., a specific column of a table).
IRI: http://purl.obolibrary.org/obo/RO_0002224
x starts with y if and only if x has part y and the time point at which x starts is equivalent to the time point at which y starts. Formally: α(y) = α(x) ∧ ω(y) < ω(x), where α is a function that maps a process to a start point, and ω is a function that maps a process to an end point.
has characteristics: transitive
IRI: https://schema.org/instrument
points to an object that helped the agent perform the action (e.g., John wrote a book with a pen)
IRI: http://www.w3.org/ns/prov#wasRoleIn
prov:wasRoleIn references the association (e.g. between an agent and an activity) in which a role shall be defined. Inverse property of prov:hadRole.
IRI: https://schema.org/endTime
The endTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to end. For actions that span a period of time, when the action was performed. e.g. John wrote a book from January to December. For media, including audio and video, it's the time offset of the end of a clip within a larger file.
Note that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions.
IRI: http://www.w3.org/ns/dcat#byteSize
The size of a distribution in bytes.
IRI: http://xmlns.com/foaf/0.1/firstName
The first name of a person.
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasAssignmentTimestamp
Points to a timestamp associated with an assignment; there are multiple kinds of timestamp datatype properties, which are included here from schema.org
IRI: https://ptb.de/si/hasCoverageFactor
points to the coverage factor, i.e., to a factor (greater than or equal to unity) by which the expanded uncertainty relates to the standard uncertainty
IRI: https://ptb.de/si/hasCoverageProbability
points to the probability (between 0 and 1) ascribed to the event of the actual value falling within the range asserted by the given uncertainty declaration
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasDateAssignmentCreated
Points to a date(time) of creation of an assignment
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasDateAssignmentDeleted
Points to a date(time) of deletion of an assignment
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasDateAssignmentModified
Points to a date(time) of modification of an assignment
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasDateAssignmentValidFrom
Points to a date(time) at which the validity of an assignment begins
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasDateAssignmentValidUntil
Points to a date(time) at which the validity of an assignment ends
IRI: http://w3id.org/nfdi4ing/metadata4ing#identifier
A systematically built alphanumeric string that identifies a unique object (e.g. a person, a publication, an organisation, a research activity, a sample, etc.) or a unique class of objects.
IRI: https://ptb.de/si/hasIntervalMax
upper boundary of the coverage interval
IRI: https://ptb.de/si/hasIntervalMin
lower boundary of the coverage interval
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasMaximumValue
Represents the highest value of a multi-valued variable
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasMinimumValue
Represents the lowest value of a multi-valued variable
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasNumericalValue
Represents the numerical value of a real
IRI: http://w3id.org/nfdi4ing/metadata4ing#orcidId
Open Researcher and Contributor ID: an identifier, that allows unique identification of a person, usually active in research.
IRI: http://w3id.org/nfdi4ing/metadata4ing#projectReferenceID
An alphanumeric identifier for a project. We recommend using an identifier which is understandable outside the involved institutions and possibly resolvable and persistent, such as the Research Activity Identifier (RAiD) or a funder-given ID (see for example the DFG project database or the EU project database).
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasRorId
A Research Organization Registry identifier that persistently and uniquely identifies a research organization
IRI: https://ptb.de/si/hasStandardUnc
The standard measurement uncertainty is the measurement uncertainty expressed as a standard deviation
IRI: https://ptb.de/si/hasDistribution
points to a descriptor/label of the assumed underlying distribution
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasStepSize
Describes the spacing of a multi-valued variable
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasStringValue
A character string of any length
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasSymbol
Letter or string that denotes a variable
IRI: https://schema.org/temporal
The 'temporal' property can be used in cases where more specific properties (e.g., dateCreated, dateModified, datePublished) are not known to be appropriate
IRI: https://ptb.de/si/hasUncertainty
absolute magnitude of the indicated uncertainty
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasValue
A value of any type
IRI: http://w3id.org/nfdi4ing/metadata4ing#hasVariableDescription
Textual and human readable description of a variable in a research context
IRI: http://xmlns.com/foaf/0.1/lastName
The last name of a person.
IRI: http://w3id.org/nfdi4ing/metadata4ing#endOfProject
end date of a project
IRI: http://w3id.org/nfdi4ing/metadata4ing#startOfProject
start date of a project
IRI: http://xmlns.com/foaf/0.1/title
Title (Mr, Mrs, Ms, Dr. etc)
IRI: http://www.w3.org/ns/dcat#spatialResolutionInMeters
Minimum spatial separation resolvable in a dataset, measured in metres.
IRI: https://schema.org/startTime
The startTime of something. For a reserved event or service (e.g. FoodEstablishmentReservation), the time that it is expected to start. For actions that span a period of time, when the action was performed. e.g. John wrote a book from January to December. For media, including audio and video, it's the time offset of the start of a clip within a larger file.
Note that Event uses startDate/endDate instead of startTime/endTime, even when describing dates with times. This situation may be clarified in future revisions.
IRI: http://www.w3.org/ns/dcat#temporalResolution
Minimum time period resolvable in a dataset.
IRI: http://w3id.org/nfdi4ing/metadata4ing#UsageInstruction
Textual description of a processing step within a research process to enable or facilitate its reproducibility
IRI: http://w3id.org/nfdi4ing/metadata4ing#ContactPerson
Person with knowledge of how to access, troubleshoot, or otherwise field issues related to the resource
IRI: http://w3id.org/nfdi4ing/metadata4ing#DataCollector
Person/institution responsible for finding or gathering/collecting data under the guidelines of the author(s) or Principal Investigator (PI)
IRI: http://w3id.org/nfdi4ing/metadata4ing#DataCurator
Person tasked with reviewing, enhancing, cleaning, or standardizing metadata and the associated data submitted for storage, use, and maintenance within a data centre or repository
IRI: http://w3id.org/nfdi4ing/metadata4ing#DataManager
Person (or organisation with a staff of data managers, such as a data centre) responsible for maintaining the finished resource
IRI: http://w3id.org/nfdi4ing/metadata4ing#Distributor
Institution tasked with responsibility to generate/disseminate copies of the resource in either electronic or print form
IRI: http://w3id.org/nfdi4ing/metadata4ing#Editor
A person who oversees the details related to the publication format of the resource
IRI: http://w3id.org/nfdi4ing/metadata4ing#HostingInstitution
Typically, the organisation allowing the resource to be available on the internet through the provision of its hardware/software/operating support
IRI: http://w3id.org/nfdi4ing/metadata4ing#
IRI: http://w3id.org/nfdi4ing/metadata4ing#Other
Any person or institution making a significant contribution to the development and/or maintenance of the resource, but whose contribution is notadequately described by any of the other values for contributorType
IRI: http://w3id.org/nfdi4ing/metadata4ing#Producer
Typically,a person or organisation responsible for the artistry and form of a media product
IRI: http://w3id.org/nfdi4ing/metadata4ing#ProjectLeader
Person officially designated as head of project team or sub-project team instrumental in the work necessary to development of the resource
IRI: http://w3id.org/nfdi4ing/metadata4ing#ProjectManager
Person officially designated as manager of a project. Project may consist of one or many project teams and sub-teams.
IRI: http://w3id.org/nfdi4ing/metadata4ing#ProjectMember
Person on the membership list of a designated project/project team
IRI: http://w3id.org/nfdi4ing/metadata4ing#RegistrationAgency
Institution/organisation officially appointed by a Registration Authority to handle specific tasks within a defined area of responsibility
IRI: http://w3id.org/nfdi4ing/metadata4ing#RegistrationAuthority
A standards-setting body from which Registration Agencies obtain official recognition and guidance
IRI: http://w3id.org/nfdi4ing/metadata4ing#RelatedPerson
A person without a specifically defined role in the development of the resource, but who is someone the author wishes to recognize
IRI: http://w3id.org/nfdi4ing/metadata4ing#ResearchGroup
Typically refers to a group of individuals with a lab, department, or divisionthathas a specifically defined focus of activity.
IRI: http://w3id.org/nfdi4ing/metadata4ing#Researcher
A person involved in analysing data or the results of an experiment or formal study. May indicate an intern or assistant to one of the authors who helped with research but who was not so “key” as to be listed as an author.
IRI: http://w3id.org/nfdi4ing/metadata4ing#RightsHolder
Person or institution owning or managing property rights, including intellectual property rights over the resource
IRI: http://w3id.org/nfdi4ing/metadata4ing#Sponsor
Person or organisation that issued a contract or under the auspices of which a work has been written, printed, published, developed, etc.
IRI: http://w3id.org/nfdi4ing/metadata4ing#Supervisor
Designated administrator over one or more groups/teams working to produce a resource, or over one or more steps of a development process
IRI: http://w3id.org/nfdi4ing/metadata4ing#WorkPackageLeader
A Work Package is a recognized data product, not all of which is included in publication. The package, instead, may include notes, discarded documents, etc. The Work Package Leader is responsible for ensuring the comprehensive contents, versioning, and availability of the Work Package during the development of the resource.
DataCite Metadata Working Group. (2024). DataCite Metadata Schema for the Publication and Citation of Research Data and Other Research Outputs. Version 4.6. https://doi.org/10.14454/csba-e454
Iglezakis, Dorothea; Terzijska, Džulia; Arndt, Susanne; Leimer, Sophia; Hickmann, Johanna; Fuhrmans, Marc; Lanza, Giacomo (2023). Modelling Scientific Processes With the m4i Ontology. Proceedings of the Conference on Research Data Infrastructure, 1. https://doi.org/10.52825/cordi.v1i.271
Preuß, Nils; Bodenbenner, Matthias, Heinrichs, Benedikt; Windeck, Jürgen; Moser, Mario; Fuhrmans, Marc (2023). Creating application-specific metadata profiles while improving interoperability and consistency of research data for the engineering sciences. Universitäts- und Landesbibliothek Darmstadt. https://doi.org/10.26083/tuprints-00024573
Horsch, Martin Thomas (2021). Mereosemiotics: Five scenarios (first revised version). Zenodo. https://doi.org/10.5281/zenodo.4846313
Fuhrmans, Marc; Iglezakis, Dorothea (2020). Metadata4Ing: Ansatz zur Modellierung interoperabler Metadaten für die Ingenieurwissenschaften. Interoperabilität von Metadaten innerhalb der NFDI - Konsortienübergreifender Metadaten-Workshop. Zenodo. https://doi.org/10.5281/zenodo.3982367
Hutzschenreuter, Daniel et al (2020). SmartCom Digital System of Units (D-SI): Guide for the use of the metadata-format used in metrology for the easy-to-use, safe, harmonised and unambiguous digital transfer of metrological data - Second Edition (D-SI 1.3.0-2). Zenodo. https://doi.org/10.5281/zenodo.3816686
Schembera, Björn; Iglezakis, Dorothea (2020). EngMeta - Metadata for Computational Engineering. International Journal of Metadata, Semantics and Ontologies, 14, 26-38. https://doi.org/10.1504/IJMSO.2020.107792
Reused Ontologies:
The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.
The authors would like to thank the Federal Government and the Heads of Government of the Länder, as well as the Joint Science Conference (GWK), for their funding and support within the framework of the NFDI4Ing consortium, which was funded by the German Research Foundation (DFG) under the project number 442146713.
This element is a parent element that is not intended to use for modeling, but only for interoperability with other ontologies.
An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.