Category¶
Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::Conceptual::Category
Definition¶
Concept whose role is to define and measure a characteristic.
Examples¶
The category “Male” is used to define or measure “Sex” or “Gender”, which are characteristics. In turn, they are also variables. “Extremely Satisfied” is a category in an agreement scale. This can be used for many kinds of variables.
Explanatory notes¶
A category is a concept, typically associated with a code in the representation of a variable value. Categories are most often used in the allowed values for qualitative, i.e., nominal and ordinal, variables. A set of categories, say “Male” and “Female” for characteristics “Sex” or “Gender,” helps define those characteristics. For describing location of measurement station, you might have categories “Urban”, “Suburban”, “Rural”, etc.
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 Category |
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 |
CategoryPosition indexes Category |
1..1 |
- own package - |
0..* |
none |
- own class - |
||
to |
CategoryRelationship hasSource Category |
0..* |
- own package - |
0..* |
none |
- own class - |
||
to |
CategoryRelationship hasTarget Category |
Second member in a relationship. Note that this can be realized as a collection to support tuples. |
0..* |
- own package - |
0..* |
none |
- own class - |
|
to |
CategorySet has Category |
0..* |
- own package - |
0..* |
none |
- own class - |
||
to |
CategoryStatistic for Category |
0..1 |
0..* |
none |
- own class - |
|||
to |
ClassificationItem denotes Category |
A definition for the code. Specialization of denotes for categories. |
1..1 |
0..* |
none |
- own class - |
||
to |
Code denotes Category |
A definition for the code. Specialization of denotes for categories. |
1..1 |
0..* |
none |
- own class - |
||
to |
Notation represents Category |
Notation represents zero to many categories. |
0..* |
1..* |
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 Category (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-Category"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Category"
6 xmi:type="uml:Class">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Category-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Category-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Category"/>
11 <body>Definition
12============
13Concept whose role is to define and measure a characteristic.
14
15Examples
16==========
17The category "Male" is used to define or measure "Sex" or "Gender", which are characteristics. In turn, they are also variables. "Extremely Satisfied" is a category in an agreement scale. This can be used for many kinds of variables.
18
19
20Explanatory notes
21===================
22A category is a concept, typically associated with a code in the representation of a variable value. Categories are most often used in the allowed values for qualitative, i.e., nominal and ordinal, variables. A set of categories, say "Male" and "Female" for characteristics "Sex" or "Gender," helps define those characteristics. For describing location of measurement station, you might have categories "Urban", "Suburban", "Rural", etc.</body>
23 </ownedComment>
24 <name>Category</name>
25 <generalization xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Category-generalization"
26 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Category-generalization"
27 xmi:type="uml:Generalization">
28 <general xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Concept"/>
29 </generalization>
30 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Category-descriptiveText"
31 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Category-descriptiveText"
32 xmi:type="uml:Property">
33 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Category-descriptiveText-ownedComment"
34 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Category-descriptiveText-ownedComment"
35 xmi:type="uml:Comment">
36 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Conceptual-Category-descriptiveText"/>
37 <body>A short natural language account of the characteristics of the object.</body>
38 </ownedComment>
39 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Category-descriptiveText-lowerValue"
40 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Category-descriptiveText-lowerValue"
41 xmi:type="uml:LiteralInteger"/>
42 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Conceptual-Category-descriptiveText-upperValue"
43 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#Category-descriptiveText-upperValue"
44 xmi:type="uml:LiteralUnlimitedNatural">
45 <value>1</value>
46 </upperValue>
47 <name>descriptiveText</name>
48 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
49 </ownedAttribute>
50</packagedElement>
Fragment for the class Category (entire XML Schema)
1<xs:element name="Category"
2 type="CategoryXsdType"
3 xml:id="Category">
4 <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::Category -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ============
8 Concept whose role is to define and measure a characteristic.
9
10 Examples
11 ==========
12 The category "Male" is used to define or measure "Sex" or "Gender", which are characteristics. In turn, they are also variables. "Extremely Satisfied" is a category in an agreement scale. This can be used for many kinds of variables.
13
14
15 Explanatory notes
16 ===================
17 A category is a concept, typically associated with a code in the representation of a variable value. Categories are most often used in the allowed values for qualitative, i.e., nominal and ordinal, variables. A set of categories, say "Male" and "Female" for characteristics "Sex" or "Gender," helps define those characteristics. For describing location of measurement station, you might have categories "Urban", "Suburban", "Rural", etc.</xs:documentation>
18 </xs:annotation>
19</xs:element>
20<xs:complexType name="CategoryXsdType"
21 xml:id="CategoryXsdType">
22 <xs:annotation>
23 <xs:documentation>Definition
24 ============
25 Concept whose role is to define and measure a characteristic.
26
27 Examples
28 ==========
29 The category "Male" is used to define or measure "Sex" or "Gender", which are characteristics. In turn, they are also variables. "Extremely Satisfied" is a category in an agreement scale. This can be used for many kinds of variables.
30
31
32 Explanatory notes
33 ===================
34 A category is a concept, typically associated with a code in the representation of a variable value. Categories are most often used in the allowed values for qualitative, i.e., nominal and ordinal, variables. A set of categories, say "Male" and "Female" for characteristics "Sex" or "Gender," helps define those characteristics. For describing location of measurement station, you might have categories "Urban", "Suburban", "Rural", etc.</xs:documentation>
35 </xs:annotation>
36 <xs:complexContent>
37 <xs:extension base="ConceptXsdType">
38 <xs:sequence>
39 <xs:element name="descriptiveText"
40 type="InternationalStringXsdType"
41 minOccurs="0"
42 maxOccurs="1"
43 xml:id="Category-descriptiveText">
44 <xs:annotation>
45 <xs:documentation>A short natural language account of the characteristics of the object.</xs:documentation>
46 </xs:annotation>
47 </xs:element>
48 </xs:sequence>
49 </xs:extension>
50 </xs:complexContent>
51</xs:complexType>
Fragment for the class Category (main ontology)
1# class Category
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::Conceptual::Category
3cdi:Category
4 a rdfs:Class, owl:Class, ucmis:Class;
5 rdfs:label "Category";
6 rdfs:comment "Definition \n============ \nConcept whose role is to define and measure a characteristic. \n\nExamples \n========== \nThe category \"Male\" is used to define or measure \"Sex\" or \"Gender\", which are characteristics. In turn, they are also variables. \"Extremely Satisfied\" is a category in an agreement scale. This can be used for many kinds of variables. \n\n\nExplanatory notes \n=================== \nA category is a concept, typically associated with a code in the representation of a variable value. Categories are most often used in the allowed values for qualitative, i.e., nominal and ordinal, variables. A set of categories, say \"Male\" and \"Female\" for characteristics \"Sex\" or \"Gender,\" helps define those characteristics. For describing location of measurement station, you might have categories \"Urban\", \"Suburban\", \"Rural\", etc."@en;
7 rdfs:subClassOf cdi:Concept;
8.
9
10cdi:Category-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:Category;
15 rdfs:range cdi:InternationalString;
16.
Fragment for the class Category (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 "Category": "cdi:Category",
8 "descriptiveText": {
9 "@id": "cdi:Category-descriptiveText",
10 "@type": "@id",
11 "@context": "InternationalString.jsonld"
12 },
13
14 "indexes_OF_CategoryPosition": {
15 "@reverse": "cdi:CategoryPosition_indexes_Category",
16 "@type": "@id"
17 },
18 "hasSource_OF_CategoryRelationship": {
19 "@reverse": "cdi:CategoryRelationship_hasSource_Category",
20 "@type": "@id"
21 },
22 "hasTarget_OF_CategoryRelationship": {
23 "@reverse": "cdi:CategoryRelationship_hasTarget_Category",
24 "@type": "@id"
25 },
26 "has_OF_CategorySet": {
27 "@reverse": "cdi:CategorySet_has_Category",
28 "@type": "@id"
29 },
30 "for_OF_CategoryStatistic": {
31 "@reverse": "cdi:CategoryStatistic_for_Category",
32 "@type": "@id"
33 },
34 "denotes_OF_ClassificationItem": {
35 "@reverse": "cdi:ClassificationItem_denotes_Category",
36 "@type": "@id"
37 },
38 "denotes_OF_Code": {
39 "@reverse": "cdi:Code_denotes_Category",
40 "@type": "@id"
41 },
42 "represents_OF_Notation": {
43 "@reverse": "cdi:Notation_represents_Category",
44 "@type": "@id"
45 },
46 " comment ": "tag:json-should-support-trailing-commas"
47 }
48 ],
49 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:04.",
50 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::Conceptual::Category"
51}