This will need some time, because you put forward big issues, but not about the question we had in this thread: Would Bentley oppose a situation in which the intermediate OOIs, like stream, would be in the signature of the TIP, together with those "parameters". Please let us know.
This does not mean that I try to escape from your questions.
As you can see from http://www.15926.org/publications/templ ... IP0002.htm the use of an existential quantifier ∃u means that any intermediate OOI has to be declared automatically by the mapping software.
For your INLET PRESSURE = 120 psig that could be:
Code: Select all
:C525306c0-1746-11e4-8c21-0800200c9a66 rdf:type dm:ClassOfInanimatePhysicalObject, owl:Class ; rdfs:subClassOf rdl:RDS398549 ; # fake ID for ISO 15926-4 STREAM CLASS meta:valEffectiveDate "2014-07-10T00:00:00Z"^^xsd:dateTime .
That shouldn't be too difficult, since all ingredients are there. Then you do have your stream, that you may or may not give a tag. If not, you use the UUID (or something else). You, or we, might add a rule for the generation of a template that tells, in the case of your INLET PRESSURE, that the stream at the relative location of the inlet port is meant. Something like:
Code: Select all
:T525306c1-1746-11e4-8c21-0800200c9a66 rdf:type tpl:ClassOfRelativeLocationDefinition, owl:Thing ; skos:prefLabel "A member of CO_P-11100A_S is contained in a member of CO_P-11100A." ; tpl:hasClassOfLocated :C525306c0-1746-11e4-8c21-0800200c9a66 ; # above declared stream class tpl:hasClassOfLocator :CO_P-11100A-INLETPORT ; tpl:hasLocationType rdl:RDS459835 ; # fake ID for UPSTREAM tpl:hasCardinalityOfLocated rdl:RDS_new_007 ; # 1:1 tpl:hasCardinalityOfLocator rdl:RDS_new_007 ; # 1:1 meta:hasLifecycleActivity rdl:RDS9704537 ; # MECHANICAL ENGINEERING meta:valEffectiveDate "2014-05-28T11:25:00+00:00"^^xsd:dateTime .
The use of ports is another story, that we have to finish, one way or the other.
Your task would be to remember that relationship, because when INLET TEMPERATURE = 68 degF comes along, you better use the above, rather than creating duplicates. NOTE - The stream at the outlet is a different thing, with its own UUID. These IDs are immutable, all time-related stuff sits inside the template instances.
Let us discuss the other stuff: 1) Lists and arrays, and 2) NULL values, from your posting in separate topics. I will take the action.