Core Ontology for Petroleum Installations · INF-UFRGS-Ontologies · CNPq INF-UFRGS-ENERGIA inf.ufrgs.br/ontologies/copi dee69df
exported necessary
pipe
IRI: http://www.inf.ufrgs.br/ontologies/copi#Pipe
Generated on 2026-04-13
Natural Language Definition
EN
A pipe is a material artifact characterized by tubular geometry and longitudinal extent, designed to conduct liquid, gaseous or finely divided solid materials from one location to another, or to serve structural purposes.
PT-BR
Um tubo é um artefato material caracterizado por geometria tubular e extensão longitudinal, projetado para conduzir materiais líquidos, gasosos ou sólidos finamente divididos de um local para outro, ou para servir a propósitos estruturais.
Formal Axioms
Semi-formal (Aristotelian)
Every pipe is a material artifact that has fluid conduction function and has tubular geometry and has longitudinal extent.
First-Order Logic Theory
Loading…
▸ Stored override ∀x(Pipe(x) → MaterialArtifact(x) ∧ ∃f(FluidConductionFunction(f) ∧ hasFunction(x,f)) ∧ ∃g(TubularGeometry(g) ∧ hasPhysicalProperty(x,g)) ∧ ∃h(LongitudinalExtent(h) ∧ hasPhysicalProperty(x,h)))
OWL 2 / Turtle
@prefix copi: <https://www.inf.ufrgs.br/ontologies/copi/> . @prefix : <https://www.inf.ufrgs.br/ontologies/copi/> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix bfo: <http://purl.obolibrary.org/obo/> . @prefix iof-core: <https://spec.industrialontologies.org/ontology/construct/> . @prefix iof-av: <https://spec.industrialontologies.org/ontology/annotation/> . @prefix skos: <http://www.w3.org/2004/02/skos/core#> . @prefix qudt: <http://qudt.org/schema/qudt/> . @prefix dcterms: <http://purl.org/dc/terms/> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix apv: <http://inf.ufrgs.br/ontologies/apv#> . ### COPI — Core Ontology for Petroleum Installations ### Class module: Pipe <https://www.inf.ufrgs.br/ontologies/copi> rdf:type owl:Ontology ; dcterms:title "Core Ontology for Petroleum Installations (COPI)"@en ; dcterms:title "Ontologia Core para Instalações de Petróleo (COPI)"@pt-br ; dcterms:description "BFO/IOF-Core conformant ontology of equipment classes for petroleum production plants, developed using the five-step RDL enrichment method."@en ; skos:scopeNote "Material artifacts (bfo:material_entity) that (i) are part of a petroleum production plant, and (ii) bear at least one function whose realization involves the transport (e.g. production and injection), processing (separation and other processes), control, monitoring, measurement, containment or offloading of material or energy."@en ; skos:scopeNote "Artefatos materiais (bfo:material_entity) que (i) fazem parte de uma planta de produção de petróleo, e (ii) possuem ao menos uma função cuja realização envolve o transporte (p. ex. produção e injeção), processamento (separação e outros processos), controle, monitoramento, medição, contenção ou escoamento de material ou energia."@pt-br ; skos:scopeNote "COPI provides high-level equipment categories defined by function to demonstrate the defined-class mechanism. Equipment subtypes are annotated with references to CFIHOS and PCA RDL terms. COPI is not a reference data library; organizations should use CFIHOS, PCA RDL, or ISO 14224 for comprehensive equipment classification."@en ; skos:scopeNote "COPI fornece categorias de alto nível de equipamentos definidas por função para demonstrar o mecanismo de classe definida. Os subtipos de equipamentos são anotados com referências aos termos do CFIHOS e do PCA RDL. COPI não é uma biblioteca de dados de referência; organizações devem utilizar o CFIHOS, o PCA RDL ou a ISO 14224 para classificação abrangente de equipamentos."@pt-br ; owl:versionInfo "1.1.0" ; owl:imports <https://spec.industrialontologies.org/ontology/core/Core/> ; owl:imports <http://purl.obolibrary.org/obo/bfo/2020/bfo.owl> ; dcterms:creator "Nicolau Oyhenard dos Santos"@en ; dcterms:contributor "Cauã Antunes" ; dcterms:contributor "Haroldo Rojas" ; dcterms:contributor "Rafael Petry" ; dcterms:contributor "Régis Romeu" ; dcterms:contributor "Mara Abel" ; dcterms:isPartOf <https://inf.ufrgs.br/projetos/OntoKG> ; dcterms:publisher "Universidade Federal do Rio Grande do Sul (UFRGS)"@en ; dcterms:license <https://creativecommons.org/licenses/by/4.0/> ; dcterms:created "2026-04-08"^^xsd:date ; dcterms:modified "2026-10-08"^^xsd:date ; apv:GlobalMinLanguageCoverage "en pt-br" ; apv:ClassURIFormationRule "https://www[.]inf[.]ufrgs[.]br/ontologies/copi/(COPI_[0-9]{7}|[A-Z][A-Za-z0-9]*)" ; apv:ClassMinAnnotationCoverage "rdfs:label https://spec.industrialontologies.org/ontology/annotation/naturalLanguageDefinition" . iof-av:naturalLanguageDefinition rdf:type owl:AnnotationProperty ; apv:MinAnnotationLength 20 . ### Identity-giving function :COPI_0000529 rdf:type owl:Class ; # FluidConductionFunction rdfs:subClassOf iof-core:DesignedFunction ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty bfo:BFO_0000054 ; # realizedIn owl:allValuesFrom :COPI_0000530 # FluidConductionProcess ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty bfo:BFO_0000054 ; # realizedIn owl:someValuesFrom :COPI_0000530 # FluidConductionProcess ] ; rdfs:label "fluid conduction function"@en ; rdfs:label "função de condução de fluido"@pt-br . ### Process type :COPI_0000530 rdf:type owl:Class ; # FluidConductionProcess rdfs:subClassOf :COPI_0000003 ; # MomentumTransfer rdfs:label "fluid conduction process"@en ; rdfs:label "processo de condução de fluido"@pt-br . :COPI_0000003 rdf:type owl:Class . # MomentumTransfer :COPI_0000530 # FluidConductionProcess rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasInput ; owl:someValuesFrom :COPI_0000037 # PortionOfFluid ] ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasSpecifiedOutput ; owl:someValuesFrom :COPI_0000037 # PortionOfFluid ] . ### Equipment universal: Pipe :COPI_0000321 rdf:type owl:Class ; # Pipe rdfs:subClassOf iof-core:MaterialArtifact ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty iof-core:hasFunction ; # Object branch (MaterialArtifact/Assembly/Object/FiatObjectPart) owl:someValuesFrom :COPI_0000529 # FluidConductionFunction ] ; rdfs:label "pipe"@en ; rdfs:label "tubo"@pt-br ; iof-av:naturalLanguageDefinition "A pipe is a material artifact characterized by tubular geometry and longitudinal extent, designed to conduct liquid, gaseous or finely divided solid materials from one location to another, or to serve structural purposes."@en ; skos:definition "A pipe is a material artifact characterized by tubular geometry and longitudinal extent, designed to conduct liquid, gaseous or finely divided solid materials from one location to another, or to serve structural purposes."@en ; iof-av:naturalLanguageDefinition "Um tubo é um artefato material caracterizado por geometria tubular e extensão longitudinal, projetado para conduzir materiais líquidos, gasosos ou sólidos finamente divididos de um local para outro, ou para servir a propósitos estruturais."@pt-br ; iof-av:semiFormalNaturalLanguageAxiom "Every pipe is a material artifact that has fluid conduction function and has tubular geometry and has longitudinal extent."@en ; iof-av:firstOrderLogicAxiom "∀x(Pipe(x) → MaterialArtifact(x) ∧ ∃f(FluidConductionFunction(f) ∧ hasFunction(x,f)) ∧ ∃g(TubularGeometry(g) ∧ hasPhysicalProperty(x,g)) ∧ ∃h(LongitudinalExtent(h) ∧ hasPhysicalProperty(x,h)))"@en ; iof-av:isPrimitive "true"^^xsd:boolean ; iof-av:primitiveRationale "Using necessary conditions because pipe is defined by constructive/geometric properties (tubular geometry, longitudinal extent) rather than purely functional criteria. Under Open World Assumption, asserting sufficient conditions based on geometric properties could lead to unintended classification of complex tubular structures that happen to conduct fluids but should not be categorized as standard pipes."@en ; skos:definition "[ISO 15926-4] A <PIPE> is an <ARTEFACT> and a <FLUID CONDUCTOR> that is a long tube or hollow body intended for conduction of liquid, gaseous or finely divided solid materials, or used for structural purposes"@en ; skos:definition "[CFIHOS] A physical object that is a long tube or hollow body intended for conduction of liquid, gaseous or finely divided solid materials, or used for structural purposes."@en ; skos:definition "[DEXPI] An elementary piece of piping, i.e., not interrupted by any item."@en ; skos:definition "[POSC Caesar] An 'artefact' that is a long tube or hollow body intended for conduction of liquid, gaseous or finely divided solid materials, or used for structural purposes."@en . # Disjointness: Pipe and Valve [] rdf:type owl:AllDisjointClasses ; owl:members ( :COPI_0000321 :COPI_0000077 ) . # Pipe, Valve # Disjointness: Pipe and Pump [] rdf:type owl:AllDisjointClasses ; owl:members ( :COPI_0000321 :COPI_0000072 ) . # Pipe, Pump # Disjointness: Pipe and Compressor [] rdf:type owl:AllDisjointClasses ; owl:members ( :COPI_0000321 :COPI_0000073 ) . # Pipe, Compressor
Axiomatization Decision Log
1 Identity-Giving Function
Function class
FluidConductionFunction ⊑ DesignedFunction
Realized in
FluidConductionProcess ⊑ MomentumTransfer
While pipes can serve structural purposes, their primary and most common designed function is fluid conduction - providing a pathway for liquid, gaseous or finely divided solid materials. This is the most general function that encompasses the majority of pipe applications.
2 Genus Determination
MaterialArtifact bfo:Object (BFO_0000030)

Monolithic causally unified material artefact. MaterialArtifact ≡ Object ⊓ ∃bearerOf.DesignedFunction.

Pipe represents a fundamental category of industrial equipment without a more specific superclass in our current ontology. While FLUID CONDUCTOR appears in the source hierarchies, it is not present in our enriched classes. A pipe is a causally unified material artifact - a single physical object that can be manufactured, transported, installed, and maintained as one unit. It lacks the complex removable subcomponents that would make it an Assembly.
3 Necessary Parts

No necessary parts recorded (concept may be primitive at this level).

These are the minimal essential parts that make a pipe a pipe - the wall structure and the hollow interior. End connections, fittings, or supports are not universal requirements.
4 Process Participation Signature ⟨I, O, T⟩
Inputs (I)
PortionOfFluid — enters at one end
Outputs (O)
PortionOfFluid — exits at other end, same composition
Transformation (T)
spatial transport without chemical or phase change
A pipe provides a conduit for fluid transport from one location to another without altering the fluid's properties. The signature is minimal - one input stream, one output stream, no transformation beyond spatial displacement.
5 Axiom Mode Decision

Necessary conditions only — modelled as a primitive universal (⊑, SubClassOf). Identity is grounded in designed function and cannot be reduced to a property checklist.

Using necessary conditions because pipe is defined by constructive/geometric properties (tubular geometry, longitudinal extent) rather than purely functional criteria. Under Open World Assumption, asserting sufficient conditions based on geometric properties could lead to unintended classification of complex tubular structures that happen to conduct fluids but should not be categorized as standard pipes.
Disjointness Axioms
Valve Pump Compressor
C4: Valve, Pump, Compressor. These classes have fundamentally different process signatures - valves control/regulate flow, pumps add energy to fluids, compressors change fluid density. Their active transformation functions are incompatible with pipe's passive transport signature.
Cross-Standard Observations
All sources consistently define pipe as a tubular/hollow body for fluid conduction. ISO 15926 and POSC Caesar explicitly mention structural uses. DEXPI focuses on the elementary/uninterrupted aspect, emphasizing pipe as a basic building block. Minor variation in whether structural purpose is primary or secondary function.

Suggest a change

Opens a pre-filled GitHub issue on the COPI repo — nothing is sent until you submit it there.