From Odp

Jump to: navigation, search

This is a property of type Text.

Pages using the property "ArchitecturalODPExample"

Showing 13 pages using this property.


Class Union +Exemple in the alignment language RDF/XML Exemple in the alignment language RDF/XML syntax: <Cell> <entity1> <Class> <or rdf:ParseType="Collection"> <Class rdf:about="O1:PersonBornInCanada"/> <Class rdf:about="O1:PersonWithCanadianParent"/> </or> </Class> </entity1> <entity2> <Class rdf:about="O2:CanadianCitizenByBirth"/> </entity2> <relation>equivalence</relation> </Cell> quivalence</relation> </Cell>
Class by attribute occurence +<Cell> <entity1> <Clas <Cell> <entity1> <Class> <and> <Class rdf:about="o1:Human"> </and> <and> <AttributeOccurenceCondition> <onAttribute> <Property rdf:about="o1:hasMedal"/> </onAttribute> </AttributeOccurenceCondition> </and> </Class> </entity1> <entity2> <Class rdf:about="o2:Champion"/> </entity2> </Cell> on"/> </entity2> </Cell>
Class by attribute type +<Cell> <entity1> <Clas <Cell> <entity1> <Class> <and> <Class rdf:about="o1:Human"/> </and> <and> <AttributeTypeCondition> <onAttribute> <Relation rdf:about="o1:culturalGroup"/> </onAttribute> <value><Instance rdf:about="o1:WesternEurope"></value> </AttributeTypeCondition> </and> </Class> </entity1> <entity2> <Class rdf:about="o2:WesternEuropean"/> </entity2> </Cell> an"/> </entity2> </Cell>
Class by attribute value +Example in EDOAL: <Cell> <enti Example in EDOAL: <Cell> <entity1> <Class> <and> <Class rdf:about="vin:Vin"> </and> <and> <AttributeValueCondition> <onAttribute> <Property rdf:about="vin:terroir"/> </onAttribute> <comparator>xsd:Equal</comparator> <value>geo:Bordelais</value> </AttributeValueCondition> </and> </Class> </entity1> <entity2> <Class rdf:about="wine:BordeauxWine"/> </entity2> </Cell> ne"/> </entity2> </Cell>
Class by path attribute value +Example correspondence: <Cell> & Example correspondence: <Cell> <entity1> <Class> <and> <Class rdf:about="o1 :Person"/> <AttributeValueCondition> <onAttribute> <Property> <first> <Relation rdf:about="o1 :workplace"/> </first> <next> <Property> <first> <Relation rdf:about="o1 :address"/> </first> <next> <Property rdf:about="o1 :city"/></next> </next> </Property> </next> </Property> </onAttribute> <comparator rdf:resource="xsd:not-equal"/> <value> <Property> <first> <Relation rdf:about="o1 :address"/> </first> <next> <Property rdf:about="o1 :city"/> </next> </Property> </value> </AttributeValueCondition> </and> </Class> </entity1> <entity2> <Class rdf:about="o2 :Commuter"> </entity2> </Cell> ter"> </entity2> </Cell>
Class correspondence defined by relation domain +<Cell> <entity1> <Cla <Cell> <entity1> <Class rdf:about="o1:Parent"/> </entity1> <entity2> <Class> <and> <Class rdf:about="o2:Animal"> </and> <and> <AttributeOccurenceCondition> <onAttribute> <Relation rdf:about="o2:children"/> </onAttribute> <AttributeOccurenceCondition> </and> </Class> </entity2> <relation>subsumption</relation> </Cell> ubsumption</relation> </Cell>
Class equivalence +Example solution in the ontology alignment Example solution in the ontology alignment language: <Cell> <entity1><Class rdf:about="O1:Human"/></entity1> <entity2><Class rdf:about="O2:Person"/></entity2> <relation>equivalence</relation> </Cell> quivalence</relation> </Cell>
Class intersection +Example solution in the ontology alignment Example solution in the ontology alignment language: <Cell> <entity1> <Class> <and rdf:ParseType="Collection"> <Class rdf:about="o1:Human"/> <Class rdf:about="o1:FemaleAnimal/> </and> </Class> </entity1> <entity2> <Class rdf:about="o2:HumanFemale"/> </entity2> <relation>equivalence</relation> </Cell> quivalence</relation> </Cell>
Class subsumption +Example solution in the ontology alignment Example solution in the ontology alignment language: <Cell> <entity1><Class rdf:about="O1:Mammal"/></entity1> <entity2><Class rdf:about="O2:Vertebrate"/></entity2> <relation>subsumedBy</relation> </Cell> subsumedBy</relation> </Cell>


Disjoint Classes +Example in EDOAL, the expressive and decla Example in EDOAL, the expressive and declarative ontology alignment language <Cell> <entity1><Class rdf:about="O1:Top"/></entity1> <entity2><Class rdf:about="O2:Top"/></entity2> <relation>Disjoint</relation> </Cell> t;Disjoint</relation> </Cell>


Spatial Graph Adapter Pattern (moved to Content ODPs) +Example Problem Question: What Building Co Example Problem Question: What Building Components are adjacent to this Space (Both creating enclosure or not creating enclosure)? Even if we use a common definition for adjacency, such as where two objects would be touching could be considered adjacent, this fails when we want to know, say what columns or walls are adjacent to a space. It is true that they may be touching some building geometries, but what about the cases where you would have adjacent columns, but they are touching only the open air that define that side of a space (not touching but still on that visual or schema induced boundary)? n that visual or schema induced boundary)?


View Inheritance +Figure above in particular, shows a matrix Figure above in particular, shows a matrix representation of all types of faults which may affect a system during its life. Implicitly, the figure reveals several alternative criteria for the classification of faults: * A first criterion can be derived from the left column of the matrix (listing the basic view points from Figure 2: ''Development/Operational Faults'', ''Internal/External Faults'' and so on). This column represents the values of the eight basic viewpoints which lead to the elementary fault classes. * A second criterion can be abstracted from the bottom row (listing numbers 1 to 31). This row represents the 31 likely combinations of fault classes out of the 256 possible. * A third criterion is implicit at the top row, representing the three major partially overlapping groupings of faults: ''Development'', ''Physical'' and ''Interaction''. * A fourth criterion can be seen at the bottom row, labeled ''Examples'', containing nine illustrative examples of fault classes. ne illustrative examples of fault classes.
Vocabulary Alignment Pattern: Subclass of an external Class +The pattern "Subclass of a external Class" is used, in the SIOC vocabulary to align the classes sioc:UserAccount and foaf:OnlineAccount. Instances of a so inferred class are a subset of the instances of the class of the external vocabulary.
Personal tools
Quality Committee
Content OP publishers