UnitType¶
Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::Conceptual::UnitType
Definition¶
Unit type is a type or class of objects of interest (units).
Examples¶
Person, Establishment, Household, State, Country, Dog, Automobile, Neutrino.
Explanatory notes¶
Unit type is the most general in the hierarchy of unit type, universe, and population. It is a description of the basic characteristics for a general set of Units. A universe is a set of entities defined by a specialization of a unit type. A Population further narrows the specification to a specific time and geography.
A unit type is used to describe a class or group of Units based on a single characteristic with no specification of time and geography. For example, the unit type of “Person” groups together a set of Units based on the characteristic that they are “Persons”.
It concerns not only unit types used in dissemination, but anywhere in the statistical process. E.g. using administrative data might involve the use of a fiscal unit. [GSIM 1.1].
Diagram
Inheritance
Attributes
Name |
Inherited from |
Description |
Data Type |
Multiplicity |
Default value |
|---|---|---|---|---|---|
descriptiveText |
- own class - |
A short natural language account of the characteristics of the object. |
0..1 |
||
catalogDetails |
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. |
0..1 |
|||
definition |
Natural language statement conveying the meaning of a concept, differentiating it from other concepts. Supports the use of multiple languages and structured text. ‘externalDefinition’ can’t be used if ‘definition’ is used. |
0..1 |
|||
displayLabel |
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. |
0..* |
|||
externalDefinition |
A reference to an external definition of a concept (that is, a concept which is described outside the content of the DDI-CDI metadata description). An example is a SKOS concept. The definition property is assumed to duplicate the external one referenced if externalDefinition is used. Other corresponding properties are assumed to be included unchanged if used. |
0..1 |
|||
identifier |
Identifier for objects requiring short- or long-lasting referencing and management. |
0..1 |
|||
name |
Human understandable name (linguistic signifier, word, phrase, or mnemonic). May follow ISO/IEC 11179-5 naming principles, and have context provided to specify usage. |
0..* |
Associations
Direction |
Association |
Description |
Multiplicity of UnitType |
Package of Other Class |
Other Class |
Multiplicity of other class |
Aggregation Kind |
Inherited from |
|---|---|---|---|---|---|---|---|---|
to |
AgentListing isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
ClassificationFamily isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
ClassificationIndex isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
ClassificationSeries isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
Concept uses Concept |
The uses association is intended to describe specific relationships between Concepts and several of its sub-classes. This is documented in section VII.D.5 of the “DDI-Cross Domain Integration: Detailed Model” document. |
0..* |
- own package - |
0..* |
none |
||
to |
ConceptMap hasSource Concept |
Concept map has one to many source concepts. |
1..* |
- own package - |
0..* |
none |
||
to |
ConceptMap hasTarget Concept |
Concept map has one to many target concepts. |
1..* |
- own package - |
0..* |
none |
||
to |
ConceptRelationship hasSource Concept |
Restricts source object to concept for the relationship. |
1..1 |
- own package - |
0..* |
none |
||
to |
ConceptRelationship hasTarget Concept |
Restricts target object to concept for the relationship. |
1..1 |
- own package - |
0..* |
none |
||
to |
ConceptSystem has Concept |
Concept system has zero to many concepts. |
0..* |
- own package - |
0..* |
none |
||
to |
ConceptSystem isDefinedBy Concept |
Concept system is defined by zero to many concepts. The conceptual basis for the collection of members. |
0..* |
- own package - |
0..* |
none |
||
to |
DataStore isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
EnumerationDomain isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
Level isDefinedBy Concept |
A concept or concept sub-type which describes the level. |
0..1 |
0..* |
none |
|||
to |
LogicalRecord isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
PhysicalDataSet isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
PhysicalRecordSegment isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
PhysicalSegmentLayout isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
0..* |
none |
|||
to |
VariableCollection isDefinedBy Concept |
The conceptual basis for the collection of members. |
0..* |
- own package - |
0..* |
none |
||
to |
ConceptualVariable measures UnitType |
The measures association is intended to describe specific relationships between the ConceptualVariable and UnitType classes, and similar relationships between their sub-classes. This is documented in section VII.D.5 of the “DDI-Cross Domain Integration: Detailed Model” document. |
0..1 |
- own package - |
0..* |
none |
- own class - |
|
to |
Unit has UnitType |
The unit type of the unit. |
0..* |
- own package - |
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 UnitType (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-UnitType"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#UnitType"
6 xmi:type="uml:Class">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#UnitType-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType"/>
11 <body>Definition
12==========
13Unit type is a type or class of objects of interest (units).
14
15Examples
16========
17Person, Establishment, Household, State, Country, Dog, Automobile, Neutrino.
18
19Explanatory notes
20=================
21Unit type is the most general in the hierarchy of unit type, universe, and population. It is a description of the basic characteristics for a general set of Units. A universe is a set of entities defined by a specialization of a unit type. A Population further narrows the specification to a specific time and geography.
22
23A unit type is used to describe a class or group of Units based on a single characteristic with no specification of time and geography. For example, the unit type of "Person" groups together a set of Units based on the characteristic that they are "Persons".
24
25It concerns not only unit types used in dissemination, but anywhere in the statistical process. E.g. using administrative data might involve the use of a fiscal unit. [GSIM 1.1].</body>
26 </ownedComment>
27 <name>UnitType</name>
28 <generalization xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType-generalization"
29 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#UnitType-generalization"
30 xmi:type="uml:Generalization">
31 <general xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Concept"/>
32 </generalization>
33 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType-descriptiveText"
34 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#UnitType-descriptiveText"
35 xmi:type="uml:Property">
36 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType-descriptiveText-ownedComment"
37 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#UnitType-descriptiveText-ownedComment"
38 xmi:type="uml:Comment">
39 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType-descriptiveText"/>
40 <body>A short natural language account of the characteristics of the object.</body>
41 </ownedComment>
42 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType-descriptiveText-lowerValue"
43 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#UnitType-descriptiveText-lowerValue"
44 xmi:type="uml:LiteralInteger"/>
45 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType-descriptiveText-upperValue"
46 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#UnitType-descriptiveText-upperValue"
47 xmi:type="uml:LiteralUnlimitedNatural">
48 <value>1</value>
49 </upperValue>
50 <name>descriptiveText</name>
51 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
52 </ownedAttribute>
53</packagedElement>
Fragment for the class UnitType (entire XML Schema)
1<xs:element name="UnitType"
2 type="UnitTypeXsdType"
3 xml:id="UnitType">
4 <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::UnitType -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ==========
8 Unit type is a type or class of objects of interest (units).
9
10 Examples
11 ========
12 Person, Establishment, Household, State, Country, Dog, Automobile, Neutrino.
13
14 Explanatory notes
15 =================
16 Unit type is the most general in the hierarchy of unit type, universe, and population. It is a description of the basic characteristics for a general set of Units. A universe is a set of entities defined by a specialization of a unit type. A Population further narrows the specification to a specific time and geography.
17
18 A unit type is used to describe a class or group of Units based on a single characteristic with no specification of time and geography. For example, the unit type of "Person" groups together a set of Units based on the characteristic that they are "Persons".
19
20 It concerns not only unit types used in dissemination, but anywhere in the statistical process. E.g. using administrative data might involve the use of a fiscal unit. [GSIM 1.1].</xs:documentation>
21 </xs:annotation>
22</xs:element>
23<xs:complexType name="UnitTypeXsdType"
24 xml:id="UnitTypeXsdType">
25 <xs:annotation>
26 <xs:documentation>Definition
27 ==========
28 Unit type is a type or class of objects of interest (units).
29
30 Examples
31 ========
32 Person, Establishment, Household, State, Country, Dog, Automobile, Neutrino.
33
34 Explanatory notes
35 =================
36 Unit type is the most general in the hierarchy of unit type, universe, and population. It is a description of the basic characteristics for a general set of Units. A universe is a set of entities defined by a specialization of a unit type. A Population further narrows the specification to a specific time and geography.
37
38 A unit type is used to describe a class or group of Units based on a single characteristic with no specification of time and geography. For example, the unit type of "Person" groups together a set of Units based on the characteristic that they are "Persons".
39
40 It concerns not only unit types used in dissemination, but anywhere in the statistical process. E.g. using administrative data might involve the use of a fiscal unit. [GSIM 1.1].</xs:documentation>
41 </xs:annotation>
42 <xs:complexContent>
43 <xs:extension base="ConceptXsdType">
44 <xs:sequence>
45 <xs:element name="descriptiveText"
46 type="InternationalStringXsdType"
47 minOccurs="0"
48 maxOccurs="1"
49 xml:id="UnitType-descriptiveText">
50 <xs:annotation>
51 <xs:documentation>A short natural language account of the characteristics of the object.</xs:documentation>
52 </xs:annotation>
53 </xs:element>
54 </xs:sequence>
55 </xs:extension>
56 </xs:complexContent>
57</xs:complexType>
Fragment for the class UnitType (main ontology)
1# class UnitType
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::UnitType
3cdi:UnitType
4 a rdfs:Class, owl:Class, ucmis:Class;
5 rdfs:label "UnitType";
6 rdfs:comment "Definition\n==========\nUnit type is a type or class of objects of interest (units).\n\nExamples\n========\nPerson, Establishment, Household, State, Country, Dog, Automobile, Neutrino.\n\nExplanatory notes\n=================\nUnit type is the most general in the hierarchy of unit type, universe, and population. It is a description of the basic characteristics for a general set of Units. A universe is a set of entities defined by a specialization of a unit type. A Population further narrows the specification to a specific time and geography.\n\nA unit type is used to describe a class or group of Units based on a single characteristic with no specification of time and geography. For example, the unit type of \"Person\" groups together a set of Units based on the characteristic that they are \"Persons\".\n\nIt concerns not only unit types used in dissemination, but anywhere in the statistical process. E.g. using administrative data might involve the use of a fiscal unit. [GSIM 1.1]."@en;
7 rdfs:subClassOf cdi:Concept;
8.
9
10cdi:UnitType-descriptiveText
11 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
12 rdfs:label "descriptiveText";
13 rdfs:comment "A short natural language account of the characteristics of the object."@en;
14 rdfs:domain cdi:UnitType;
15 rdfs:range cdi:InternationalString;
16.
Fragment for the class UnitType (main JSON-LD)
1{
2 "@context": [
3 "Concept.jsonld",
4 {
5 "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
6 "xsd": "http://www.w3.org/2001/XMLSchema#",
7 "UnitType": "cdi:UnitType",
8 "descriptiveText": {
9 "@id": "cdi:UnitType-descriptiveText",
10 "@type": "@id",
11 "@context": "InternationalString.jsonld"
12 },
13
14 "measures_OF_ConceptualVariable": {
15 "@reverse": "cdi:ConceptualVariable_measures_UnitType",
16 "@type": "@id"
17 },
18 "has_OF_Unit": {
19 "@reverse": "cdi:Unit_has_UnitType",
20 "@type": "@id"
21 },
22 " comment ": "tag:json-should-support-trailing-commas"
23 }
24 ],
25 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:06.",
26 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::Conceptual::UnitType"
27}
