Looking at the example RDF, I'm pasting here the Line Number, its line class and its pipe size.
Code: Select all
<owl:Thing rdf:ID="T6af670ff-67b6-11e1-b86c-0800200c9a66"> <!-- Line has Line Number -->
<rdf:type rdf:resource="&p7tpl;ClassifiedIdentificationOfClass"/>
<p7tpl:hasUrClass rdf:resource="#Ce269d540-678a-11e1-b86c-0800200c9a66"/> <!-- line RZ17801 -->
<p7tpl:hasIdentified rdf:resource="#Cc8873cc1-dbc2-11e1-9b23-0800200c9a66"/>
<p7tpl:valIdentifier rdf:datatype="&xsd;string">RZ17801</p7tpl:valIdentifier>
<p7tpl:hasIdentificationType rdf:resource="&xyzrdl;Ce269fc64-678a-11e1-b86c-0800200c9a66"/> <!-- XYZ Corp. Tag Numbering System -->
</owl:Thing>
<owl:Thing rdf:ID="T6af67106-67b6-11e1-b86c-0800200c9a66"> <!-- Line is member of a Pipe Class -->
<rdf:type rdf:resource="&p7tpl;ClassificationOfClass"/>
<p7tpl:hasUrClass rdf:resource="#Ce269d540-678a-11e1-b86c-0800200c9a66"/> <!-- Line RZ17801 -->
<p7tpl:hasSubClass rdf:resource="#Cc8878ad9-dbc2-11e1-9b23-0800200c9a66"/>
<p7tpl:hasSuperClass rdf:resource="&xyzrdl;Ce269fc6f-678a-11e1-b86c-0800200c9a66"/> <!-- H191K01PG -->
</owl:Thing>
<owl:Thing rdf:ID="T6af67109-67b6-11e1-b86c-0800200c9a66"> <!-- Line segment1 has a Size -->
<rdf:type rdf:resource="&p7tpl;ClassOfIndirectPropertyWithPointValue"/>
<p7tpl:hasUrClass rdf:resource="#Ce269fc50-678a-11e1-b86c-0800200c9a66"/> <!-- Line RZ17801 segment1 -->
<p7tpl:hasPossessorType rdf:resource="#Cc88763d4-dbc2-11e1-9b23-0800200c9a66"/>
<p7tpl:hasDefined rdf:resource="#C7bac7150-8cba-11e1-b0c4-0800200c9a66"/> <!-- referred to by member relationship -->
<p7tpl:hasIndirectPropertyType rdf:resource="&rdl;R17622148043"/> <!-- Nominal Diameter -->
<p7tpl:hasBasePropertyType rdf:resource="&rdl;R32277183282"/> <!-- Length -->
<p7tpl:valPointValue rdf:datatype="&xsd;float">3</p7tpl:valPointValue>
<p7tpl:hasScale rdf:resource="&rdl;R34755432270"/> <!-- inch -->
<p7tpl:hasPossessorCardinality rdf:resource="&xyzrdl;Ce269fc71-678a-11e1-b86c-0800200c9a66"/>
</owl:Thing>
2. Why is the nominal pipe size a point value? Isn't nominal pipe size a class, just like pipe class? Eventually, when we have all our ducks in a row, the nominal pipe size is an address in the DIN server (in case of DN sizes, API and ASTM in case of inches).
3. Is the line an assembly of pipe segments? In the OIM, the nominal pipe sizes are in an n-ary relation with the pipe segment designation. Pipe segments are not objects. Instead, shouldn't a pipe segment just have its own OIM with nominal size as a property?