LayoutComponentRelation

Is Abstract: 
no
Is Pattern: 
no
Definition: 

Relation between components in a layout as specified by RelationSpecification

Explanatory Notes: 

A layout may consist of other components in addition to instance variables. In the RDF Data Cube Vocabulary at https://dvcs.w3.org/hg/gld/raw-file/29a3dd6dc12c/data-cube/index.html#dsd in addition to instance variables functioning in various roles (dimension, measure, attribute) there are categories or more precisely sdmx-codes. In the RDF Data Cube Vocabulary sdmx-codes are associated with observations together with their associated dimensions. These observations contain measurements that in turn are rolled up into aggregates.

So at least when it comes to data cubes both instance variables AND their codes need to be represented in the layout mix. The way this works in LayoutComponentRelation with data cubes is that instance variables as dimensions have codes and codes participate in instance variables as measurements.

By way of an example see: https://ddi-alliance.atlassian.net/wiki/download/attachments/491696/Data...

Property: 
NameCardinalityDatatypeDescription
hasRelationSpecification
1..1
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an ennumeration list
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.
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
realizes
Class of the Collection pattern realized by this class.
0..n
1..1
Neither
source
Restricts source to Instance Variables in a Logical Record Layout.
0..n
1..1
Neither
target
Restricts target Instance Variables and cardinality in a Logical Record Layout.
0..n
1..1
Neither
alternateSource
Restricts source to Codes in a Logical Record Layout.
0..1
0..n
Neither
alternateTarget
Restricts target to Codes in a Logical Record Layout.
0..n
0..1
Neither

Stage:

Is extendable: 
Is property: 
1
RDF Mapping: 

Comments

If this is always a sequence it could be handled by logical record realizing a collection and using the contains with ordered memberItems.

It is old and not used