@prefix dc: .
@prefix dcterms: .
@prefix ns1: .
@prefix ns2: .
@prefix ns3: .
@prefix ns4: .
@prefix owl: .
@prefix rdf: .
@prefix rdfs: .
@prefix skos: .
ns1:IAO_0000112 a owl:AnnotationProperty .
ns1:IAO_0000115 a owl:AnnotationProperty .
ns1:IAO_0000116 a owl:AnnotationProperty .
ns1:IAO_0000118 a owl:AnnotationProperty .
ns1:IAO_0000119 a owl:AnnotationProperty .
ns1:IAO_0000219 a owl:ObjectProperty ;
rdfs:label "denotes"@en ;
ns1:IAO_0000112 "A person's name denotes the person. A variable name in a computer program denotes some piece of memory. Lexically equivalent strings can denote different things, for instance \"Alan\" can denote different people. In each case of use, there is a case of the denotation relation obtaining, between \"Alan\" and the person that is being named."@en ;
ns1:IAO_0000115 "A primitive, instance-level, relation obtaining between an information content entity and some portion of reality. Denotation is what happens when someone creates an information content entity E in order to specifically refer to something. The only relation between E and the thing is that E can be used to 'pick out' the thing. This relation connects those two together. Freedictionary.com sense 3: To signify directly; refer to specifically"@en ;
ns1:IAO_0000116 """2009-11-10 Alan Ruttenberg. Old definition said the following to emphasize the generic nature of this relation. We no longer have 'specifically denotes', which would have been primitive, so make this relation primitive.
g denotes r =def
r is a portion of reality
there is some c that is a concretization of g
every c that is a concretization of g specifically denotes r"""@en ;
ns1:IAO_0000119 "Conversations with Barry Smith, Werner Ceusters, Bjoern Peters, Michel Dumontier, Melanie Courtot, James Malone, Bill Hogan"@en ;
rdfs:domain ns1:IAO_0000030 ;
rdfs:range ns1:BFO_0000001 ;
rdfs:subPropertyOf ns1:IAO_0000136 ;
owl:inverseOf ns1:IAO_0000235 .
ns1:RO_0000079 a owl:ObjectProperty ;
rdfs:label "function of"@en ;
ns1:IAO_0000112 "this catalysis function is a function of this enzyme"@en ;
ns1:IAO_0000115 "a relation between a function and an independent continuant (the bearer), in which the function specifically depends on the bearer for its existence"@en ;
ns1:IAO_0000116 "A function inheres in its bearer at all times for which the function exists, however the function need not be realized at all the times that the function exists."@en ;
rdfs:domain ns1:BFO_0000034 ;
rdfs:subPropertyOf ns1:RO_0000052 ;
owl:inverseOf ns1:RO_0000085 .
ns1:RO_0000080 a owl:ObjectProperty ;
rdfs:label "quality of"@en ;
ns1:IAO_0000112 "this red color is a quality of this apple"@en ;
ns1:IAO_0000115 "a relation between a quality and an independent continuant (the bearer), in which the quality specifically depends on the bearer for its existence"@en ;
ns1:IAO_0000116 "A quality inheres in its bearer at all times for which the quality exists."@en ;
rdfs:domain [ a owl:Class ;
owl:intersectionOf ( ns1:BFO_0000019 [ a owl:Class ;
owl:complementOf ns1:BFO_0000145 ] ) ] ;
rdfs:subPropertyOf ns1:RO_0000052 ;
owl:inverseOf ns1:RO_0000086 .
ns1:RO_0000081 a owl:ObjectProperty ;
rdfs:label "role of"@en ;
ns1:IAO_0000112 "this investigator role is a role of this person"@en ;
ns1:IAO_0000115 "a relation between a role and an independent continuant (the bearer), in which the role specifically depends on the bearer for its existence"@en ;
ns1:IAO_0000116 "A role inheres in its bearer at all times for which the role exists, however the role need not be realized at all the times that the role exists."@en ;
rdfs:subPropertyOf ns1:RO_0000052 ;
owl:inverseOf ns1:RO_0000087 .
dc:identifier a owl:AnnotationProperty .
dcterms:bibliographicCitation a owl:AnnotationProperty .
dcterms:conformsTo a owl:AnnotationProperty .
dcterms:creator a owl:AnnotationProperty .
dcterms:license a owl:AnnotationProperty .
a owl:Ontology .
ns4:coversRequirements a owl:AnnotationProperty .
ns4:extractedFrom a owl:AnnotationProperty .
ns4:hasComponent a owl:AnnotationProperty .
ns4:hasConsequences a owl:AnnotationProperty .
ns4:hasIntent a owl:AnnotationProperty .
ns4:hasUnitTest a owl:AnnotationProperty .
ns4:isSpecializationOf a owl:AnnotationProperty .
ns4:reengineeredFrom a owl:AnnotationProperty .
ns4:relatedCPs a owl:AnnotationProperty .
ns4:scenarios a owl:AnnotationProperty .
skos:altLabel a owl:AnnotationProperty .
skos:definition a owl:AnnotationProperty .
skos:editorialNote a owl:AnnotationProperty .
skos:example a owl:AnnotationProperty .
skos:scopeNote a owl:AnnotationProperty .
a ;
rdfs:label "IUC1" ;
ns1:IAO_0000235 ,
,
,
,
;
ns1:RO_0000087 ;
ns1:RO_0002353 ;
ns3:NFDI_0000226 .
a owl:Ontology ;
rdfs:label "matwerkiuc — NFDI-MatWerk ontology design pattern" ;
dcterms:bibliographicCitation "Hossein Beygi Nasrabadi, Jörg Waitelonis, Ebrahim Norouzi, Kostiantyn Hubaiev, Harald Sack. NFDI MatWerk Ontology (mwo). Revision: v3.0.1. Retrieved from: http://purls.helmholtz-metadaten.de/mwo/3.0.1" ;
dcterms:conformsTo ;
dcterms:creator ,
,
,
;
dcterms:license "CC BY 4.0 (repository); CC0 1.0 declared in the ontology header" ;
ns4:coversRequirements "Which datasets, software and services does a given use case produce or consume?",
"Which infrastructure use cases exist, and which task area does each belong to?",
"Which organisations collaborate on a given infrastructure use case?" ;
ns4:extractedFrom "the matwerkiuc tab of the NFDI-MatWerk curation workbook" ;
ns4:hasComponent ns1:IAO_0000005,
ns1:IAO_0000642,
,
ns3:NFDI_0001101 ;
ns4:hasConsequences "Values become reusable and independently addressable, and one value may be shared by many entities. The cost: every `I` reference resolves by label, so labels must be unique and a typo yields a silently missing relation rather than an error." ;
ns4:hasIntent "To represent a infrastructure use case in the MatWerk Knowledge Graph: its identity, the value nodes that describe it, and its links to the other entities the NFDI-MatWerk consortium records." ;
ns4:hasUnitTest "SELECT ?x ?label WHERE { ?x a ; ?label } LIMIT 10" ;
ns4:isSpecializationOf ;
ns4:reengineeredFrom "ROBOT template directives, row 2 of the matwerkiuc tab" ;
ns4:scenarios "“IUC1” is a infrastructure use case, with iuc name “Web-based demonstration and teaching framework for MSE research data infrastructure”; main task area “TA-CI”; related task area “TA-MDI,TA-WSD”." ;
rdfs:isDefinedBy ;
owl:versionIRI ;
owl:versionInfo "1.0.0" .
ns3:NFDI_0010013 a owl:AnnotationProperty .
ns1:BFO_0000054 a owl:ObjectProperty ;
rdfs:label "has realization"@en ;
dc:identifier "206-BFO" ;
rdfs:domain ns1:BFO_0000017 ;
rdfs:range ns1:BFO_0000015 ;
owl:inverseOf ns1:BFO_0000055 ;
skos:altLabel "realized in"@en ;
skos:definition "b has realization c =Def c realizes b"@en ;
skos:example "As for realizes"@en .
ns1:BFO_0000055 a owl:ObjectProperty ;
rdfs:label "realizes"@en ;
dc:identifier "059-BFO" ;
rdfs:domain ns1:BFO_0000015 ;
rdfs:range ns1:BFO_0000017 ;
skos:definition "(Elucidation) realizes is a relation between a process b and realizable entity c such that c inheres in some d & for all t, if b has participant d then c exists & the type instantiated by b is correlated with the type instantiated by c"@en ;
skos:example "A balding process realizes a disposition to go bald; a studying process realizes a student role; a process of pumping blood realizes the pumping function of a heart"@en ;
skos:scopeNote "Users that require more sophisticated representations of time are encouraged to import a temporal extension of BFO-Core provided by the BFO development team. See documentation for guidance: "@en .
ns1:BFO_0000141 a owl:Class ;
rdfs:label "immaterial entity"@en ;
dc:identifier "028-BFO" ;
rdfs:subClassOf ns1:BFO_0000004 ;
skos:definition "b is an immaterial entity =Def b is an independent continuant which is such that there is no time t when it has a material entity as continuant part"@en ;
skos:example "As for fiat point, fiat line, fiat surface, site"@en .
ns1:BFO_0000145 a owl:Class ;
rdfs:label "relational quality"@en ;
dc:identifier "057-BFO" ;
rdfs:subClassOf ns1:BFO_0000019 ;
skos:definition "b is a relational quality =Def b is a quality & there exists c and d such that c and d are not identical & b specifically depends on c & b specifically depends on d"@en ;
skos:example "A marriage bond; an instance of love; an obligation between one person and another"@en .
ns1:IAO_0000033 a owl:Class ;
rdfs:label "directive information entity"@en ;
ns1:IAO_0000115 "An information content entity whose concretizations indicate to their bearer how to realize them in a process."@en ;
ns1:IAO_0000116 "2009-03-16: provenance: a term realizable information entity was proposed for OBI (OBI_0000337) , edited by the PlanAndPlannedProcess branch. Original definition was \"is the specification of a process that can be concretized and realized by an actor\" with alternative term \"instruction\".It has been subsequently moved to IAO where the objective for which the original term was defined was satisfied with the definitionof this, different, term."@en,
"2013-05-30 Alan Ruttenberg: What differentiates a directive information entity from an information concretization is that it can have concretizations that are either qualities or realizable entities. The concretizations that are realizable entities are created when an individual chooses to take up the direction, i.e. has the intention to (try to) realize it."@en,
"8/6/2009 Alan Ruttenberg: Changed label from \"information entity about a realizable\" after discussions at ICBO"@en,
"Werner pushed back on calling it realizable information entity as it isn't realizable. However this name isn't right either. An example would be a recipe. The realizable entity would be a plan, but the information entity isn't about the plan, it, once concretized, *is* the plan. -Alan"@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:onProperty ns1:IAO_0000136 ;
owl:someValuesFrom ns1:BFO_0000017 ],
ns1:IAO_0000030 .
ns1:IAO_0000235 a owl:ObjectProperty ;
rdfs:label "denoted by",
"denoted by"@en ;
ns1:IAO_0000115 "inverse of the relation 'denotes'"@en ;
rdfs:domain ns1:BFO_0000001 ;
rdfs:range ns1:IAO_0000030 ;
rdfs:subPropertyOf ns3:NFDI_0000226 .
ns1:IAO_0000590 a owl:Class ;
rdfs:label "written name",
"written name"@en ;
ns1:IAO_0000112 "\"Bill Clinton\""@en,
"\"The Eiffel Tower\""@en,
"\"United States of America\""@en ;
ns1:IAO_0000115 "A textual entity that denotes a particular in reality."@en ;
ns1:IAO_0000119 "https://github.com/information-artifact-ontology/IAO/issues/114"@en ;
rdfs:subClassOf ns1:IAO_0000300 .
ns1:RO_0000056 a owl:ObjectProperty ;
rdfs:label "participates in",
"participates in"@en ;
ns1:IAO_0000112 "this blood clot participates in this blood coagulation"@en,
"this input material (or this output material) participates in this process"@en,
"this investigator participates in this investigation"@en ;
ns1:IAO_0000115 "a relation between a continuant and a process, in which the continuant is somehow involved in the process"@en ;
rdfs:domain ns1:BFO_0000002 ;
rdfs:range ns1:BFO_0000003 ;
owl:inverseOf ns1:RO_0000057 .
ns1:RO_0000091 a owl:ObjectProperty ;
rdfs:label "has disposition"@en ;
ns1:IAO_0000115 "a relation between an independent continuant (the bearer) and a disposition, in which the disposition specifically depends on the bearer for its existence"@en ;
rdfs:domain ns1:BFO_0000004 ;
rdfs:range ns1:BFO_0000016 ;
rdfs:subPropertyOf ns1:RO_0000053 ;
owl:inverseOf ns1:RO_0000092 .
ns1:RO_0000092 a owl:ObjectProperty ;
rdfs:label "disposition of"@en ;
ns1:IAO_0000115 "inverse of has disposition" ;
rdfs:subPropertyOf ns1:RO_0000052 .
ns1:RO_0002234 a owl:ObjectProperty ;
rdfs:label "has output"@en ;
ns1:IAO_0000115 "p has output c iff c is a participant in p, c is present at the end of p, and c is not present in the same state at the beginning of p." ;
rdfs:subPropertyOf ns1:RO_0000057 ;
owl:inverseOf ns1:RO_0002353 .
ns1:RO_0002353 a owl:ObjectProperty ;
rdfs:label "output of",
"output of"@en ;
ns1:IAO_0000115 "inverse of has output" ;
rdfs:subPropertyOf ns1:RO_0000056 .
a owl:Class ;
rdfs:label "infrastructure use case",
"infrastructure use case"@en ;
ns1:IAO_0000118 "IUC" ;
rdfs:comment "An Infrastructure Use Case (IUC) is a service product that defines a specific application scenario, requirement, or implementation of research infrastructure, demonstrating its functionality, benefits, and impact in a given scientific or industrial domain." ;
rdfs:subClassOf ns3:NFDI_0000232 ;
skos:example "NFDI MatWerk Infrastructure Use Cases (IUCs) are exmplary scenarios used to demonstrate and validate the functionality of the NFDI-MatWerk infrastructure in real-world research contexts. They illustrate how the digital infrastructure can be applied to various stages of materials science research, including data acquisition, processing, sharing, and analysis. Developed in collaboration with the research community, IUCs provide detailed examples of how researchers can effectively use the infrastructure to enhance their workflows. By showcasing specific applications, IUCs highlight the capabilities and benefits of the infrastructure, guiding its development to meet actual research needs and ensuring that it aligns with the dynamic requirements of materials science and engineering." .
a ns1:IAO_0000005 ;
rdfs:label "TA-CI" .
a ns1:IAO_0000590 ;
rdfs:label "Web-based demonstration and teaching framework for MSE research data infrastructure" .
a ns3:NFDI_0001018 ;
rdfs:label "Teaching" .
a ;
rdfs:label "Students can experience the the full functionality of the DME and learn to use workflows with pre-existing datasets and ontologies." .
a ns3:NFDI_0001101 ;
rdfs:label "teaching personnel can tailor the demo framework as well as datasets and workflows to match their study courses." .
a ns1:IAO_0000642 ;
rdfs:label "Support for the development of academic teaching materials (TA-CI); DME (TA-MDI); Validated and well-documented workflows (TA-CI)" .
a ns3:NFDI_0000101 ;
rdfs:label "IUCProcess 1" .
a ns3:NFDI_0000228 ;
rdfs:label "IUCRole 1" .
ns3:NFDI_0000228 a owl:Class ;
rdfs:label "service product role",
"service product role"@en ;
rdfs:comment "Role of an immaterial entity that facilitates the delivery or support of a service product, ensuring its proper execution and value realization."@en ;
rdfs:subClassOf [ a owl:Class ;
owl:intersectionOf ( ns1:BFO_0000023 [ a owl:Restriction ;
owl:onProperty ns1:BFO_0000054 ;
owl:someValuesFrom ns3:NFDI_0000101 ] ) ] .
ns3:NFDI_0001018 a owl:Class ;
rdfs:label "textual description",
"textual description"@en ;
rdfs:comment "A textual entity that describe some resource."@en ;
rdfs:subClassOf ns1:IAO_0000300 .
rdfs:label "Harald Sack" .
rdfs:label "Jörg Waitelonis" .
rdfs:label "Ebrahim Norouzi" .
rdfs:label "Hossein Beygi Nasrabadi" .
ns1:IAO_0000005 a owl:Class ;
rdfs:label "objective specification",
"objective specification"@en ;
ns1:IAO_0000112 "In the protocol of a ChIP assay the objective specification says to identify protein and DNA interaction."@en ;
ns1:IAO_0000115 "A directive information entity that describes an intended process endpoint. When part of a plan specification the concretization is realized in a planned process in which the bearer tries to effect the world so that the process endpoint is achieved."@en ;
ns1:IAO_0000116 "2009-03-16: original definition when imported from OBI read: \"objective is an non realizable information entity which can serve as that proper part of a plan towards which the realization of the plan is directed.\""@en,
"2014-03-31: In the example of usage (\"In the protocol of a ChIP assay the objective specification says to identify protein and DNA interaction\") there is a protocol which is the ChIP assay protocol. In addition to being concretized on paper, the protocol can be concretized as a realizable entity, such as a plan that inheres in a person. The objective specification is the part that says that some protein and DNA interactions are identified. This is a specification of a process endpoint: the boundary in the process before which they are not identified and after which they are. During the realization of the plan, the goal is to get to the point of having the interactions, and participants in the realization of the plan try to do that."@en,
"Answers the question, why did you do this experiment?"@en ;
ns1:IAO_0000118 "goal specification"@en ;
ns1:IAO_0000119 "OBI Plan and Planned Process/Roles Branch"@en,
"OBI_0000217"@en ;
rdfs:subClassOf ns1:IAO_0000033 .
ns1:IAO_0000642 a owl:Class ;
rdfs:label "requirements textual entity",
"requirements textual entity"@en ;
ns1:IAO_0000112 """From Qi et al. BMC Bioinformatics. 2014; 15: 11. (http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3897912/):
• Operating systems: Platform independent
• Programming language: Matlab, R, Python
• Other requirements: None
• License: GNU GPL v3
• Any restrictions to use by non-academics: None"""@en ;
ns1:IAO_0000115 "A textual entity that expresses the requirements necessary to use a resource, e.g. software."@en ;
rdfs:subClassOf ns1:IAO_0000300 .
ns1:RO_0000057 a owl:ObjectProperty ;
rdfs:label "has participant"@en ;
ns1:IAO_0000112 "this blood coagulation has participant this blood clot"@en,
"this investigation has participant this investigator"@en,
"this process has participant this input material (or this output material)"@en ;
ns1:IAO_0000115 "a relation between a process and a continuant, in which the continuant is somehow involved in the process"@en ;
ns1:IAO_0000116 "Has_participant is a primitive instance-level relation between a process, a continuant, and a time at which the continuant participates in some way in the process. The relation obtains, for example, when this particular process of oxygen exchange across this particular alveolar membrane has_participant this particular sample of hemoglobin at this particular time."@en ;
rdfs:domain ns1:BFO_0000003 ;
rdfs:range ns1:BFO_0000002 .
ns1:RO_0000085 a owl:ObjectProperty ;
rdfs:label "has function"@en ;
ns1:IAO_0000112 "this enzyme has function this catalysis function (more colloquially: this enzyme has this catalysis function)"@en ;
ns1:IAO_0000115 "a relation between an independent continuant (the bearer) and a function, in which the function specifically depends on the bearer for its existence"@en ;
ns1:IAO_0000116 "A bearer can have many functions, and its functions can exist for different periods of time, but none of its functions can exist when the bearer does not exist. A function need not be realized at all the times that the function exists."@en ;
rdfs:domain ns1:BFO_0000004 ;
rdfs:range ns1:BFO_0000034 ;
rdfs:subPropertyOf ns1:RO_0000053 .
ns1:RO_0000086 a owl:ObjectProperty ;
rdfs:label "has quality"@en ;
ns1:IAO_0000112 "this apple has quality this red color"@en ;
ns1:IAO_0000115 "a relation between an independent continuant (the bearer) and a quality, in which the quality specifically depends on the bearer for its existence"@en ;
ns1:IAO_0000116 "A bearer can have many qualities, and its qualities can exist for different periods of time, but none of its qualities can exist when the bearer does not exist."@en ;
rdfs:range ns1:BFO_0000019 ;
rdfs:subPropertyOf ns1:RO_0000053 .
ns1:RO_0000087 a owl:ObjectProperty ;
rdfs:label "has role",
"has role"@en ;
ns1:IAO_0000112 "this person has role this investigator role (more colloquially: this person has this role of investigator)"@en ;
ns1:IAO_0000115 "a relation between an independent continuant (the bearer) and a role, in which the role specifically depends on the bearer for its existence"@en ;
ns1:IAO_0000116 "A bearer can have many roles, and its roles can exist for different periods of time, but none of its roles can exist when the bearer does not exist. A role need not be realized at all the times that the role exists."@en ;
rdfs:domain ns1:BFO_0000004 ;
rdfs:range ns1:BFO_0000023 ;
rdfs:subPropertyOf ns1:RO_0000053 .
a owl:Class ;
rdfs:label "measure textual entity",
"measure textual entity"@en ;
rdfs:comment "A measure textual entity is a textual entity that describes quantitative or qualitative assessments, metrics, or evaluation criteria used to analyze, compare, or monitor a specific process, performance, or characteristic." ;
rdfs:subClassOf ns1:IAO_0000300 .
ns3:NFDI_0000101 a owl:Class ;
rdfs:label "service process",
"service process"@en ;
rdfs:comment "A process that organizes activities and resources to deliver a specific service, ensuring its efficiency, reliability, and alignment with intended goals."@en ;
rdfs:subClassOf [ a owl:Class ;
owl:intersectionOf ( ns1:BFO_0000015 [ a owl:Restriction ;
owl:onProperty ns1:RO_0002234 ;
owl:someValuesFrom ns3:NFDI_0000232 ] ) ] ;
ns3:NFDI_0010013 "Issue: https://github.com/ISE-FIZKarlsruhe/nfdicore/issues/75" .
ns3:NFDI_0000226 a owl:ObjectProperty ;
rdfs:label "is subject of",
"is subject of"@en ;
rdfs:comment "inverse of the relation 'is about'" ;
skos:altLabel "is described by" .
ns3:NFDI_0000232 a owl:Class ;
rdfs:label "service product"@en ;
rdfs:comment "An immaterial entity that provides value through a service offering, delivering intangible benefits or functionality designed to fulfill specific needs or requirements, often in a structured process."@en ;
rdfs:subClassOf ns1:BFO_0000141 .
ns3:NFDI_0001101 a owl:Class ;
rdfs:label "added value textual entity",
"added value textual entity"@en ;
rdfs:comment "An added value textual entity is a textual entity that describes the achievements, benefits, or additional value generated by a project, service, or initiative, highlighting its impact, improvements, or contributions." ;
rdfs:subClassOf ns1:IAO_0000300 ;
skos:editorialNote "In responce to competency questions like what are the added values of project X1 or service X2." ;
ns3:NFDI_0010013 "https://github.com/ISE-FIZKarlsruhe/nfdicore/issues/119" .
ns1:BFO_0000015 a owl:Class ;
rdfs:label "process"@en ;
ns1:IAO_0000115 "p is a process = Def. p is an occurrent that has temporal proper parts and for some time t, p s-depends_on some material entity at t. (axiom label in BFO2 Reference: [083-003])"@en ;
dc:identifier "083-BFO" ;
rdfs:subClassOf ns1:BFO_0000003 ;
skos:altLabel "event"@en ;
skos:definition "(Elucidation) p is a process means p is an occurrent that has some temporal proper part and for some time t, p has some material entity as participant"@en ;
skos:example "An act of selling; the life of an organism; a process of sleeping; a process of cell-division; a beating of the heart; a process of meiosis; the taxiing of an aircraft; the programming of a computer"@en .
ns1:BFO_0000016 a owl:Class ;
rdfs:label "disposition"@en ;
ns1:IAO_0000112 "an atom of element X has the disposition to decay to an atom of element Y"@en,
"certain people have a predisposition to colon cancer"@en,
"children are innately disposed to categorize objects in certain ways."@en,
"the cell wall is disposed to filter chemicals in endocytosis and exocytosis"@en ;
ns1:IAO_0000116 "BFO 2 Reference: Dispositions exist along a strength continuum. Weaker forms of disposition are realized in only a fraction of triggering cases. These forms occur in a significant number of cases of a similar type."@en ;
dc:identifier "062-BFO" ;
rdfs:subClassOf ns1:BFO_0000017 ;
owl:disjointWith ns1:BFO_0000023 ;
skos:altLabel "internally-grounded realizable entity"@en ;
skos:definition "(Elucidation) A disposition b is a realizable entity such that if b ceases to exist then its bearer is physically changed & b's realization occurs when and because this bearer is in some special physical circumstances & this realization occurs in virtue of the bearer's physical make-up"@en ;
skos:example "An atom of element X has the disposition to decay to an atom of element Y; the cell wall is disposed to transport cellular material through endocytosis and exocytosis; certain people have a predisposition to colon cancer; children are innately disposed to categorize objects in certain ways"@en .
ns1:BFO_0000034 a owl:Class ;
rdfs:label "function"@en ;
ns1:IAO_0000112 "the function of a hammer to drive in nails"@en,
"the function of a heart pacemaker to regulate the beating of a heart through electricity"@en,
"the function of amylase in saliva to break down starch into sugar"@en ;
ns1:IAO_0000116 "BFO 2 Reference: In the past, we have distinguished two varieties of function, artifactual function and biological function. These are not asserted subtypes of BFO:function however, since the same function – for example: to pump, to transport – can exist both in artifacts and in biological entities. The asserted subtypes of function that would be needed in order to yield a separate monoheirarchy are not artifactual function, biological function, etc., but rather transporting function, pumping function, etc."@en ;
dc:identifier "064-BFO" ;
rdfs:subClassOf ns1:BFO_0000016 ;
skos:definition "(Elucidation) A function is a disposition that exists in virtue of its bearer's physical make-up & this physical make-up is something the bearer possesses because it came into being either through evolution (in the case of natural biological entities) or through intentional design (in the case of artefacts) in order to realize processes of a certain sort"@en ;
skos:example "The function of a hammer to drive in nails; the function of a heart pacemaker to regulate the beating of a heart through electricity"@en .
ns1:IAO_0000136 a owl:ObjectProperty ;
rdfs:label "is about"@en ;
ns1:IAO_0000112 "This document is about information artifacts and their representations"@en ;
ns1:IAO_0000115 "A (currently) primitive relation that relates an information artifact to an entity."@en ;
ns1:IAO_0000116 """7/6/2009 Alan Ruttenberg. Following discussion with Jonathan Rees, and introduction of "mentions" relation. Weaken the is_about relationship to be primitive.
We will try to build it back up by elaborating the various subproperties that are more precisely defined.
Some currently missing phenomena that should be considered "about" are predications - "The only person who knows the answer is sitting beside me" , Allegory, Satire, and other literary forms that can be topical without explicitly mentioning the topic."""@en ;
ns1:IAO_0000119 "Smith, Ceusters, Ruttenberg, 2000 years of philosophy"@en ;
rdfs:domain ns1:IAO_0000030 ;
owl:inverseOf ns3:NFDI_0000226 .
ns1:BFO_0000003 a owl:Class ;
rdfs:label "occurrent"@en ;
ns1:IAO_0000115 "An entity that has temporal parts and that happens, unfolds or develops through time."@en ;
dc:identifier "077-BFO" ;
rdfs:subClassOf ns1:BFO_0000001 ;
skos:definition "(Elucidation) An occurrent is an entity that unfolds itself in time or it is the start or end of such an entity or it is a temporal or spatiotemporal region"@en ;
skos:example "As for process, history, process boundary, spatiotemporal region, zero-dimensional temporal region, one-dimensional temporal region, temporal interval, temporal instant."@en .
ns1:BFO_0000023 a owl:Class ;
rdfs:label "role"@en ;
ns1:IAO_0000112 "John’s role of husband to Mary is dependent on Mary’s role of wife to John, and both are dependent on the object aggregate comprising John and Mary as member parts joined together through the relational quality of being married."@en,
"the priest role"@en,
"the role of a boundary to demarcate two neighboring administrative territories"@en,
"the role of a building in serving as a military target"@en,
"the role of a stone in marking a property boundary"@en,
"the role of subject in a clinical trial"@en,
"the student role"@en ;
ns1:IAO_0000115 "A realizable entity the manifestation of which brings about some result or end that is not essential to a continuant in virtue of the kind of thing that it is but that can be served or participated in by that kind of continuant in some kinds of natural, social or institutional contexts."@en ;
ns1:IAO_0000116 "BFO 2 Reference: One major family of examples of non-rigid universals involves roles, and ontologies developed for corresponding administrative purposes may consist entirely of representatives of entities of this sort. Thus ‘professor’, defined as follows,b instance_of professor at t =Def. there is some c, c instance_of professor role & c inheres_in b at t.denotes a non-rigid universal and so also do ‘nurse’, ‘student’, ‘colonel’, ‘taxpayer’, and so forth. (These terms are all, in the jargon of philosophy, phase sortals.) By using role terms in definitions, we can create a BFO conformant treatment of such entities drawing on the fact that, while an instance of professor may be simultaneously an instance of trade union member, no instance of the type professor role is also (at any time) an instance of the type trade union member role (any more than any instance of the type color is at any time an instance of the type length).If an ontology of employment positions should be defined in terms of roles following the above pattern, this enables the ontology to do justice to the fact that individuals instantiate the corresponding universals – professor, sergeant, nurse – only during certain phases in their lives."@en ;
dc:identifier "061-BFO" ;
rdfs:subClassOf ns1:BFO_0000017 ;
skos:altLabel "externally-grounded realizable entity"@en ;
skos:definition "(Elucidation) A role b is a realizable entity such that b exists because there is some single bearer that is in some special physical, social, or institutional set of circumstances in which this bearer does not have to be & b is not such that, if it ceases to exist, then the physical make-up of the bearer is thereby changed"@en ;
skos:example "The priest role; the student role; the role of subject in a clinical trial; the role of a stone in marking a property boundary; the role of a boundary to demarcate two neighbouring administrative territories; the role of a building in serving as a military target"@en .
ns1:BFO_0000031 a owl:Class ;
rdfs:label "generically dependent continuant"@en ;
ns1:IAO_0000112 "The entries in your database are patterns instantiated as quality instances in your hard drive. The database itself is an aggregate of such patterns. When you create the database you create a particular instance of the generically dependent continuant type database. Each entry in the database is an instance of the generically dependent continuant type IAO: information content entity."@en,
"the pdf file on your laptop, the pdf file that is a copy thereof on my laptop"@en,
"the sequence of this protein molecule; the sequence that is a copy thereof in that protein molecule."@en ;
ns1:IAO_0000115 "b is a generically dependent continuant = Def. b is a continuant that g-depends_on one or more other entities. (axiom label in BFO2 Reference: [074-001])"@en ;
dc:identifier "074-BFO" ;
rdfs:subClassOf ns1:BFO_0000002 ;
skos:altLabel "g-dependent continuant"@en ;
skos:definition "(Elucidation) A generically dependent continuant is an entity that exists in virtue of the fact that there is at least one of what may be multiple copies which is the content or the pattern that multiple copies would share"@en ;
skos:example "The pdf file on your laptop; the pdf file that is a copy thereof on my laptop; the sequence of this protein molecule; the sequence that is a copy thereof in that protein molecule; the content that is shared by a string of dots and dashes written on a page and the transmitted Morse code signal; the content of a sentence; an engineering blueprint"@en .
ns1:RO_0000052 a owl:FunctionalProperty,
owl:ObjectProperty ;
rdfs:label "characteristic of"@en ;
ns1:IAO_0000112 "this fragility is a characteristic of this vase"@en,
"this red color is a characteristic of this apple"@en ;
ns1:IAO_0000115 "a relation between a specifically dependent continuant (the characteristic) and any other entity (the bearer), in which the characteristic depends on the bearer for its existence."@en ;
owl:inverseOf ns1:RO_0000053 .
ns1:BFO_0000001 a owl:Class ;
rdfs:label "entity"@en ;
ns1:IAO_0000112 "Julius Caesar"@en,
"Verdi’s Requiem"@en,
"the Second World War"@en,
"your body mass index"@en ;
ns1:IAO_0000116 "BFO 2 Reference: In all areas of empirical inquiry we encounter general terms of two sorts. First are general terms which refer to universals or types:animaltuberculosissurgical procedurediseaseSecond, are general terms used to refer to groups of entities which instantiate a given universal but do not correspond to the extension of any subuniversal of that universal because there is nothing intrinsic to the entities in question by virtue of which they – and only they – are counted as belonging to the given group. Examples are: animal purchased by the Emperortuberculosis diagnosed on a Wednesdaysurgical procedure performed on a patient from Stockholmperson identified as candidate for clinical trial #2056-555person who is signatory of Form 656-PPVpainting by Leonardo da VinciSuch terms, which represent what are called ‘specializations’ in [81"@en ;
dc:identifier "001-BFO" ;
skos:definition "(Elucidation) An entity is anything that exists or has existed or will exist"@en ;
skos:example "Julius Caesar; the Second World War; your body mass index; Verdi's Requiem"@en .
ns1:BFO_0000002 a owl:Class ;
rdfs:label "continuant"@en ;
ns1:IAO_0000115 "An entity that exists in full at any time in which it exists at all, persists through time while maintaining its identity and has no temporal parts."@en ;
ns1:IAO_0000116 "BFO 2 Reference: Continuant entities are entities which can be sliced to yield parts only along the spatial dimension, yielding for example the parts of your table which we call its legs, its top, its nails. ‘My desk stretches from the window to the door. It has spatial parts, and can be sliced (in space) in two. With respect to time, however, a thing is a continuant.’ [60, p. 240"@en ;
dc:identifier "008-BFO" ;
rdfs:subClassOf ns1:BFO_0000001 ;
owl:disjointWith ns1:BFO_0000003 ;
skos:definition "(Elucidation) A continuant is an entity that persists, endures, or continues to exist through time while maintaining its identity"@en ;
skos:example "A human being; a tennis ball; a cave; a region of space; someone's temperature"@en .
ns1:BFO_0000004 a owl:Class ;
rdfs:label "independent continuant"@en ;
ns1:IAO_0000112 "a chair"@en,
"a heart"@en,
"a leg"@en,
"a molecule"@en,
"a spatial region"@en,
"an atom"@en,
"an orchestra."@en,
"an organism"@en,
"the bottom right portion of a human torso"@en,
"the interior of your mouth"@en ;
ns1:IAO_0000115 "b is an independent continuant = Def. b is a continuant which is such that there is no c and no t such that b s-depends_on c at t. (axiom label in BFO2 Reference: [017-002])"@en ;
dc:identifier "017-BFO" ;
rdfs:subClassOf ns1:BFO_0000002 ;
owl:disjointWith ns1:BFO_0000020,
ns1:BFO_0000031 ;
skos:definition "b is an independent continuant =Def b is a continuant & there is no c such that b specifically depends on c or b generically depends on c"@en ;
skos:example "An atom; a molecule; an organism; a heart; a chair; the bottom right portion of a human torso; a leg; the interior of your mouth; a spatial region; an orchestra"@en .
ns1:BFO_0000017 a owl:Class ;
rdfs:label "realizable entity"@en ;
ns1:IAO_0000112 "the disposition of this piece of metal to conduct electricity."@en,
"the disposition of your blood to coagulate"@en,
"the function of your reproductive organs"@en,
"the role of being a doctor"@en,
"the role of this boundary to delineate where Utah and Colorado meet"@en ;
ns1:IAO_0000115 "A specifically dependent continuant that inheres in continuant entities and are not exhibited in full at every time in which it inheres in an entity or group of entities. The exhibition or actualization of a realizable entity is a particular manifestation, functioning or process that occurs under certain circumstances."@en ;
dc:identifier "058-BFO" ;
rdfs:subClassOf ns1:BFO_0000020 ;
owl:disjointWith ns1:BFO_0000019 ;
skos:definition "(Elucidation) A realizable entity is a specifically dependent continuant that inheres in some independent continuant which is not a spatial region & which is of a type some instances of which are realized in processes of a correlated type"@en ;
skos:example "The role of being a doctor; the role of this boundary to delineate where Utah and Colorado meet; the function of your reproductive organs; the disposition of your blood to coagulate; the disposition of this piece of metal to conduct electricity"@en .
ns1:BFO_0000019 a owl:Class ;
rdfs:label "quality"@en ;
ns1:IAO_0000112 "the ambient temperature of this portion of air"@en,
"the color of a tomato"@en,
"the length of the circumference of your waist"@en,
"the mass of this piece of gold."@en,
"the shape of your nose"@en,
"the shape of your nostril"@en ;
dc:identifier "055-BFO" ;
rdfs:subClassOf ns1:BFO_0000020 ;
skos:definition "(Elucidation) A quality is a specifically dependent continuant that, in contrast to roles and dispositions, does not require any further process in order to be realized"@en ;
skos:example "The colour of a tomato; the ambient temperature of this portion of air; the length of the circumference of your waist; the shape of your nose; the shape of your nostril; the mass of this piece of gold"@en .
ns1:BFO_0000020 a owl:Class ;
rdfs:label "specifically dependent continuant"@en ;
ns1:IAO_0000112 "Reciprocal specifically dependent continuants: the function of this key to open this lock and the mutually dependent disposition of this lock: to be opened by this key"@en,
"of one-sided specifically dependent continuants: the mass of this tomato"@en,
"of relational dependent continuants (multiple bearers): John’s love for Mary, the ownership relation between John and this statue, the relation of authority between John and his subordinates."@en,
"the disposition of this fish to decay"@en,
"the function of this heart: to pump blood"@en,
"the mutual dependence of proton donors and acceptors in chemical reactions [79"@en,
"the mutual dependence of the role predator and the role prey as played by two organisms in a given interaction"@en,
"the pink color of a medium rare piece of grilled filet mignon at its center"@en,
"the role of being a doctor"@en,
"the shape of this hole."@en,
"the smell of this portion of mozzarella"@en ;
ns1:IAO_0000115 "b is a specifically dependent continuant = Def. b is a continuant & there is some independent continuant c which is not a spatial region and which is such that b s-depends_on c at every time t during the course of b’s existence. (axiom label in BFO2 Reference: [050-003])"@en ;
dc:identifier "050-BFO" ;
rdfs:subClassOf ns1:BFO_0000002 ;
owl:disjointWith ns1:BFO_0000031 ;
skos:definition "b is a specifically dependent continuant =Def b is a continuant & there is some independent continuant c which is not a spatial region & which is such that b specifically depends on c"@en ;
skos:example "(with multiple bearers) John's love for Mary; the ownership relation between John and this statue; the relation of authority between John and his subordinates"@en,
"(with one bearer) The mass of this tomato; the pink colour of a medium rare piece of grilled filet mignon at its centre; the smell of this portion of mozzarella; the disposition of this fish to decay; the role of being a doctor; the function of this heart to pump blood; the shape of this hole"@en .
ns1:IAO_0000030 a owl:Class ;
rdfs:label "information content entity",
"information content entity"@en ;
ns1:IAO_0000112 "Examples of information content entites include journal articles, data, graphical layouts, and graphs.",
"Examples of information content entites include journal articles, data, graphical layouts, and graphs."@en ;
ns1:IAO_0000115 "An information content entity is an entity that is generically dependent on some artifact and stands in relation of aboutness to some entity.",
"A generically dependent continuant that is about some thing."@en ;
ns1:IAO_0000116 "2014-03-10: The use of \"thing\" is intended to be general enough to include universals and configurations (see https://groups.google.com/d/msg/information-ontology/GBxvYZCk1oc/-L6B5fSBBTQJ)."@en,
"""information_content_entity 'is_encoded_in' some digital_entity in obi before split (040907). information_content_entity 'is_encoded_in' some physical_document in obi before split (040907).
Previous. An information content entity is a non-realizable information entity that 'is encoded in' some digital or physical entity."""@en ;
ns1:IAO_0000119 "IAO",
"OBI_0000142"@en ;
rdfs:subClassOf [ a owl:Restriction ;
owl:onProperty ns1:IAO_0000136 ;
owl:someValuesFrom ns1:BFO_0000001 ],
ns1:BFO_0000031 .
ns1:IAO_0000300 a owl:Class ;
rdfs:label "textual entity"@en ;
ns1:IAO_0000112 "Words, sentences, paragraphs, and the written (non-figure) parts of publications are all textual entities"@en ;
ns1:IAO_0000115 "A textual entity is a part of a manifestation (FRBR sense), a generically dependent continuant whose concretizations are patterns of glyphs intended to be interpreted as words, formulas, etc."@en ;
ns1:IAO_0000116 "AR, (IAO call 2009-09-01): a document as a whole is not typically a textual entity, because it has pictures in it - rather there are parts of it that are textual entities. Examples: The title, paragraph 2 sentence 7, etc."@en,
"MC, 2009-09-14 (following IAO call 2009-09-01): textual entities live at the FRBR (http://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records) manifestation level. Everything is significant: line break, pdf and html versions of same document are different textual entities."@en ;
ns1:IAO_0000118 "text"@en ;
rdfs:subClassOf ns1:IAO_0000030 .
a ns2:Variable .
ns1:RO_0000053 a owl:InverseFunctionalProperty,
owl:ObjectProperty ;
rdfs:label "has characteristic"@en ;
ns1:IAO_0000112 "this apple is bearer of this red color"@en,
"this vase is bearer of this fragility"@en ;
ns1:IAO_0000115 "Inverse of characteristic_of"@en ;
ns1:IAO_0000116 "A bearer can have many dependents, and its dependents can exist for different periods of time, but none of its dependents can exist when the bearer does not exist."@en ;
rdfs:range ns1:BFO_0000020 .
a ns2:Variable .
[] a owl:AllDisjointClasses ;
owl:members ( ns1:BFO_0000004 ns1:BFO_0000020 ns1:BFO_0000031 ) .
[] a ns2:Imp ;
ns2:body [ a ns2:AtomList ;
rdf:first [ a ns2:IndividualPropertyAtom ;
ns2:argument1 ;
ns2:argument2 ;
ns2:propertyPredicate ns1:RO_0000053 ] ;
rdf:rest [ a ns2:AtomList ;
rdf:first [ a ns2:ClassAtom ;
ns2:argument1 ;
ns2:classPredicate ns1:BFO_0000016 ] ;
rdf:rest () ] ] ;
ns2:head [ a ns2:AtomList ;
rdf:first [ a ns2:IndividualPropertyAtom ;
ns2:argument1 ;
ns2:argument2 ;
ns2:propertyPredicate ns1:RO_0000091 ] ;
rdf:rest () ] .
[] a ns2:Imp ;
ns2:body [ a ns2:AtomList ;
rdf:first [ a ns2:IndividualPropertyAtom ;
ns2:argument1 ;
ns2:argument2 ;
ns2:propertyPredicate ns1:RO_0000053 ] ;
rdf:rest [ a ns2:AtomList ;
rdf:first [ a ns2:ClassAtom ;
ns2:argument1 ;
ns2:classPredicate ns1:BFO_0000019 ] ;
rdf:rest () ] ] ;
ns2:head [ a ns2:AtomList ;
rdf:first [ a ns2:IndividualPropertyAtom ;
ns2:argument1 ;
ns2:argument2 ;
ns2:propertyPredicate ns1:RO_0000086 ] ;
rdf:rest () ] .
[] a ns2:Imp ;
ns2:body [ a ns2:AtomList ;
rdf:first [ a ns2:IndividualPropertyAtom ;
ns2:argument1 ;
ns2:argument2 ;
ns2:propertyPredicate ns1:RO_0000053 ] ;
rdf:rest [ a ns2:AtomList ;
rdf:first [ a ns2:ClassAtom ;
ns2:argument1 ;
ns2:classPredicate ns1:BFO_0000023 ] ;
rdf:rest () ] ] ;
ns2:head [ a ns2:AtomList ;
rdf:first [ a ns2:IndividualPropertyAtom ;
ns2:argument1 ;
ns2:argument2 ;
ns2:propertyPredicate ns1:RO_0000087 ] ;
rdf:rest () ] .
[] a ns2:Imp ;
ns2:body [ a ns2:AtomList ;
rdf:first [ a ns2:IndividualPropertyAtom ;
ns2:argument1 ;
ns2:argument2 ;
ns2:propertyPredicate ns1:RO_0000053 ] ;
rdf:rest [ a ns2:AtomList ;
rdf:first [ a ns2:ClassAtom ;
ns2:argument1 ;
ns2:classPredicate ns1:BFO_0000034 ] ;
rdf:rest () ] ] ;
ns2:head [ a ns2:AtomList ;
rdf:first [ a ns2:IndividualPropertyAtom ;
ns2:argument1 ;
ns2:argument2 ;
ns2:propertyPredicate ns1:RO_0000085 ] ;
rdf:rest () ] .