PhysicalLayoutRelationStructure

Generalization is Identifiable.

Superclass hierarchy

Definition

Realization of relation structure that is used to describe the sequence of value mappings in a physical layout.

Examples

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.

Explanatory notes

This can be more complex than a simple sequence.


Subclasses


Properties

Name

Description

Data Type

Multi- plicity

Intensional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.).

InternationalStructuredString

0..1

A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided then a context to differentiate usage must be provided as well.

ObjectName

0..*

An explanation of the purpose of the layout relation structure.

InternationalStructuredString

0..1

Provides semantic context for the relationship.

ExternalControlledVocabularyEntry

0..1

specification

SpecificationType

0..1

Type of relation in terms of totality with respect to an associated collection.

TotalityType

0..1

Inherited Properties

Name

Description

Data Type

Multi- plicity

agency

Agency expressed as filed with the DDI Agency ID registry [registry.ddialliance.org] with optional additional sub-agency extensions.

:ref:``

1..1

id

ID conforming to the allowed structure of the DDI Identifier and must be unique within the Agency.

:ref:``

1..1

isPersistent

Default value is false indicating that the content of the current version may change (may be in development mode). Set to true when the content of this version will no longer change.

:ref:``

1..1

isUniversallyUnique

Default value is false. If the id of the object was created as a Universally Unique ID (UUID) set to true.

:ref:``

1..1

localId

Locally used identifier unique with a specified context, such as a variable name within a dataset.

LocalIdFormat

0..*

version

Version number of the object.

:ref:``

1..1

versionDate

Date and time the object was changed expressed in standard ISO formats.

XSDdate

0..1

versionRationale

Reason for making a new version of the object.

RationaleDefinition

0..1

versionResponsibility

Contributor who has the ownership and responsibility for the current version.

:ref:``

0..1

Associations

Multiplicity

Association

Navigable Class

Multiplicity

0..*

PhysicalLayoutRelationStructure_structures_PhysicalSegmentLayout

PhysicalSegmentLayout

0..1

0..*

PhysicalLayoutRelationStructure_has_ValueMappingRelationship

PhysicalLayoutRelationStructure

1..1

TBD

Diagram

TBD