Unit

Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::Conceptual::Unit

Definition

Individual object of interest for some statistical activity, such as data collection.

Examples

Here are 3 examples:

  1. Individual US person (i.e., Arofan Gregory, Dan Gillman, Barack Obama, etc.)

  2. Individual US computer companies (i.e., Microsoft, Apple, IBM, etc.)

  3. Individual US universities (i.e., Johns Hopkins, University of Maryland, Yale, etc.) [GSIM 1.1]

Explanatory notes

In a traditional data table each column might represent some variable (measurement). Each row would represent the entity (Unit) to which those variables relate. Height measurements might be made on persons (unit type) of primary school age (Universe) at Pinckney Elementary School on September 1, 2005 (population). The height for Mary Roe (Unit) might be 139 cm.

The Unit is not invariably tied to some value. A median income might be calculated for a block in the U.S. but then used as an attribute of a person residing on that block. For the initial measurement the Unit was the block. In the reuse the unit would be that specific person to which the value was applied.

In a big data table each row represents a unit/variable double. Together a unit identifier and a variable identifier define the key. And for each key there is just one value – the measure of the unit on the variable.

A big data table is sometimes referred to as a column-oriented data store whereas a traditional database is sometimes referred to as a row-oriented data store. The unit plays an identifier role in both types of data stores.

Diagram

Attributes

Name

Inherited from

Description

Data Type

Multiplicity

Default value

catalogDetails

- own class -

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

definition

- own class -

Natural language statement conveying the meaning of a concept, differentiating it from other concepts. Supports the use of multiple languages and structured text.

InternationalString

0..1

displayLabel

- own class -

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

- own class -

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

Identifier

0..1

name

- own class -

Human understandable name (liguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage.

ObjectName

0..*
Associations

Direction

Association

Description

Multiplicity of Unit

Package of Other Class

Other Class

Multiplicity of other class

Aggregation Kind

Inherited from

to

Key correspondsTo Unit

0..1

DataDescription

Key

0..*

none

- own class -

to

KeyDefinition correspondsTo Unit

0..1

DataDescription

KeyDefinition

0..*

none

- own class -

to

Population isComposedOf Unit

A unit in the population.

0..*

- own package -

Population

0..*

none

- own class -

from

Unit has UnitType

The unit type of the unit.

0..*

- own package -

UnitType

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 Unit (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-Conceptual-Unit"
  5                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit"
  6                 xmi:type="uml:Class">
  7   <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-ownedComment"
  8                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-ownedComment"
  9                 xmi:type="uml:Comment">
 10      <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit"/>
 11      <body>Definition
 12==========
 13Individual object of interest for some statistical activity, such as data collection.
 14
 15Examples
 16========
 17Here are 3 examples:
 18
 191. Individual US person (i.e., Arofan Gregory, Dan Gillman, Barack Obama, etc.)
 202. Individual US computer companies (i.e., Microsoft, Apple, IBM, etc.)
 213. Individual US universities (i.e., Johns Hopkins, University of Maryland, Yale, etc.) [GSIM 1.1]
 22
 23Explanatory notes
 24=================
 25In a traditional data table each column might represent some variable (measurement). Each row would represent the entity (Unit)  to which those variables relate. Height measurements might be made on persons (unit type) of primary school age (Universe) at Pinckney Elementary School on September 1, 2005 (population). The height for Mary Roe (Unit)  might be 139 cm.
 26
 27The Unit is not invariably tied to some value. A median income might be calculated for a block in the U.S. but then used as an attribute of a person residing on that block. For the initial measurement the Unit was the block. In the reuse the unit would be that specific person to which the value was applied.
 28
 29In a big data table each row represents a unit/variable double. Together a unit identifier and a variable identifier define the key. And for each key there is just one value – the measure of the unit on the variable.
 30
 31A big data table is sometimes referred to as a column-oriented data store whereas a traditional database is sometimes referred to as a row-oriented data store. The unit plays an identifier role in both types of data stores.</body>
 32   </ownedComment>
 33   <name>Unit</name>
 34   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-catalogDetails"
 35                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-catalogDetails"
 36                   xmi:type="uml:Property">
 37      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-catalogDetails-ownedComment"
 38                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-catalogDetails-ownedComment"
 39                    xmi:type="uml:Comment">
 40         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-catalogDetails"/>
 41         <body>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.</body>
 42      </ownedComment>
 43      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-catalogDetails-lowerValue"
 44                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-catalogDetails-lowerValue"
 45                  xmi:type="uml:LiteralInteger"/>
 46      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-catalogDetails-upperValue"
 47                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-catalogDetails-upperValue"
 48                  xmi:type="uml:LiteralUnlimitedNatural">
 49         <value>1</value>
 50      </upperValue>
 51      <name>catalogDetails</name>
 52      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CatalogDetails"/>
 53   </ownedAttribute>
 54   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-definition"
 55                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-definition"
 56                   xmi:type="uml:Property">
 57      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-definition-ownedComment"
 58                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-definition-ownedComment"
 59                    xmi:type="uml:Comment">
 60         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-definition"/>
 61         <body>Natural language statement conveying the meaning of a concept, differentiating it from other concepts. Supports the use of multiple languages and structured text.</body>
 62      </ownedComment>
 63      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-definition-lowerValue"
 64                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-definition-lowerValue"
 65                  xmi:type="uml:LiteralInteger"/>
 66      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-definition-upperValue"
 67                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-definition-upperValue"
 68                  xmi:type="uml:LiteralUnlimitedNatural">
 69         <value>1</value>
 70      </upperValue>
 71      <name>definition</name>
 72      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
 73   </ownedAttribute>
 74   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-displayLabel"
 75                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-displayLabel"
 76                   xmi:type="uml:Property">
 77      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-displayLabel-ownedComment"
 78                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-displayLabel-ownedComment"
 79                    xmi:type="uml:Comment">
 80         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-displayLabel"/>
 81         <body>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.</body>
 82      </ownedComment>
 83      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-displayLabel-lowerValue"
 84                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-displayLabel-lowerValue"
 85                  xmi:type="uml:LiteralInteger"/>
 86      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-displayLabel-upperValue"
 87                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-displayLabel-upperValue"
 88                  xmi:type="uml:LiteralUnlimitedNatural">
 89         <value>*</value>
 90      </upperValue>
 91      <name>displayLabel</name>
 92      <isOrdered>true</isOrdered>
 93      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-LabelForDisplay"/>
 94   </ownedAttribute>
 95   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-identifier"
 96                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-identifier"
 97                   xmi:type="uml:Property">
 98      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-identifier-ownedComment"
 99                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-identifier-ownedComment"
100                    xmi:type="uml:Comment">
101         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-identifier"/>
102         <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
103      </ownedComment>
104      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-identifier-lowerValue"
105                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-identifier-lowerValue"
106                  xmi:type="uml:LiteralInteger"/>
107      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-identifier-upperValue"
108                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-identifier-upperValue"
109                  xmi:type="uml:LiteralUnlimitedNatural">
110         <value>1</value>
111      </upperValue>
112      <name>identifier</name>
113      <isID>true</isID>
114      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
115   </ownedAttribute>
116   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-name"
117                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-name"
118                   xmi:type="uml:Property">
119      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-name-ownedComment"
120                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-name-ownedComment"
121                    xmi:type="uml:Comment">
122         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-name"/>
123         <body>Human understandable name (liguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage.</body>
124      </ownedComment>
125      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-name-lowerValue"
126                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-name-lowerValue"
127                  xmi:type="uml:LiteralInteger"/>
128      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-name-upperValue"
129                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-name-upperValue"
130                  xmi:type="uml:LiteralUnlimitedNatural">
131         <value>*</value>
132      </upperValue>
133      <name>name</name>
134      <isOrdered>true</isOrdered>
135      <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ObjectName"/>
136   </ownedAttribute>
137   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-ownedAttribute"
138                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-ownedAttribute"
139                   xmi:type="uml:Property">
140      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-ownedAttribute-lowerValue"
141                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-ownedAttribute-lowerValue"
142                  xmi:type="uml:LiteralInteger"/>
143      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit-ownedAttribute-upperValue"
144                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Unit-ownedAttribute-upperValue"
145                  xmi:type="uml:LiteralUnlimitedNatural">
146         <value>*</value>
147      </upperValue>
148      <association xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Unit_has_UnitType"/>
149      <type xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType"/>
150   </ownedAttribute>
151</packagedElement>

Fragment for the class Unit (entire XML Schema)

  1<xs:element name="Unit"
  2            type="UnitXsdType"
  3            xml:id="Unit">
  4  <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::Unit -->
  5  <xs:annotation>
  6    <xs:documentation>Definition
  7          ==========
  8          Individual object of interest for some statistical activity, such as data collection.
  9          
 10          Examples
 11          ========
 12          Here are 3 examples:
 13          
 14          1. Individual US person (i.e., Arofan Gregory, Dan Gillman, Barack Obama, etc.)
 15          2. Individual US computer companies (i.e., Microsoft, Apple, IBM, etc.)
 16          3. Individual US universities (i.e., Johns Hopkins, University of Maryland, Yale, etc.) [GSIM 1.1]
 17          
 18          Explanatory notes
 19          =================
 20          In a traditional data table each column might represent some variable (measurement). Each row would represent the entity (Unit)  to which those variables relate. Height measurements might be made on persons (unit type) of primary school age (Universe) at Pinckney Elementary School on September 1, 2005 (population). The height for Mary Roe (Unit)  might be 139 cm.
 21          
 22          The Unit is not invariably tied to some value. A median income might be calculated for a block in the U.S. but then used as an attribute of a person residing on that block. For the initial measurement the Unit was the block. In the reuse the unit would be that specific person to which the value was applied.
 23          
 24          In a big data table each row represents a unit/variable double. Together a unit identifier and a variable identifier define the key. And for each key there is just one value – the measure of the unit on the variable.
 25          
 26          A big data table is sometimes referred to as a column-oriented data store whereas a traditional database is sometimes referred to as a row-oriented data store. The unit plays an identifier role in both types of data stores.</xs:documentation>
 27  </xs:annotation>
 28</xs:element>
 29<xs:complexType name="UnitXsdType"
 30                xml:id="UnitXsdType">
 31  <xs:annotation>
 32    <xs:documentation>Definition
 33          ==========
 34          Individual object of interest for some statistical activity, such as data collection.
 35          
 36          Examples
 37          ========
 38          Here are 3 examples:
 39          
 40          1. Individual US person (i.e., Arofan Gregory, Dan Gillman, Barack Obama, etc.)
 41          2. Individual US computer companies (i.e., Microsoft, Apple, IBM, etc.)
 42          3. Individual US universities (i.e., Johns Hopkins, University of Maryland, Yale, etc.) [GSIM 1.1]
 43          
 44          Explanatory notes
 45          =================
 46          In a traditional data table each column might represent some variable (measurement). Each row would represent the entity (Unit)  to which those variables relate. Height measurements might be made on persons (unit type) of primary school age (Universe) at Pinckney Elementary School on September 1, 2005 (population). The height for Mary Roe (Unit)  might be 139 cm.
 47          
 48          The Unit is not invariably tied to some value. A median income might be calculated for a block in the U.S. but then used as an attribute of a person residing on that block. For the initial measurement the Unit was the block. In the reuse the unit would be that specific person to which the value was applied.
 49          
 50          In a big data table each row represents a unit/variable double. Together a unit identifier and a variable identifier define the key. And for each key there is just one value – the measure of the unit on the variable.
 51          
 52          A big data table is sometimes referred to as a column-oriented data store whereas a traditional database is sometimes referred to as a row-oriented data store. The unit plays an identifier role in both types of data stores.</xs:documentation>
 53  </xs:annotation>
 54  <xs:sequence>
 55    <xs:element name="catalogDetails"
 56                type="CatalogDetailsXsdType"
 57                minOccurs="0"
 58                maxOccurs="1"
 59                xml:id="Unit-catalogDetails">
 60      <xs:annotation>
 61        <xs:documentation>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.</xs:documentation>
 62      </xs:annotation>
 63    </xs:element>
 64    <xs:element name="definition"
 65                type="InternationalStringXsdType"
 66                minOccurs="0"
 67                maxOccurs="1"
 68                xml:id="Unit-definition">
 69      <xs:annotation>
 70        <xs:documentation>Natural language statement conveying the meaning of a concept, differentiating it from other concepts. Supports the use of multiple languages and structured text.</xs:documentation>
 71      </xs:annotation>
 72    </xs:element>
 73    <xs:element name="displayLabel"
 74                type="LabelForDisplayXsdType"
 75                minOccurs="0"
 76                maxOccurs="unbounded"
 77                xml:id="Unit-displayLabel">
 78      <xs:annotation>
 79        <xs:documentation>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.</xs:documentation>
 80      </xs:annotation>
 81    </xs:element>
 82    <xs:element name="identifier"
 83                type="IdentifierXsdType"
 84                minOccurs="0"
 85                maxOccurs="1"
 86                xml:id="Unit-identifier">
 87      <xs:annotation>
 88        <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
 89      </xs:annotation>
 90    </xs:element>
 91    <xs:element name="name"
 92                type="ObjectNameXsdType"
 93                minOccurs="0"
 94                maxOccurs="unbounded"
 95                xml:id="Unit-name">
 96      <xs:annotation>
 97        <xs:documentation>Human understandable name (liguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage.</xs:documentation>
 98      </xs:annotation>
 99    </xs:element>
100    <xs:element name="Unit_has_UnitType"
101                minOccurs="0"
102                maxOccurs="unbounded"
103                xml:id="Unit_has_UnitType">
104      <xs:annotation>
105        <xs:documentation>The unit type of the unit.</xs:documentation>
106      </xs:annotation>
107      <xs:complexType>
108        <xs:complexContent>
109          <xs:restriction base="AssociationReferenceXsdType">
110            <xs:sequence>
111              <xs:element name="ddiReference"
112                          type="InternationalRegistrationDataIdentifierXsdType"
113                          minOccurs="0"
114                          maxOccurs="1"
115                          xml:id="Unit_has_UnitType-ddiReference"/>
116              <xs:element name="validType"
117                          minOccurs="0"
118                          maxOccurs="unbounded"
119                          xml:id="Unit_has_UnitType-validType">
120                <xs:simpleType>
121                  <xs:restriction base="xs:NMTOKEN">
122                    <xs:enumeration value="Population"/>
123                    <xs:enumeration value="UnitType"/>
124                    <xs:enumeration value="Universe"/>
125                  </xs:restriction>
126                </xs:simpleType>
127              </xs:element>
128            </xs:sequence>
129          </xs:restriction>
130        </xs:complexContent>
131      </xs:complexType>
132    </xs:element>
133  </xs:sequence>
134</xs:complexType>

Fragment for the class Unit (main ontology)

 1# class Unit
 2# based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::Unit
 3cdi:Unit
 4  a rdfs:Class, owl:Class, ucmis:Class;
 5  rdfs:label "Unit";
 6  rdfs:comment "Definition\n==========\nIndividual object of interest for some statistical activity, such as data collection.\n\nExamples\n========\nHere are 3 examples:\n\n1. Individual US person (i.e., Arofan Gregory, Dan Gillman, Barack Obama, etc.)\n2. Individual US computer companies (i.e., Microsoft, Apple, IBM, etc.)\n3. Individual US universities (i.e., Johns Hopkins, University of Maryland, Yale, etc.) [GSIM 1.1]\n\nExplanatory notes\n=================\nIn a traditional data table each column might represent some variable (measurement). Each row would represent the entity (Unit)  to which those variables relate. Height measurements might be made on persons (unit type) of primary school age (Universe) at Pinckney Elementary School on September 1, 2005 (population). The height for Mary Roe (Unit)  might be 139 cm.\n\nThe Unit is not invariably tied to some value. A median income might be calculated for a block in the U.S. but then used as an attribute of a person residing on that block. For the initial measurement the Unit was the block. In the reuse the unit would be that specific person to which the value was applied.\n\nIn a big data table each row represents a unit/variable double. Together a unit identifier and a variable identifier define the key. And for each key there is just one value – the measure of the unit on the variable.\n\nA big data table is sometimes referred to as a column-oriented data store whereas a traditional database is sometimes referred to as a row-oriented data store. The unit plays an identifier role in both types of data stores."@en;
 7  
 8.
 9
10cdi:Unit-catalogDetails
11  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
12  rdfs:label "catalogDetails";
13  rdfs:comment "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."@en;
14  rdfs:domain cdi:Unit;
15  rdfs:range cdi:CatalogDetails;
16.
17
18cdi:Unit-definition
19  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
20  rdfs:label "definition";
21  rdfs:comment "Natural language statement conveying the meaning of a concept, differentiating it from other concepts. Supports the use of multiple languages and structured text."@en;
22  rdfs:domain cdi:Unit;
23  rdfs:range cdi:InternationalString;
24.
25
26cdi:Unit-displayLabel
27  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
28  rdfs:label "displayLabel";
29  rdfs:comment "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."@en;
30  rdfs:domain cdi:Unit;
31  rdfs:range cdi:LabelForDisplay;
32.
33
34cdi:Unit-identifier
35  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
36  rdfs:label "identifier";
37  rdfs:comment "Identifier for objects requiring short- or long-lasting referencing and management."@en;
38  rdfs:domain cdi:Unit;
39  rdfs:range cdi:Identifier;
40.
41
42cdi:Unit-name
43  a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
44  rdfs:label "name";
45  rdfs:comment "Human understandable name (liguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage."@en;
46  rdfs:domain cdi:Unit;
47  rdfs:range cdi:ObjectName;
48.
49
50
51cdi:Unit_has_UnitType
52  a rdf:Property, owl:ObjectProperty, ucmis:Association;
53  # ASSOCIATION
54  rdfs:label "has";
55  skos:altLabel "Unit_has_UnitType";
56  rdfs:comment "The unit type of the unit."@en;
57  rdfs:domain cdi:Unit;
58  rdfs:range cdi:UnitType;
59.

Fragment for the class Unit (main JSON-LD)

 1{
 2  "@context": [
 3    {
 4      "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
 5      "xsd": "http://www.w3.org/2001/XMLSchema#",
 6      "Unit": "cdi:Unit",
 7      "catalogDetails": {
 8        "@id": "cdi:Unit-catalogDetails",
 9        "@type": "@id",
10        "@context": "CatalogDetails.jsonld"
11      },
12      "definition": {
13        "@id": "cdi:Unit-definition",
14        "@type": "@id",
15        "@context": "InternationalString.jsonld"
16      },
17      "displayLabel": {
18        "@id": "cdi:Unit-displayLabel",
19        "@type": "@id",
20        "@context": "LabelForDisplay.jsonld"
21      },
22      "identifier": {
23        "@id": "cdi:Unit-identifier",
24        "@type": "@id",
25        "@context": "Identifier.jsonld"
26      },
27      "name": {
28        "@id": "cdi:Unit-name",
29        "@type": "@id",
30        "@context": "ObjectName.jsonld"
31      },
32      
33      "has": {
34        "@id": "cdi:Unit_has_UnitType",
35        "@type": "@id"      },
36      "correspondsTo_OF_Key": {
37        "@reverse": "cdi:Key_correspondsTo_Unit",
38        "@type": "@id"
39      },
40      "correspondsTo_OF_KeyDefinition": {
41        "@reverse": "cdi:KeyDefinition_correspondsTo_Unit",
42        "@type": "@id"
43      },
44      "isComposedOf_OF_Population": {
45        "@reverse": "cdi:Population_isComposedOf_Unit",
46        "@type": "@id"
47      },
48      " comment ": "tag:json-should-support-trailing-commas" 
49    }
50  ],
51  "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:06.",
52  "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::Conceptual::Unit"
53}