ReferenceValueDomain

Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::DataDescription::Long::ReferenceValueDomain

Definition

Set of permissible values for a variable playing the role of a variable value component.

Examples

Consider two variables, i.e. income and age, with values appearing in the same column. A reference variable in this case would be a type of represented variable that can take on values from both income and age. A long data structure might have a column that takes on values from this reference variable. A descriptor variable would then have values paired with the values from the reference variable, pointing to either the income or age variable.

Diagram

Inheritance
  ᐊ── Long::ReferenceValueDomain
Attributes

Name

Inherited from

Description

Data Type

Multiplicity

Default value

catalogDetails

Representations::ValueDomain

Bundles the information useful for a data catalog entry.

Examples would be creator, contributor, title, copyright, embargo, and license information

A set of information useful for attribution, data discovery, and access. This is information that is tied to the identity of the object. If this information changes the version of the associated object changes.

CatalogDetails

0..1

displayLabel

Representations::ValueDomain

A human-readable display label for the object. Supports the use of multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.

LabelForDisplay

0..*

identifier

Representations::ValueDomain

Identifier for objects requiring short- or long-lasting referencing and management.

Identifier

0..1

recommendedDataType

Representations::ValueDomain

The data types that are recommended for use with this domain.

ControlledVocabularyEntry

0..*

Associations

Direction

Association

Description

Multiplicity of ReferenceValueDomain

Package of Other Class

Other Class

Multiplicity of other class

Aggregation Kind

Inherited from

to

InstanceValue hasValueFrom ValueDomain

1..1

DataDescription

InstanceValue

0..*

none

Representations::ValueDomain

to

DimensionComponent isStructuredBy ValueDomain

0..1

Components

DimensionComponent

0..*

none

Representations::ValueDomain

to

ReferenceValue hasValueFrom ReferenceValueDomain

1..1

- own package -

ReferenceValue

0..*

none

- own class -

to

ReferenceVariable takesValuesFrom ReferenceValueDomain

Points to a value domain that contains values that may be drawn from the domains of multiple simple variables.

0..1

- own package -

ReferenceVariable

0..*

none

- own class -

Syntax representations / encodings

All syntax representations except the Canonical XMI are provided as reference points for specific implementations, or for use as defaults if sufficient in the form presented.

Fragment for the class ReferenceValueDomain (entire model as XMI)

 1<packagedElement xmlns:StandardProfile="http://www.eclipse.org/uml2/5.0.0/UML/Profile/Standard"
 2                 xmlns:uml="http://www.eclipse.org/uml2/5.0.0/UML"
 3                 xmlns:xmi="http://www.omg.org/spec/XMI/20131001"
 4                 xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Long-ReferenceValueDomain"
 5                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ReferenceValueDomain"
 6                 xmi:type="uml:Class">
 7   <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Long-ReferenceValueDomain-ownedComment"
 8                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ReferenceValueDomain-ownedComment"
 9                 xmi:type="uml:Comment">
10      <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-Long-ReferenceValueDomain"/>
11      <body>Definition
12============
13Set of permissible values for a variable playing the role of a variable value component.
14
15Examples
16==========
17Consider two variables, i.e. income and age, with values appearing in the same column. A reference variable in this case would be a type of represented variable that can take on values from both income and age. A long data structure might have a column that takes on values from this reference variable. A descriptor variable would then have values paired with the values from the reference variable, pointing to either the income or age variable.</body>
18   </ownedComment>
19   <name>ReferenceValueDomain</name>
20   <generalization xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-Long-ReferenceValueDomain-generalization"
21                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ReferenceValueDomain-generalization"
22                   xmi:type="uml:Generalization">
23      <general xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueDomain"/>
24   </generalization>
25</packagedElement>

Fragment for the class ReferenceValueDomain (entire XML Schema)

 1<xs:element name="ReferenceValueDomain"
 2            type="ReferenceValueDomainXsdType"
 3            xml:id="ReferenceValueDomain">
 4  <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::DataDescription::Long::ReferenceValueDomain -->
 5  <xs:annotation>
 6    <xs:documentation>Definition
 7          ============
 8          Set of permissible values for a variable playing the role of a variable value component.
 9          
10          Examples
11          ==========
12          Consider two variables, i.e. income and age, with values appearing in the same column. A reference variable in this case would be a type of represented variable that can take on values from both income and age. A long data structure might have a column that takes on values from this reference variable. A descriptor variable would then have values paired with the values from the reference variable, pointing to either the income or age variable.</xs:documentation>
13  </xs:annotation>
14</xs:element>
15<xs:complexType name="ReferenceValueDomainXsdType"
16                xml:id="ReferenceValueDomainXsdType">
17  <xs:annotation>
18    <xs:documentation>Definition
19          ============
20          Set of permissible values for a variable playing the role of a variable value component.
21          
22          Examples
23          ==========
24          Consider two variables, i.e. income and age, with values appearing in the same column. A reference variable in this case would be a type of represented variable that can take on values from both income and age. A long data structure might have a column that takes on values from this reference variable. A descriptor variable would then have values paired with the values from the reference variable, pointing to either the income or age variable.</xs:documentation>
25  </xs:annotation>
26  <xs:complexContent>
27    <xs:extension base="ValueDomainXsdType">
28      
29    </xs:extension>
30  </xs:complexContent>
31</xs:complexType>

Fragment for the class ReferenceValueDomain (main ontology)

1# class ReferenceValueDomain
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::DataDescription::Long::ReferenceValueDomain
3cdi:ReferenceValueDomain
4  a rdfs:Class, owl:Class, ucmis:Class;
5  rdfs:label "ReferenceValueDomain";
6  rdfs:comment "Definition\n============\nSet of permissible values for a variable playing the role of a variable value component.\n\nExamples\n==========\nConsider two variables, i.e. income and age, with values appearing in the same column. A reference variable in this case would be a type of represented variable that can take on values from both income and age. A long data structure might have a column that takes on values from this reference variable. A descriptor variable would then have values paired with the values from the reference variable, pointing to either the income or age variable."@en;
7  rdfs:subClassOf cdi:ValueDomain;
8.

Fragment for the class ReferenceValueDomain (main JSON-LD)

 1{
 2  "@context": [
 3    "ValueDomain.jsonld",
 4    {
 5      "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
 6      "xsd": "http://www.w3.org/2001/XMLSchema#",
 7      "ReferenceValueDomain": "cdi:ReferenceValueDomain",
 8      
 9      "hasValueFrom_OF_ReferenceValue": {
10        "@reverse": "cdi:ReferenceValue_hasValueFrom_ReferenceValueDomain",
11        "@type": "@id"
12      },
13      "takesValuesFrom_OF_ReferenceVariable": {
14        "@reverse": "cdi:ReferenceVariable_takesValuesFrom_ReferenceValueDomain",
15        "@type": "@id"
16      },
17      " comment ": "tag:json-should-support-trailing-commas" 
18    }
19  ],
20  "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:08.",
21  "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::DataDescription::Long::ReferenceValueDomain"
22}