Universe

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

Definition

Specialized unit type, with the specialization based upon characteristics other than time and geography.

Examples

  1. Canadian adults (not limited to those residing in Canada)

  2. Computer companies

  3. Universities

Explanatory notes

Universe sits in a hierarchy between unit type and population, with unit type being most general and Population most specific. A universe is a set of entities defined by a more narrow specification than that of an underlying unit type. A population further narrows the specification to a specific time and geography.

If the Universe consists of people, a number of factors may be used in defining membership in the Universe, such as age, sex, residence, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. A universe may be described as “inclusive” or “exclusive”.

Not to be confused with Population, which includes the specification of time and geography.

Diagram

Inheritance
  ᐊ── Conceptual::UnitType
    ᐊ── Conceptual::Universe
      ᐊ── Conceptual::Population
Attributes

Name

Inherited from

Description

Data Type

Multiplicity

Default value

isInclusive

- own class -

Default value is True. The description statement of a universe is generally stated in inclusive terms such as “All persons with university degree”. Occasionally a universe is defined by what it excludes, i.e., “All persons except those with university degree”. In this case the value would be changed to False.

Boolean

0..1

true

descriptiveText

Conceptual::UnitType

A short natural language account of the characteristics of the object.

InternationalString

0..1

catalogDetails

Conceptual::Concept

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

Conceptual::Concept

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.

InternationalString

0..1

displayLabel

Conceptual::Concept

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..*

externalDefinition

Conceptual::Concept

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.

Reference

0..1

identifier

Conceptual::Concept

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

Identifier

0..1

name

Conceptual::Concept

Human understandable name (linguistic 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 Universe

Package of Other Class

Other Class

Multiplicity of other class

Aggregation Kind

Inherited from

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 -

ConceptualVariable

0..*

none

Conceptual::UnitType

to

Unit has UnitType

The unit type of the unit.

0..*

- own package -

Unit

0..*

none

Conceptual::UnitType

to

AgentListing isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

Agents

AgentListing

0..*

none

Conceptual::Concept

to

ClassificationFamily isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

Representations

ClassificationFamily

0..*

none

Conceptual::Concept

to

ClassificationIndex isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

Representations

ClassificationIndex

0..*

none

Conceptual::Concept

to

ClassificationSeries isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

Representations

ClassificationSeries

0..*

none

Conceptual::Concept

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 -

Concept

0..*

none

Conceptual::Concept

to

ConceptMap hasSource Concept

Concept map has one to many source concepts.

1..*

- own package -

ConceptMap

0..*

none

Conceptual::Concept

to

ConceptMap hasTarget Concept

Concept map has one to many target concepts.

1..*

- own package -

ConceptMap

0..*

none

Conceptual::Concept

to

ConceptRelationship hasSource Concept

Restricts source object to concept for the relationship.

1..1

- own package -

ConceptRelationship

0..*

none

Conceptual::Concept

to

ConceptRelationship hasTarget Concept

Restricts target object to concept for the relationship.

1..1

- own package -

ConceptRelationship

0..*

none

Conceptual::Concept

to

ConceptSystem has Concept

Concept system has zero to many concepts.

0..*

- own package -

ConceptSystem

0..*

none

Conceptual::Concept

to

ConceptSystem isDefinedBy Concept

Concept system is defined by zero to many concepts. The conceptual basis for the collection of members.

0..*

- own package -

ConceptSystem

0..*

none

Conceptual::Concept

to

DataStore isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

FormatDescription

DataStore

0..*

none

Conceptual::Concept

to

EnumerationDomain isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

Representations

EnumerationDomain

0..*

none

Conceptual::Concept

to

Level isDefinedBy Concept

A concept or concept sub-type which describes the level.

0..1

Representations

Level

0..*

none

Conceptual::Concept

to

LogicalRecord isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

FormatDescription

LogicalRecord

0..*

none

Conceptual::Concept

to

PhysicalDataSet isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

FormatDescription

PhysicalDataSet

0..*

none

Conceptual::Concept

to

PhysicalRecordSegment isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

FormatDescription

PhysicalRecordSegment

0..*

none

Conceptual::Concept

to

PhysicalSegmentLayout isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

FormatDescription

PhysicalSegmentLayout

0..*

none

Conceptual::Concept

to

VariableCollection isDefinedBy Concept

The conceptual basis for the collection of members.

0..*

- own package -

VariableCollection

0..*

none

Conceptual::Concept

to

Key correspondsTo Universe

0..1

DataDescription

Key

0..*

none

- own class -

to

KeyDefinition correspondsTo Universe

0..1

DataDescription

KeyDefinition

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 Universe (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-Universe"
 5                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Universe"
 6                 xmi:type="uml:Class">
 7   <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe-ownedComment"
 8                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Universe-ownedComment"
 9                 xmi:type="uml:Comment">
10      <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe"/>
11      <body>Definition
12============
13Specialized unit type, with the specialization based upon characteristics other than time and geography.
14
15Examples
16==========
171. Canadian adults (not limited to those residing in Canada)
182. Computer companies 
193. Universities
20
21Explanatory notes
22===================
23Universe sits in a hierarchy between unit type and population, with unit type being most general and Population most specific. A universe is a set of entities defined by a more narrow specification than that of an underlying unit type. A population further narrows the specification to a specific time and geography.
24
25If the Universe consists of people, a number of factors may be used in defining membership in the Universe, such as age, sex, residence, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. A universe may be described as "inclusive" or "exclusive". 
26
27Not to be confused with Population, which includes the specification of time and geography.</body>
28   </ownedComment>
29   <name>Universe</name>
30   <generalization xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe-generalization"
31                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Universe-generalization"
32                   xmi:type="uml:Generalization">
33      <general xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-UnitType"/>
34   </generalization>
35   <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe-isInclusive"
36                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Universe-isInclusive"
37                   xmi:type="uml:Property">
38      <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe-isInclusive-ownedComment"
39                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Universe-isInclusive-ownedComment"
40                    xmi:type="uml:Comment">
41         <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe-isInclusive"/>
42         <body>Default value is True. The description statement of a universe is generally stated in inclusive terms such as "All persons with university degree". Occasionally a universe is defined by what it excludes, i.e., "All persons except those with university degree". In this case the value would be changed to False.</body>
43      </ownedComment>
44      <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe-isInclusive-lowerValue"
45                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Universe-isInclusive-lowerValue"
46                  xmi:type="uml:LiteralInteger"/>
47      <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe-isInclusive-upperValue"
48                  xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Universe-isInclusive-upperValue"
49                  xmi:type="uml:LiteralUnlimitedNatural">
50         <value>1</value>
51      </upperValue>
52      <name>isInclusive</name>
53      <defaultValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Universe-isInclusive-defaultValue"
54                    xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Universe-isInclusive-defaultValue"
55                    xmi:type="uml:LiteralBoolean">
56         <value>True</value>
57      </defaultValue>
58      <type href="http://www.eclipse.org/uml2/5.0.0/UML/PrimitiveTypes.xmi#Boolean"
59            xmi:type="uml:PrimitiveType"/>
60   </ownedAttribute>
61</packagedElement>

Fragment for the class Universe (entire XML Schema)

 1<xs:element name="Universe"
 2            type="UniverseXsdType"
 3            xml:id="Universe">
 4  <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::Universe -->
 5  <xs:annotation>
 6    <xs:documentation>Definition
 7          ============
 8          Specialized unit type, with the specialization based upon characteristics other than time and geography.
 9          
10          Examples
11          ==========
12          1. Canadian adults (not limited to those residing in Canada)
13          2. Computer companies 
14          3. Universities
15          
16          Explanatory notes
17          ===================
18          Universe sits in a hierarchy between unit type and population, with unit type being most general and Population most specific. A universe is a set of entities defined by a more narrow specification than that of an underlying unit type. A population further narrows the specification to a specific time and geography.
19          
20          If the Universe consists of people, a number of factors may be used in defining membership in the Universe, such as age, sex, residence, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. A universe may be described as "inclusive" or "exclusive". 
21          
22          Not to be confused with Population, which includes the specification of time and geography.</xs:documentation>
23  </xs:annotation>
24</xs:element>
25<xs:complexType name="UniverseXsdType"
26                xml:id="UniverseXsdType">
27  <xs:annotation>
28    <xs:documentation>Definition
29          ============
30          Specialized unit type, with the specialization based upon characteristics other than time and geography.
31          
32          Examples
33          ==========
34          1. Canadian adults (not limited to those residing in Canada)
35          2. Computer companies 
36          3. Universities
37          
38          Explanatory notes
39          ===================
40          Universe sits in a hierarchy between unit type and population, with unit type being most general and Population most specific. A universe is a set of entities defined by a more narrow specification than that of an underlying unit type. A population further narrows the specification to a specific time and geography.
41          
42          If the Universe consists of people, a number of factors may be used in defining membership in the Universe, such as age, sex, residence, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. A universe may be described as "inclusive" or "exclusive". 
43          
44          Not to be confused with Population, which includes the specification of time and geography.</xs:documentation>
45  </xs:annotation>
46  <xs:complexContent>
47    <xs:extension base="UnitTypeXsdType">
48      <xs:sequence>
49        <xs:element name="isInclusive"
50                    type="xs:boolean"
51                    minOccurs="0"
52                    maxOccurs="1"
53                    xml:id="Universe-isInclusive">
54          <xs:annotation>
55            <xs:documentation>Default value is True. The description statement of a universe is generally stated in inclusive terms such as "All persons with university degree". Occasionally a universe is defined by what it excludes, i.e., "All persons except those with university degree". In this case the value would be changed to False.</xs:documentation>
56          </xs:annotation>
57        </xs:element>
58      </xs:sequence>
59    </xs:extension>
60  </xs:complexContent>
61</xs:complexType>

Fragment for the class Universe (main ontology)

 1# class Universe
 2# based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::Universe
 3cdi:Universe
 4  a rdfs:Class, owl:Class, ucmis:Class;
 5  rdfs:label "Universe";
 6  rdfs:comment "Definition\n============\nSpecialized unit type, with the specialization based upon characteristics other than time and geography.\n\nExamples\n==========\n1. Canadian adults (not limited to those residing in Canada)\n2. Computer companies \n3. Universities\n\nExplanatory notes\n===================\nUniverse sits in a hierarchy between unit type and population, with unit type being most general and Population most specific. A universe is a set of entities defined by a more narrow specification than that of an underlying unit type. A population further narrows the specification to a specific time and geography.\n\nIf the Universe consists of people, a number of factors may be used in defining membership in the Universe, such as age, sex, residence, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. A universe may be described as \"inclusive\" or \"exclusive\". \n\nNot to be confused with Population, which includes the specification of time and geography."@en;
 7  rdfs:subClassOf cdi:UnitType;
 8.
 9
10cdi:Universe-isInclusive
11  a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
12  rdfs:label "isInclusive";
13  rdfs:comment "Default value is True. The description statement of a universe is generally stated in inclusive terms such as \"All persons with university degree\". Occasionally a universe is defined by what it excludes, i.e., \"All persons except those with university degree\". In this case the value would be changed to False."@en;
14  rdfs:domain cdi:Universe;
15  rdfs:range xsd:boolean;
16.

Fragment for the class Universe (main JSON-LD)

 1{
 2  "@context": [
 3    "UnitType.jsonld",
 4    {
 5      "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
 6      "xsd": "http://www.w3.org/2001/XMLSchema#",
 7      "Universe": "cdi:Universe",
 8      "isInclusive": {
 9        "@id": "cdi:Universe-isInclusive",
10        "@type": "xsd:boolean"
11      },
12      
13      "correspondsTo_OF_Key": {
14        "@reverse": "cdi:Key_correspondsTo_Universe",
15        "@type": "@id"
16      },
17      "correspondsTo_OF_KeyDefinition": {
18        "@reverse": "cdi:KeyDefinition_correspondsTo_Universe",
19        "@type": "@id"
20      },
21      " comment ": "tag:json-should-support-trailing-commas" 
22    }
23  ],
24  "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:06.",
25  "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::Conceptual::Universe"
26}