PhysicalLayoutRelationStructure

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

A realization of RelationStructure that is used to describe the sequence of Value Mappings in a Physical Layout. This can be more complex than a simple sequence.

Example: 
The W3C Tabular Data on the Web specification allows for a list datatype. In the example below there are three top level InstanceVariables PersonID – the person identifier AgeYr – age in year BpSys_Dia – blood pressure (a list containing Systolic and Diastolic values) There are two variables at a secondary level of the hierarchy Systolic – the systolic pressure Diastolic – the diastolic pressure The delimited file below uses the comma to separate "columns" and forward slash to separate elements of a blood pressure list. PersonID, AgeYr, BpSys_Dia 1,22,119/67 2,68,122/70 The PhysicalRelationStructure in this case would describe a BpSys_Dia list variable as containing an ordered sequence of the Systolic and Diastolic InstanceVariables.
Property: 
NameCardinalityDatatypeDescription
criteria
0..1
Intensional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.)
hasRelationSpecification
0..1
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an ennumeration 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
Specifics of relations between InstanceVariables in the PhysicalLayout
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
realizes
Class of the Collection pattern realized by this class.
0..n
1..1
Neither

Stage:

Is extendable: 
Is property: 
0
RDF Mapping: