IdentifierRelationStructure

Package: 
Extends: 
Is Abstract: 
no
Is Pattern: 
no
Definition: 

IdentifierOrder is useful in specifying the organization of a compound or, again, a composite key. A Viewpoint has a composite key when several instance variables are associated with the IdentifierRole.

An IdentiferRole may have one or more IdentifierOrders. This situation occurs when the composition of a composite key is variable depending on the instance variables.

Example: 
The US Census GEOID is a good example of both a composite key and a key that is variable. Indeed, the GEOID is actually a family of composite keys where the instance variables that participate in the composition vary. In general the GEOID code contains many levels of geography. However, this hierarchy of geographical areas varies depending whether the geographical entity being described is, for example, a state, a reservation or a territorial island.
Property: 
NameCardinalityDatatypeDescription
hasRelationSpecification
0..1
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an enumeration list. Use if all relations within this relation structure are of the same specification.
semantic
0..1
Provides semantic context for the relationship
totality
0..1
Type of relation in terms of totality with respect to an associated collection.
hasMemberRelation
0..n
Member relations that comprise the relation structure
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
realizes
0..n
1..1
Neither

Stage:

Is extendable: 
Is property: 
0
RDF Mapping: