@prefix : . @prefix dce: . @prefix obo: . @prefix owl: . @prefix rdf: . @prefix xml: . @prefix xsd: . @prefix bibo: . @prefix doap: . @prefix rdfs: . @prefix skos: . @prefix swrl: . @prefix vann: . @prefix swrlb: . @prefix dcterms: . @prefix ontology: . @base . rdf:type owl:Ontology ; owl:versionIRI ; dcterms:bibliographicCitation "Jörg Waitelonis, Oleksandra Bruns, Tabea Tietz, Etienne Posthumus, Hossein Beygi Nasrabadi, Harald Sack. NFDIcore Ontology. Revision: v3.0.4. Retrieved from: https://nfdi.fiz-karlsruhe.de/ontology/3.0.4" ; dcterms:created "2026-02-05" ; dcterms:creator , , , , , ; dcterms:description """The National Research Data Infrastructure (NFDI) initiative has led to the formation of various consortia, each focused on developing a research data infrastructure tailored to its specific domain. To ensure interoperability across these consortia, the NFDIcore ontology has been developed as a mid-level ontology for representing metadata related to NFDI resources, including individuals, organizations, projects, data portals, and more. Further infomration can be found at GitHub: https://github.com/ISE-FIZKarlsruhe/nfdicore/"""@en ; dcterms:license ; dcterms:title "NFDIcore Ontology"@en ; bibo:status "Ontology Specification"@en ; vann:preferredNamespaceUri ontology: ; doap:repository ; rdfs:label "NFDIcore" ; owl:priorVersion ; owl:versionInfo "3.0.4" . ################################################################# # Annotation properties ################################################################# ### http://purl.obolibrary.org/obo/IAO_0000112 obo:IAO_0000112 rdf:type owl:AnnotationProperty ; obo:IAO_0000115 "A phrase describing how a term should be used and/or a citation to a work which uses it. May also include other kinds of examples that facilitate immediate understanding, such as widely know prototypes or instances of a class, or cases where a relation is said to hold."@en , "A phrase describing how a class name should be used. May also include other kinds of examples that facilitate immediate understanding of a class semantics, such as widely known prototypical subclasses or instances of the class. Although essential for high level terms, examples for low level terms (e.g., Affymetrix HU133 array) are not." ; obo:IAO_0000119 "GROUP:OBI:"@en , "IAO" ; rdfs:label "example of usage"@en , "example of usage" . ### http://purl.obolibrary.org/obo/IAO_0000115 obo:IAO_0000115 rdf:type owl:AnnotationProperty ; obo:IAO_0000115 "The official OBI definition, explaining the meaning of a class or property. Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions."@en , "The official definition, explaining the meaning of a class or property. Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions."@en ; obo:IAO_0000116 """2012-04-05: Barry Smith The official OBI definition, explaining the meaning of a class or property: 'Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions' is terrible. Can you fix to something like: A statement of necessary and sufficient conditions explaining the meaning of an expression referring to a class or property. Alan Ruttenberg Your proposed definition is a reasonable candidate, except that it is very common that necessary and sufficient conditions are not given. Mostly they are necessary, occasionally they are necessary and sufficient or just sufficient. Often they use terms that are not themselves defined and so they effectively can't be evaluated by those criteria. On the specifics of the proposed definition: We don't have definitions of 'meaning' or 'expression' or 'property'. For 'reference' in the intended sense I think we use the term 'denotation'. For 'expression', I think we you mean symbol, or identifier. For 'meaning' it differs for class and property. For class we want documentation that let's the intended reader determine whether an entity is instance of the class, or not. For property we want documentation that let's the intended reader determine, given a pair of potential relata, whether the assertion that the relation holds is true. The 'intended reader' part suggests that we also specify who, we expect, would be able to understand the definition, and also generalizes over human and computer reader to include textual and logical definition. Personally, I am more comfortable weakening definition to documentation, with instructions as to what is desirable. We also have the outstanding issue of how to aim different definitions to different audiences. A clinical audience reading chebi wants a different sort of definition documentation/definition from a chemistry trained audience, and similarly there is a need for a definition that is adequate for an ontologist to work with."""@en , """2012-04-05: Barry Smith The official OBI definition, explaining the meaning of a class or property: 'Shall be Aristotelian, formalized and normalized. Can be augmented with colloquial definitions' is terrible. Can you fix to something like: A statement of necessary and sufficient conditions explaining the meaning of an expression referring to a class or property. Alan Ruttenberg Your proposed definition is a reasonable candidate, except that it is very common that necessary and sufficient conditions are not given. Mostly they are necessary, occasionally they are necessary and sufficient or just sufficient. Often they use terms that are not themselves defined and so they effectively can't be evaluated by those criteria. On the specifics of the proposed definition: We don't have definitions of 'meaning' or 'expression' or 'property'. For 'reference' in the intended sense I think we use the term 'denotation'. For 'expression', I think we you mean symbol, or identifier. For 'meaning' it differs for class and property. For class we want documentation that let's the intended reader determine whether an entity is instance of the class, or not. For property we want documentation that let's the intended reader determine, given a pair of potential relata, whether the assertion that the relation holds is true. The 'intended reader' part suggests that we also specify who, we expect, would be able to understand the definition, and also generalizes over human and computer reader to include textual and logical definition. Personally, I am more comfortable weakening definition to documentation, with instructions as to what is desirable. We also have the outstanding issue of how to aim different definitions to different audiences. A clinical audience reading chebi wants a different sort of definition documentation/definition from a chemistry trained audience, and similarly there is a need for a definition that is adequate for an ontologist to work with. """@en ; obo:IAO_0000119 "GROUP:OBI:"@en ; rdfs:label "definition"@en , "definition" , "textual definition" . ### http://purl.obolibrary.org/obo/IAO_0000116 obo:IAO_0000116 rdf:type owl:AnnotationProperty ; obo:IAO_0000115 "An administrative note intended for its editor. It may not be included in the publication version of the ontology, so it should contain nothing necessary for end users to understand the ontology."@en ; obo:IAO_0000119 "GROUP:OBI:"@en ; rdfs:label "editor note"@en . ### http://purl.obolibrary.org/obo/IAO_0000118 obo:IAO_0000118 rdf:type owl:AnnotationProperty ; obo:IAO_0000115 "A label for a class or property that can be used to refer to the class or property instead of the preferred rdfs:label. Alternative labels should be used to indicate community- or context-specific labels, abbreviations, shorthand forms and the like."@en ; obo:IAO_0000119 "GROUP:OBI:"@en ; rdfs:label "alternative label"@en . ### http://purl.obolibrary.org/obo/IAO_0000119 obo:IAO_0000119 rdf:type owl:AnnotationProperty ; obo:IAO_0000115 "Formal citation, e.g. identifier in external database to indicate / attribute source(s) for the definition. Free text indicate / attribute source(s) for the definition. EXAMPLE: Author Name, URI, MeSH Term C04, PUBMED ID, Wiki uri on 31.01.2007"@en ; obo:IAO_0000119 "Discussion on obo-discuss mailing-list, see http://bit.ly/hgm99w"@en , "GROUP:OBI:"@en ; rdfs:label "definition source"@en , "definition source" . ### http://purl.obolibrary.org/obo/IAO_0100001 obo:IAO_0100001 rdf:type owl:AnnotationProperty ; obo:IAO_0000115 "Use on obsolete terms, relating the term to another term that can be used as a substitute"@en ; obo:IAO_0000119 "Person:Alan Ruttenberg"@en ; rdfs:label "term replaced by"@en . ### http://purl.obolibrary.org/obo/OMO_0002000 obo:OMO_0002000 rdf:type owl:AnnotationProperty ; obo:IAO_0000112 """'part disjoint with' 'defined by construct' \"\"\" PREFIX owl: PREFIX :