Re: TIPs revisited
Posted: Fri Aug 01, 2014 8:07 am
Now we have reached this point, I want to re-emphasize the need for generic patterns.
In this case these generic patterns would be ClassifiedPartOfClassOfAssembly and ClassifiedPartOfAssembly, or something like that.
ClassifiedPartOfClassOfAssembly(OOI, PartType) ↔
ClassOfInanimatePhysicalObject(OOI) ∧
ClassOfInanimatePhysicalObject(Part) ∧
ClassOfInanimatePhysicalObject(PartType) ∧
ClassOfAssemblyDefinition(OOI, Part, RDS_new_0007, RDS_new_0007) ∧
SpecializationOfClassOfIndividual(Part, PartType) ∧
SpecializationOfClassOfIndividual(PartType, RDS892484261) .
Using this information the class of part can be declared:
:C1719c380-1950-11e4-8c21-0800200c9a66 rdf:type dm:ClassOfInanimatePhysicalObject, owl:Class ;
rdfs:subClassOf rdl:RDS892484261 .
ClassifiedPartOfAssembly(OOI, PartType) ↔
PhysicalObject(OOI) ∧
PhysicalObject(Part) ∧
ClassOfInanimatePhysicalObject(PartType) ∧
AssemblyOfAnIndividual(OOI, Part) ∧
ClassificationOfIndividual(Part, PartType) ∧
SpecializationOfClassOfIndividual(PartType, RDS892484261) .
Using this information the part can be declared:
:T32e2a5f0-1950-11e4-8c21-0800200c9a66 rdf:type dm:WholeLifeIndividual, dm:PhysicalObject, rdl:RDS892484261, owl:Class .
(if the individual "can be kicked" then add: dm:ActualIndividual)
NOTE - Do NOT instantiate this generic pattern as such, because its information would be too shallow, since the part type is ISO 15926-4 INANIMATE PHYSICAL OBJECT.
Always create a specialization and use that and give it a name that can be understood by an engineer who does (or advises in) the mapping.
For example a German engineer might see: OOI-hat-einen-Stellantriebstyp(OOI,PartType)
Whether the Class version or the Individual version applies is to be determined by the applicable LifecycleActivity, which often can be derived from the originating application of which data are to be mapped.
Such specializations are locally defined and should normally not be standardized or shared as a pattern, but shared only in the form of the resulting Part 8 file.
IMPLEMENTERS: PLEASE CONCUR OR COME FORWARD WITH A BETTER SOLUTION.
In this case these generic patterns would be ClassifiedPartOfClassOfAssembly and ClassifiedPartOfAssembly, or something like that.
ClassifiedPartOfClassOfAssembly(OOI, PartType) ↔
ClassOfInanimatePhysicalObject(OOI) ∧
ClassOfInanimatePhysicalObject(Part) ∧
ClassOfInanimatePhysicalObject(PartType) ∧
ClassOfAssemblyDefinition(OOI, Part, RDS_new_0007, RDS_new_0007) ∧
SpecializationOfClassOfIndividual(Part, PartType) ∧
SpecializationOfClassOfIndividual(PartType, RDS892484261) .
Using this information the class of part can be declared:
:C1719c380-1950-11e4-8c21-0800200c9a66 rdf:type dm:ClassOfInanimatePhysicalObject, owl:Class ;
rdfs:subClassOf rdl:RDS892484261 .
ClassifiedPartOfAssembly(OOI, PartType) ↔
PhysicalObject(OOI) ∧
PhysicalObject(Part) ∧
ClassOfInanimatePhysicalObject(PartType) ∧
AssemblyOfAnIndividual(OOI, Part) ∧
ClassificationOfIndividual(Part, PartType) ∧
SpecializationOfClassOfIndividual(PartType, RDS892484261) .
Using this information the part can be declared:
:T32e2a5f0-1950-11e4-8c21-0800200c9a66 rdf:type dm:WholeLifeIndividual, dm:PhysicalObject, rdl:RDS892484261, owl:Class .
(if the individual "can be kicked" then add: dm:ActualIndividual)
NOTE - Do NOT instantiate this generic pattern as such, because its information would be too shallow, since the part type is ISO 15926-4 INANIMATE PHYSICAL OBJECT.
Always create a specialization and use that and give it a name that can be understood by an engineer who does (or advises in) the mapping.
For example a German engineer might see: OOI-hat-einen-Stellantriebstyp(OOI,PartType)
Whether the Class version or the Individual version applies is to be determined by the applicable LifecycleActivity, which often can be derived from the originating application of which data are to be mapped.
Such specializations are locally defined and should normally not be standardized or shared as a pattern, but shared only in the form of the resulting Part 8 file.
IMPLEMENTERS: PLEASE CONCUR OR COME FORWARD WITH A BETTER SOLUTION.