KeyDefinitionMember

Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::DataDescription::KeyDefinitionMember

Definition

Single concept that is part of the structure of a key definition.

Diagram

Inheritance
    ᐊ── DataDescription::KeyDefinitionMember
Attributes

Name

Inherited from

Description

Data Type

Multiplicity

Default value

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 KeyDefinitionMember

Package of Other Class

Other Class

Multiplicity of other class

Aggregation Kind

Inherited from

from

ConceptualValue hasConceptFrom ConceptualDomain

Conceptual value has concept from one conceptual domain.

0..*

Conceptual

ConceptualDomain

1..1

none

DataDescription::ConceptualValue

to

Datum denotes ConceptualValue

1..1

- own package -

Datum

0..*

none

DataDescription::ConceptualValue

to

InstanceValue represents ConceptualValue

0..1

- own package -

InstanceValue

1..*

none

DataDescription::ConceptualValue

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

Conceptual

Concept

0..*

none

Conceptual::Concept

to

ConceptMap hasSource Concept

Concept map has one to many source concepts.

1..*

Conceptual

ConceptMap

0..*

none

Conceptual::Concept

to

ConceptMap hasTarget Concept

Concept map has one to many target concepts.

1..*

Conceptual

ConceptMap

0..*

none

Conceptual::Concept

to

ConceptRelationship hasSource Concept

Restricts source object to concept for the relationship.

1..1

Conceptual

ConceptRelationship

0..*

none

Conceptual::Concept

to

ConceptRelationship hasTarget Concept

Restricts target object to concept for the relationship.

1..1

Conceptual

ConceptRelationship

0..*

none

Conceptual::Concept

to

ConceptSystem has Concept

Concept system has zero to many concepts.

0..*

Conceptual

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

Conceptual

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

Conceptual

VariableCollection

0..*

none

Conceptual::Concept

to

KeyDefinition has KeyDefinitionMember

0..*

- own package -

KeyDefinition

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 KeyDefinitionMember (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-KeyDefinitionMember"
 5                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#KeyDefinitionMember"
 6                 xmi:type="uml:Class">
 7   <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-KeyDefinitionMember-ownedComment"
 8                 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#KeyDefinitionMember-ownedComment"
 9                 xmi:type="uml:Comment">
10      <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-KeyDefinitionMember"/>
11      <body>Definition 
12============ 
13Single concept that is part of the structure of a key definition.</body>
14   </ownedComment>
15   <name>KeyDefinitionMember</name>
16   <generalization xmi:id="DDICDIModels-DDICDILibrary-Classes-DataDescription-KeyDefinitionMember-generalization"
17                   xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#KeyDefinitionMember-generalization"
18                   xmi:type="uml:Generalization">
19      <general xmi:idref="DDICDIModels-DDICDILibrary-Classes-DataDescription-ConceptualValue"/>
20   </generalization>
21</packagedElement>

Fragment for the class KeyDefinitionMember (entire XML Schema)

 1<xs:element name="KeyDefinitionMember"
 2            type="KeyDefinitionMemberXsdType"
 3            xml:id="KeyDefinitionMember">
 4  <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::DataDescription::KeyDefinitionMember -->
 5  <xs:annotation>
 6    <xs:documentation>Definition 
 7          ============ 
 8          Single concept that is part of the structure of a key definition.</xs:documentation>
 9  </xs:annotation>
10</xs:element>
11<xs:complexType name="KeyDefinitionMemberXsdType"
12                xml:id="KeyDefinitionMemberXsdType">
13  <xs:annotation>
14    <xs:documentation>Definition 
15          ============ 
16          Single concept that is part of the structure of a key definition.</xs:documentation>
17  </xs:annotation>
18  <xs:complexContent>
19    <xs:extension base="ConceptualValueXsdType">
20      
21    </xs:extension>
22  </xs:complexContent>
23</xs:complexType>

Fragment for the class KeyDefinitionMember (main ontology)

1# class KeyDefinitionMember
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::DataDescription::KeyDefinitionMember
3cdi:KeyDefinitionMember
4  a rdfs:Class, owl:Class, ucmis:Class;
5  rdfs:label "KeyDefinitionMember";
6  rdfs:comment "Definition \n============ \nSingle concept that is part of the structure of a key definition."@en;
7  rdfs:subClassOf cdi:ConceptualValue;
8.

Fragment for the class KeyDefinitionMember (main JSON-LD)

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