ValueAndConceptDescription¶
Fully qualified class name: DDICDIModels::DDICDILibrary::Classes::Representations::ValueAndConceptDescription
Definition¶
Formal description of a set of values.
Examples¶
1. The integers between 1 and 10, inclusive. The values of x satisfying the logicalExpression property: “ (1 less than or equal to X less than or equalto 10) AND mod(x,10)=0” Also described with minimumValueInclusive = 1 and maximumValueInclusive = 10 (and datatype of integer). 2. The upper case letters A through C and X described with the regularExpression “/[A-CX]/”. 3. A date-time described with the Unicode Locale Data Markup Language pattern yyyy.MM.dd G ‘at’ HH:mm:ss zzz.
Explanatory notes¶
The value and concept description may be used to describe either a value domain or a conceptual domain. For a value domain, the value and concept description contains the details for a described” domain (as opposed to an enumerated domain). There are a number of properties which can be used for the description. The description could be just text such as: “an even number greater than zero”, or a more formal logical expression like “x>0 and mod(x,2)=0”. A regular expression might be useful for describing a textual domain. It could also employ a format pattern from the Unicode Locale Data Markup Language (LDML: http://www.unicode.org/reports/tr35/tr35.html). Some conceptual domains might be described with just a narrative. Others, though, might be described in much the same way as a value domain depending on the specificity of the concept. In ISO 11404 a value domain may be described either through enumeration or description, or both. This class provides the facility for that description. It may be just a text description, but a description through a logical expression is machine actionable and might, for example, be rendered as an integrity constraint. If both text and a logical expression are provided the logical expression is to be taken as the canonical description. The logical expression could conform to an expression syntax like that of the Validation and Transformation Language (VTL: https://sdmx.org/?page_id=5096) or the Structured Data Transformation Language (SDTL: https://ddialliance.org/products/sdtl/1.0).
Diagram
Attributes
Name |
Inherited from |
Description |
Data Type |
Multiplicity |
Default value |
---|---|---|---|---|---|
classificationLevel |
- own class - |
Indicates the type of relationship, nominal, ordinal, interval, ratio, or continuous. Use where appropriate for the representation type. |
0..1 |
||
description |
- own class - |
A formal description of the set of values in human-readable language. |
0..1 |
||
formatPattern |
- own class - |
A pattern for a number as described in Unicode Locale Data Markup Language (LDML) (http://www.unicode.org/reports/tr35/tr35.html) Part 3: Numbers (http://www.unicode.org/reports/tr35/tr35-numbers.html#Number_Format_Patterns) and Part 4. Dates (http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Format_Patterns) . Examples would be #,##0.### to describe the pattern for a decimal number, or yyyy.MM.dd G ‘at’ HH:mm:ss zzz for a datetime pattern. |
0..1 |
||
identifier |
- own class - |
Identifier for objects requiring short- or long-lasting referencing and management. |
0..1 |
||
logicalExpression |
- own class - |
A logical expression where the values of “x” making the expression true are the members of the set of valid values. For example, “(all reals x such that x > 0)” describes the real numbers greater than 0. |
0..1 |
||
maximumValueExclusive |
- own class - |
A string denoting the maximum possible value (excluding this value). From the W3C Recommendation “Metadata Vocabulary for Tabular Data” (https://www.w3.org/TR/tabular-metadata/) 5.11.2: “maxExclusive: An atomic property that contains a single number or string that is the maximum valid value (exclusive). The value of this property becomes the maximum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.” |
String |
0..1 |
|
maximumValueInclusive |
- own class - |
A string denoting the maximum possible value. From the W3C Recommendation “Metadata Vocabulary for Tabular Data” (https://www.w3.org/TR/tabular-metadata/) 5.11.2: “maximum: An atomic property that contains a single number or string that is the maximum valid value (inclusive); equivalent to maxInclusive. The value of this property becomes the maximum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.” |
String |
0..1 |
|
minimumValueExclusive |
- own class - |
A string denoting the minimum possible value (excluding this value). From the W3C Recommendation “Metadata Vocabulary for Tabular Data” (https://www.w3.org/TR/tabular-metadata/) 5.11.2: “minExclusive: An atomic property that contains a single number or string that is the minimum valid value (exclusive). The value of this property becomes the minimum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.” |
String |
0..1 |
|
minimumValueInclusive |
- own class - |
A string denoting the minimum possible value. From the W3C Recommendation “Metadata Vocabulary for Tabular Data” (https://www.w3.org/TR/tabular-metadata/) 5.11.2: “minimum: An atomic property that contains a single number or string that is the minimum valid value (inclusive); equivalent to minInclusive. The value of this property becomes the minimum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.” |
String |
0..1 |
|
regularExpression |
- own class - |
A regular expression where strings matching the expression belong to the set of valid values. Use typeOfContent to specify the syntax of the regularExpression found in content. |
0..1 |
Associations
Direction |
Association |
Description |
Multiplicity of ValueAndConceptDescription |
Package of Other Class |
Other Class |
Multiplicity of other class |
Aggregation Kind |
Inherited from |
---|---|---|---|---|---|---|---|---|
to |
ConceptualDomain isDescribedBy ValueAndConceptDescription |
A description of the concepts in the domain. A numeric domain might use a logical expression to be machine actionable; a text domain might use a regular expression to describe strings that describe the concepts. |
0..1 |
0..* |
none |
- own class - |
||
to |
SentinelValueDomain isDescribedBy ValueAndConceptDescription |
A formal description of the set of valid values - for described value domains. |
0..1 |
- own package - |
0..* |
none |
- own class - |
|
to |
SubstantiveValueDomain isDescribedBy ValueAndConceptDescription |
A formal description of the set of valid values - for described value domains. |
0..1 |
- 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 ValueAndConceptDescription (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-Representations-ValueAndConceptDescription"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription"
6 xmi:type="uml:Class">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription"/>
11 <body>Definition
12==========
13Formal description of a set of values.
14
15Examples
16========
17
181. The integers between 1 and 10, inclusive. The values of x satisfying the logicalExpression property: " (1 less than or equal to X less than or equalto 10) AND mod(x,10)=0" Also described with minimumValueInclusive = 1 and maximumValueInclusive = 10 (and datatype of integer).
192. The upper case letters A through C and X described with the regularExpression "/[A-CX]/".
203. A date-time described with the Unicode Locale Data Markup Language pattern yyyy.MM.dd G 'at' HH:mm:ss zzz.
21
22Explanatory notes
23=================
24The value and concept description may be used to describe either a value domain or a conceptual domain. For a value domain, the value and concept description contains the details for a described" domain (as opposed to an enumerated domain). There are a number of properties which can be used for the description. The description could be just text such as: "an even number greater than zero", or a more formal logical expression like "x>0 and mod(x,2)=0". A regular expression might be useful for describing a textual domain. It could also employ a format pattern from the Unicode Locale Data Markup Language (LDML: http://www.unicode.org/reports/tr35/tr35.html). Some conceptual domains might be described with just a narrative. Others, though, might be described in much the same way as a value domain depending on the specificity of the concept. In ISO 11404 a value domain may be described either through enumeration or description, or both. This class provides the facility for that description. It may be just a text description, but a description through a logical expression is machine actionable and might, for example, be rendered as an integrity constraint. If both text and a logical expression are provided the logical expression is to be taken as the canonical description. The logical expression could conform to an expression syntax like that of the Validation and Transformation Language (VTL: https://sdmx.org/?page_id=5096) or the Structured Data Transformation Language (SDTL: https://ddialliance.org/products/sdtl/1.0).</body>
25 </ownedComment>
26 <name>ValueAndConceptDescription</name>
27 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-classificationLevel"
28 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-classificationLevel"
29 xmi:type="uml:Property">
30 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-classificationLevel-ownedComment"
31 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-classificationLevel-ownedComment"
32 xmi:type="uml:Comment">
33 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-classificationLevel"/>
34 <body>Indicates the type of relationship, nominal, ordinal, interval, ratio, or continuous. Use where appropriate for the representation type.</body>
35 </ownedComment>
36 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-classificationLevel-lowerValue"
37 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-classificationLevel-lowerValue"
38 xmi:type="uml:LiteralInteger"/>
39 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-classificationLevel-upperValue"
40 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-classificationLevel-upperValue"
41 xmi:type="uml:LiteralUnlimitedNatural">
42 <value>1</value>
43 </upperValue>
44 <name>classificationLevel</name>
45 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-Enumerations-CategoryRelationCode"/>
46 </ownedAttribute>
47 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-description"
48 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-description"
49 xmi:type="uml:Property">
50 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-description-ownedComment"
51 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-description-ownedComment"
52 xmi:type="uml:Comment">
53 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-description"/>
54 <body>A formal description of the set of values in human-readable language.</body>
55 </ownedComment>
56 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-description-lowerValue"
57 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-description-lowerValue"
58 xmi:type="uml:LiteralInteger"/>
59 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-description-upperValue"
60 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-description-upperValue"
61 xmi:type="uml:LiteralUnlimitedNatural">
62 <value>1</value>
63 </upperValue>
64 <name>description</name>
65 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-InternationalString"/>
66 </ownedAttribute>
67 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-formatPattern"
68 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-formatPattern"
69 xmi:type="uml:Property">
70 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-formatPattern-ownedComment"
71 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-formatPattern-ownedComment"
72 xmi:type="uml:Comment">
73 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-formatPattern"/>
74 <body>A pattern for a number as described in Unicode Locale Data Markup Language (LDML) (http://www.unicode.org/reports/tr35/tr35.html) Part 3: Numbers (http://www.unicode.org/reports/tr35/tr35-numbers.html#Number_Format_Patterns) and Part 4. Dates (http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Format_Patterns) . Examples would be #,##0.### to describe the pattern for a decimal number, or yyyy.MM.dd G 'at' HH:mm:ss zzz for a datetime pattern.</body>
75 </ownedComment>
76 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-formatPattern-lowerValue"
77 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-formatPattern-lowerValue"
78 xmi:type="uml:LiteralInteger"/>
79 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-formatPattern-upperValue"
80 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-formatPattern-upperValue"
81 xmi:type="uml:LiteralUnlimitedNatural">
82 <value>1</value>
83 </upperValue>
84 <name>formatPattern</name>
85 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ControlledVocabularyEntry"/>
86 </ownedAttribute>
87 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-identifier"
88 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-identifier"
89 xmi:type="uml:Property">
90 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-identifier-ownedComment"
91 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-identifier-ownedComment"
92 xmi:type="uml:Comment">
93 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-identifier"/>
94 <body>Identifier for objects requiring short- or long-lasting referencing and management.</body>
95 </ownedComment>
96 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-identifier-lowerValue"
97 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-identifier-lowerValue"
98 xmi:type="uml:LiteralInteger"/>
99 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-identifier-upperValue"
100 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-identifier-upperValue"
101 xmi:type="uml:LiteralUnlimitedNatural">
102 <value>1</value>
103 </upperValue>
104 <name>identifier</name>
105 <isID>true</isID>
106 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-Identifier"/>
107 </ownedAttribute>
108 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-logicalExpression"
109 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-logicalExpression"
110 xmi:type="uml:Property">
111 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-logicalExpression-ownedComment"
112 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-logicalExpression-ownedComment"
113 xmi:type="uml:Comment">
114 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-logicalExpression"/>
115 <body>A logical expression where the values of "x" making the expression true are the members of the set of valid values. For example, "(all reals x such that x > 0)" describes the real numbers greater than 0.</body>
116 </ownedComment>
117 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-logicalExpression-lowerValue"
118 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-logicalExpression-lowerValue"
119 xmi:type="uml:LiteralInteger"/>
120 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-logicalExpression-upperValue"
121 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-logicalExpression-upperValue"
122 xmi:type="uml:LiteralUnlimitedNatural">
123 <value>1</value>
124 </upperValue>
125 <name>logicalExpression</name>
126 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ControlledVocabularyEntry"/>
127 </ownedAttribute>
128 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueExclusive"
129 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-maximumValueExclusive"
130 xmi:type="uml:Property">
131 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueExclusive-ownedComment"
132 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-maximumValueExclusive-ownedComment"
133 xmi:type="uml:Comment">
134 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueExclusive"/>
135 <body>A string denoting the maximum possible value (excluding this value). From the W3C Recommendation "Metadata Vocabulary for Tabular Data" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: "maxExclusive: An atomic property that contains a single number or string that is the maximum valid value (exclusive). The value of this property becomes the maximum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details."</body>
136 </ownedComment>
137 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueExclusive-lowerValue"
138 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-maximumValueExclusive-lowerValue"
139 xmi:type="uml:LiteralInteger"/>
140 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueExclusive-upperValue"
141 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-maximumValueExclusive-upperValue"
142 xmi:type="uml:LiteralUnlimitedNatural">
143 <value>1</value>
144 </upperValue>
145 <name>maximumValueExclusive</name>
146 <type href="http://www.eclipse.org/uml2/5.0.0/UML/PrimitiveTypes.xmi#String"
147 xmi:type="uml:PrimitiveType"/>
148 </ownedAttribute>
149 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueInclusive"
150 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-maximumValueInclusive"
151 xmi:type="uml:Property">
152 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueInclusive-ownedComment"
153 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-maximumValueInclusive-ownedComment"
154 xmi:type="uml:Comment">
155 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueInclusive"/>
156 <body>A string denoting the maximum possible value. From the W3C Recommendation "Metadata Vocabulary for Tabular Data" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: "maximum: An atomic property that contains a single number or string that is the maximum valid value (inclusive); equivalent to maxInclusive. The value of this property becomes the maximum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details."</body>
157 </ownedComment>
158 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueInclusive-lowerValue"
159 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-maximumValueInclusive-lowerValue"
160 xmi:type="uml:LiteralInteger"/>
161 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-maximumValueInclusive-upperValue"
162 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-maximumValueInclusive-upperValue"
163 xmi:type="uml:LiteralUnlimitedNatural">
164 <value>1</value>
165 </upperValue>
166 <name>maximumValueInclusive</name>
167 <type href="http://www.eclipse.org/uml2/5.0.0/UML/PrimitiveTypes.xmi#String"
168 xmi:type="uml:PrimitiveType"/>
169 </ownedAttribute>
170 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueExclusive"
171 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-minimumValueExclusive"
172 xmi:type="uml:Property">
173 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueExclusive-ownedComment"
174 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-minimumValueExclusive-ownedComment"
175 xmi:type="uml:Comment">
176 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueExclusive"/>
177 <body>A string denoting the minimum possible value (excluding this value). From the W3C Recommendation "Metadata Vocabulary for Tabular Data" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: "minExclusive: An atomic property that contains a single number or string that is the minimum valid value (exclusive). The value of this property becomes the minimum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details."</body>
178 </ownedComment>
179 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueExclusive-lowerValue"
180 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-minimumValueExclusive-lowerValue"
181 xmi:type="uml:LiteralInteger"/>
182 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueExclusive-upperValue"
183 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-minimumValueExclusive-upperValue"
184 xmi:type="uml:LiteralUnlimitedNatural">
185 <value>1</value>
186 </upperValue>
187 <name>minimumValueExclusive</name>
188 <type href="http://www.eclipse.org/uml2/5.0.0/UML/PrimitiveTypes.xmi#String"
189 xmi:type="uml:PrimitiveType"/>
190 </ownedAttribute>
191 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueInclusive"
192 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-minimumValueInclusive"
193 xmi:type="uml:Property">
194 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueInclusive-ownedComment"
195 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-minimumValueInclusive-ownedComment"
196 xmi:type="uml:Comment">
197 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueInclusive"/>
198 <body>A string denoting the minimum possible value. From the W3C Recommendation "Metadata Vocabulary for Tabular Data" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: "minimum: An atomic property that contains a single number or string that is the minimum valid value (inclusive); equivalent to minInclusive. The value of this property becomes the minimum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details."</body>
199 </ownedComment>
200 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueInclusive-lowerValue"
201 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-minimumValueInclusive-lowerValue"
202 xmi:type="uml:LiteralInteger"/>
203 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-minimumValueInclusive-upperValue"
204 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-minimumValueInclusive-upperValue"
205 xmi:type="uml:LiteralUnlimitedNatural">
206 <value>1</value>
207 </upperValue>
208 <name>minimumValueInclusive</name>
209 <type href="http://www.eclipse.org/uml2/5.0.0/UML/PrimitiveTypes.xmi#String"
210 xmi:type="uml:PrimitiveType"/>
211 </ownedAttribute>
212 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-regularExpression"
213 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-regularExpression"
214 xmi:type="uml:Property">
215 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-regularExpression-ownedComment"
216 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-regularExpression-ownedComment"
217 xmi:type="uml:Comment">
218 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-regularExpression"/>
219 <body>A regular expression where strings matching the expression belong to the set of valid values. Use typeOfContent to specify the syntax of the regularExpression found in content.</body>
220 </ownedComment>
221 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-regularExpression-lowerValue"
222 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-regularExpression-lowerValue"
223 xmi:type="uml:LiteralInteger"/>
224 <upperValue xmi:id="DDICDIModels-DDICDILibrary-Classes-Representations-ValueAndConceptDescription-regularExpression-upperValue"
225 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#ValueAndConceptDescription-regularExpression-upperValue"
226 xmi:type="uml:LiteralUnlimitedNatural">
227 <value>1</value>
228 </upperValue>
229 <name>regularExpression</name>
230 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-TypedString"/>
231 </ownedAttribute>
232</packagedElement>
Fragment for the class ValueAndConceptDescription (entire XML Schema)
1<xs:element name="ValueAndConceptDescription"
2 type="ValueAndConceptDescriptionXsdType"
3 xml:id="ValueAndConceptDescription">
4 <!-- based on the UML class DDICDIModels::DDICDILibrary::Classes::Representations::ValueAndConceptDescription -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ==========
8 Formal description of a set of values.
9
10 Examples
11 ========
12
13 1. The integers between 1 and 10, inclusive. The values of x satisfying the logicalExpression property: " (1 less than or equal to X less than or equalto 10) AND mod(x,10)=0" Also described with minimumValueInclusive = 1 and maximumValueInclusive = 10 (and datatype of integer).
14 2. The upper case letters A through C and X described with the regularExpression "/[A-CX]/".
15 3. A date-time described with the Unicode Locale Data Markup Language pattern yyyy.MM.dd G 'at' HH:mm:ss zzz.
16
17 Explanatory notes
18 =================
19 The value and concept description may be used to describe either a value domain or a conceptual domain. For a value domain, the value and concept description contains the details for a described" domain (as opposed to an enumerated domain). There are a number of properties which can be used for the description. The description could be just text such as: "an even number greater than zero", or a more formal logical expression like "x>0 and mod(x,2)=0". A regular expression might be useful for describing a textual domain. It could also employ a format pattern from the Unicode Locale Data Markup Language (LDML: http://www.unicode.org/reports/tr35/tr35.html). Some conceptual domains might be described with just a narrative. Others, though, might be described in much the same way as a value domain depending on the specificity of the concept. In ISO 11404 a value domain may be described either through enumeration or description, or both. This class provides the facility for that description. It may be just a text description, but a description through a logical expression is machine actionable and might, for example, be rendered as an integrity constraint. If both text and a logical expression are provided the logical expression is to be taken as the canonical description. The logical expression could conform to an expression syntax like that of the Validation and Transformation Language (VTL: https://sdmx.org/?page_id=5096) or the Structured Data Transformation Language (SDTL: https://ddialliance.org/products/sdtl/1.0).</xs:documentation>
20 </xs:annotation>
21</xs:element>
22<xs:complexType name="ValueAndConceptDescriptionXsdType"
23 xml:id="ValueAndConceptDescriptionXsdType">
24 <xs:annotation>
25 <xs:documentation>Definition
26 ==========
27 Formal description of a set of values.
28
29 Examples
30 ========
31
32 1. The integers between 1 and 10, inclusive. The values of x satisfying the logicalExpression property: " (1 less than or equal to X less than or equalto 10) AND mod(x,10)=0" Also described with minimumValueInclusive = 1 and maximumValueInclusive = 10 (and datatype of integer).
33 2. The upper case letters A through C and X described with the regularExpression "/[A-CX]/".
34 3. A date-time described with the Unicode Locale Data Markup Language pattern yyyy.MM.dd G 'at' HH:mm:ss zzz.
35
36 Explanatory notes
37 =================
38 The value and concept description may be used to describe either a value domain or a conceptual domain. For a value domain, the value and concept description contains the details for a described" domain (as opposed to an enumerated domain). There are a number of properties which can be used for the description. The description could be just text such as: "an even number greater than zero", or a more formal logical expression like "x>0 and mod(x,2)=0". A regular expression might be useful for describing a textual domain. It could also employ a format pattern from the Unicode Locale Data Markup Language (LDML: http://www.unicode.org/reports/tr35/tr35.html). Some conceptual domains might be described with just a narrative. Others, though, might be described in much the same way as a value domain depending on the specificity of the concept. In ISO 11404 a value domain may be described either through enumeration or description, or both. This class provides the facility for that description. It may be just a text description, but a description through a logical expression is machine actionable and might, for example, be rendered as an integrity constraint. If both text and a logical expression are provided the logical expression is to be taken as the canonical description. The logical expression could conform to an expression syntax like that of the Validation and Transformation Language (VTL: https://sdmx.org/?page_id=5096) or the Structured Data Transformation Language (SDTL: https://ddialliance.org/products/sdtl/1.0).</xs:documentation>
39 </xs:annotation>
40 <xs:sequence>
41 <xs:element name="classificationLevel"
42 type="CategoryRelationCodeXsdType"
43 minOccurs="0"
44 maxOccurs="1"
45 xml:id="ValueAndConceptDescription-classificationLevel">
46 <xs:annotation>
47 <xs:documentation>Indicates the type of relationship, nominal, ordinal, interval, ratio, or continuous. Use where appropriate for the representation type.</xs:documentation>
48 </xs:annotation>
49 </xs:element>
50 <xs:element name="description"
51 type="InternationalStringXsdType"
52 minOccurs="0"
53 maxOccurs="1"
54 xml:id="ValueAndConceptDescription-description">
55 <xs:annotation>
56 <xs:documentation>A formal description of the set of values in human-readable language.</xs:documentation>
57 </xs:annotation>
58 </xs:element>
59 <xs:element name="formatPattern"
60 type="ControlledVocabularyEntryXsdType"
61 minOccurs="0"
62 maxOccurs="1"
63 xml:id="ValueAndConceptDescription-formatPattern">
64 <xs:annotation>
65 <xs:documentation>A pattern for a number as described in Unicode Locale Data Markup Language (LDML) (http://www.unicode.org/reports/tr35/tr35.html) Part 3: Numbers (http://www.unicode.org/reports/tr35/tr35-numbers.html#Number_Format_Patterns) and Part 4. Dates (http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Format_Patterns) . Examples would be #,##0.### to describe the pattern for a decimal number, or yyyy.MM.dd G 'at' HH:mm:ss zzz for a datetime pattern.</xs:documentation>
66 </xs:annotation>
67 </xs:element>
68 <xs:element name="identifier"
69 type="IdentifierXsdType"
70 minOccurs="0"
71 maxOccurs="1"
72 xml:id="ValueAndConceptDescription-identifier">
73 <xs:annotation>
74 <xs:documentation>Identifier for objects requiring short- or long-lasting referencing and management.</xs:documentation>
75 </xs:annotation>
76 </xs:element>
77 <xs:element name="logicalExpression"
78 type="ControlledVocabularyEntryXsdType"
79 minOccurs="0"
80 maxOccurs="1"
81 xml:id="ValueAndConceptDescription-logicalExpression">
82 <xs:annotation>
83 <xs:documentation>A logical expression where the values of "x" making the expression true are the members of the set of valid values. For example, "(all reals x such that x > 0)" describes the real numbers greater than 0.</xs:documentation>
84 </xs:annotation>
85 </xs:element>
86 <xs:element name="maximumValueExclusive"
87 type="xs:string"
88 minOccurs="0"
89 maxOccurs="1"
90 xml:id="ValueAndConceptDescription-maximumValueExclusive">
91 <xs:annotation>
92 <xs:documentation>A string denoting the maximum possible value (excluding this value). From the W3C Recommendation "Metadata Vocabulary for Tabular Data" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: "maxExclusive: An atomic property that contains a single number or string that is the maximum valid value (exclusive). The value of this property becomes the maximum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details."</xs:documentation>
93 </xs:annotation>
94 </xs:element>
95 <xs:element name="maximumValueInclusive"
96 type="xs:string"
97 minOccurs="0"
98 maxOccurs="1"
99 xml:id="ValueAndConceptDescription-maximumValueInclusive">
100 <xs:annotation>
101 <xs:documentation>A string denoting the maximum possible value. From the W3C Recommendation "Metadata Vocabulary for Tabular Data" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: "maximum: An atomic property that contains a single number or string that is the maximum valid value (inclusive); equivalent to maxInclusive. The value of this property becomes the maximum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details."</xs:documentation>
102 </xs:annotation>
103 </xs:element>
104 <xs:element name="minimumValueExclusive"
105 type="xs:string"
106 minOccurs="0"
107 maxOccurs="1"
108 xml:id="ValueAndConceptDescription-minimumValueExclusive">
109 <xs:annotation>
110 <xs:documentation>A string denoting the minimum possible value (excluding this value). From the W3C Recommendation "Metadata Vocabulary for Tabular Data" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: "minExclusive: An atomic property that contains a single number or string that is the minimum valid value (exclusive). The value of this property becomes the minimum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details."</xs:documentation>
111 </xs:annotation>
112 </xs:element>
113 <xs:element name="minimumValueInclusive"
114 type="xs:string"
115 minOccurs="0"
116 maxOccurs="1"
117 xml:id="ValueAndConceptDescription-minimumValueInclusive">
118 <xs:annotation>
119 <xs:documentation>A string denoting the minimum possible value. From the W3C Recommendation "Metadata Vocabulary for Tabular Data" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: "minimum: An atomic property that contains a single number or string that is the minimum valid value (inclusive); equivalent to minInclusive. The value of this property becomes the minimum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details."</xs:documentation>
120 </xs:annotation>
121 </xs:element>
122 <xs:element name="regularExpression"
123 type="TypedStringXsdType"
124 minOccurs="0"
125 maxOccurs="1"
126 xml:id="ValueAndConceptDescription-regularExpression">
127 <xs:annotation>
128 <xs:documentation>A regular expression where strings matching the expression belong to the set of valid values. Use typeOfContent to specify the syntax of the regularExpression found in content.</xs:documentation>
129 </xs:annotation>
130 </xs:element>
131 </xs:sequence>
132</xs:complexType>
Fragment for the class ValueAndConceptDescription (main ontology)
1# class ValueAndConceptDescription
2# based on the UML class DDICDIModels::DDICDILibrary::Classes::Representations::ValueAndConceptDescription
3cdi:ValueAndConceptDescription
4 a rdfs:Class, owl:Class, ucmis:Class;
5 rdfs:label "ValueAndConceptDescription";
6 rdfs:comment "Definition\n==========\nFormal description of a set of values. \n\nExamples\n========\n\n1. The integers between 1 and 10, inclusive. The values of x satisfying the logicalExpression property: \" (1 less than or equal to X less than or equalto 10) AND mod(x,10)=0\" Also described with minimumValueInclusive = 1 and maximumValueInclusive = 10 (and datatype of integer).\n2. The upper case letters A through C and X described with the regularExpression \"/[A-CX]/\".\n3. A date-time described with the Unicode Locale Data Markup Language pattern yyyy.MM.dd G 'at' HH:mm:ss zzz. \n\nExplanatory notes\n=================\nThe value and concept description may be used to describe either a value domain or a conceptual domain. For a value domain, the value and concept description contains the details for a described\" domain (as opposed to an enumerated domain). There are a number of properties which can be used for the description. The description could be just text such as: \"an even number greater than zero\", or a more formal logical expression like \"x>0 and mod(x,2)=0\". A regular expression might be useful for describing a textual domain. It could also employ a format pattern from the Unicode Locale Data Markup Language (LDML: http://www.unicode.org/reports/tr35/tr35.html). Some conceptual domains might be described with just a narrative. Others, though, might be described in much the same way as a value domain depending on the specificity of the concept. In ISO 11404 a value domain may be described either through enumeration or description, or both. This class provides the facility for that description. It may be just a text description, but a description through a logical expression is machine actionable and might, for example, be rendered as an integrity constraint. If both text and a logical expression are provided the logical expression is to be taken as the canonical description. The logical expression could conform to an expression syntax like that of the Validation and Transformation Language (VTL: https://sdmx.org/?page_id=5096) or the Structured Data Transformation Language (SDTL: https://ddialliance.org/products/sdtl/1.0)."@en;
7
8.
9
10cdi:ValueAndConceptDescription-classificationLevel
11 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
12 rdfs:label "classificationLevel";
13 rdfs:comment "Indicates the type of relationship, nominal, ordinal, interval, ratio, or continuous. Use where appropriate for the representation type."@en;
14 rdfs:domain cdi:ValueAndConceptDescription;
15 rdfs:range cdi:CategoryRelationCode;
16.
17
18cdi:ValueAndConceptDescription-description
19 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
20 rdfs:label "description";
21 rdfs:comment "A formal description of the set of values in human-readable language."@en;
22 rdfs:domain cdi:ValueAndConceptDescription;
23 rdfs:range cdi:InternationalString;
24.
25
26cdi:ValueAndConceptDescription-formatPattern
27 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
28 rdfs:label "formatPattern";
29 rdfs:comment "A pattern for a number as described in Unicode Locale Data Markup Language (LDML) (http://www.unicode.org/reports/tr35/tr35.html) Part 3: Numbers (http://www.unicode.org/reports/tr35/tr35-numbers.html#Number_Format_Patterns) and Part 4. Dates (http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Format_Patterns) . Examples would be #,##0.### to describe the pattern for a decimal number, or yyyy.MM.dd G 'at' HH:mm:ss zzz for a datetime pattern."@en;
30 rdfs:domain cdi:ValueAndConceptDescription;
31 rdfs:range cdi:ControlledVocabularyEntry;
32.
33
34cdi:ValueAndConceptDescription-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:ValueAndConceptDescription;
39 rdfs:range cdi:Identifier;
40.
41
42cdi:ValueAndConceptDescription-logicalExpression
43 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
44 rdfs:label "logicalExpression";
45 rdfs:comment "A logical expression where the values of \"x\" making the expression true are the members of the set of valid values. For example, \"(all reals x such that x > 0)\" describes the real numbers greater than 0."@en;
46 rdfs:domain cdi:ValueAndConceptDescription;
47 rdfs:range cdi:ControlledVocabularyEntry;
48.
49
50cdi:ValueAndConceptDescription-maximumValueExclusive
51 a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
52 rdfs:label "maximumValueExclusive";
53 rdfs:comment "A string denoting the maximum possible value (excluding this value). From the W3C Recommendation \"Metadata Vocabulary for Tabular Data\" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: \"maxExclusive: An atomic property that contains a single number or string that is the maximum valid value (exclusive). The value of this property becomes the maximum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.\""@en;
54 rdfs:domain cdi:ValueAndConceptDescription;
55 rdfs:range xsd:string;
56.
57
58cdi:ValueAndConceptDescription-maximumValueInclusive
59 a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
60 rdfs:label "maximumValueInclusive";
61 rdfs:comment "A string denoting the maximum possible value. From the W3C Recommendation \"Metadata Vocabulary for Tabular Data\" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: \"maximum: An atomic property that contains a single number or string that is the maximum valid value (inclusive); equivalent to maxInclusive. The value of this property becomes the maximum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.\""@en;
62 rdfs:domain cdi:ValueAndConceptDescription;
63 rdfs:range xsd:string;
64.
65
66cdi:ValueAndConceptDescription-minimumValueExclusive
67 a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
68 rdfs:label "minimumValueExclusive";
69 rdfs:comment "A string denoting the minimum possible value (excluding this value). From the W3C Recommendation \"Metadata Vocabulary for Tabular Data\" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: \"minExclusive: An atomic property that contains a single number or string that is the minimum valid value (exclusive). The value of this property becomes the minimum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.\""@en;
70 rdfs:domain cdi:ValueAndConceptDescription;
71 rdfs:range xsd:string;
72.
73
74cdi:ValueAndConceptDescription-minimumValueInclusive
75 a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
76 rdfs:label "minimumValueInclusive";
77 rdfs:comment "A string denoting the minimum possible value. From the W3C Recommendation \"Metadata Vocabulary for Tabular Data\" (https://www.w3.org/TR/tabular-metadata/) 5.11.2: \"minimum: An atomic property that contains a single number or string that is the minimum valid value (inclusive); equivalent to minInclusive. The value of this property becomes the minimum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.\""@en;
78 rdfs:domain cdi:ValueAndConceptDescription;
79 rdfs:range xsd:string;
80.
81
82cdi:ValueAndConceptDescription-regularExpression
83 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
84 rdfs:label "regularExpression";
85 rdfs:comment "A regular expression where strings matching the expression belong to the set of valid values. Use typeOfContent to specify the syntax of the regularExpression found in content."@en;
86 rdfs:domain cdi:ValueAndConceptDescription;
87 rdfs:range cdi:TypedString;
88.
Fragment for the class ValueAndConceptDescription (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 "ValueAndConceptDescription": "cdi:ValueAndConceptDescription",
7 "classificationLevel": {
8 "@id": "cdi:ValueAndConceptDescription-classificationLevel",
9 "@type": "@vocab",
10 "@context": {
11 "Continuous": "cdi:Continuous",
12 "Interval": "cdi:Interval",
13 "Nominal": "cdi:Nominal",
14 "Ordinal": "cdi:Ordinal",
15 "Ratio": "cdi:Ratio",
16 " comment ": "tag:json-should-support-trailing-commas"
17 }
18 },
19 "description": {
20 "@id": "cdi:ValueAndConceptDescription-description",
21 "@type": "@id",
22 "@context": "InternationalString.jsonld"
23 },
24 "formatPattern": {
25 "@id": "cdi:ValueAndConceptDescription-formatPattern",
26 "@type": "@id",
27 "@context": "ControlledVocabularyEntry.jsonld"
28 },
29 "identifier": {
30 "@id": "cdi:ValueAndConceptDescription-identifier",
31 "@type": "@id",
32 "@context": "Identifier.jsonld"
33 },
34 "logicalExpression": {
35 "@id": "cdi:ValueAndConceptDescription-logicalExpression",
36 "@type": "@id",
37 "@context": "ControlledVocabularyEntry.jsonld"
38 },
39 "maximumValueExclusive": {
40 "@id": "cdi:ValueAndConceptDescription-maximumValueExclusive",
41 "@type": "xsd:string"
42 },
43 "maximumValueInclusive": {
44 "@id": "cdi:ValueAndConceptDescription-maximumValueInclusive",
45 "@type": "xsd:string"
46 },
47 "minimumValueExclusive": {
48 "@id": "cdi:ValueAndConceptDescription-minimumValueExclusive",
49 "@type": "xsd:string"
50 },
51 "minimumValueInclusive": {
52 "@id": "cdi:ValueAndConceptDescription-minimumValueInclusive",
53 "@type": "xsd:string"
54 },
55 "regularExpression": {
56 "@id": "cdi:ValueAndConceptDescription-regularExpression",
57 "@type": "@id",
58 "@context": "TypedString.jsonld"
59 },
60
61 "isDescribedBy_OF_ConceptualDomain": {
62 "@reverse": "cdi:ConceptualDomain_isDescribedBy_ValueAndConceptDescription",
63 "@type": "@id"
64 },
65 "isDescribedBy_OF_SentinelValueDomain": {
66 "@reverse": "cdi:SentinelValueDomain_isDescribedBy_ValueAndConceptDescription",
67 "@type": "@id"
68 },
69 "isDescribedBy_OF_SubstantiveValueDomain": {
70 "@reverse": "cdi:SubstantiveValueDomain_isDescribedBy_ValueAndConceptDescription",
71 "@type": "@id"
72 },
73 " comment ": "tag:json-should-support-trailing-commas"
74 }
75 ],
76 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:12.",
77 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::Classes::Representations::ValueAndConceptDescription"
78}