Changes for page 3 SDMX Base Package
Last modified by Helena on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -26,10 +26,8 @@ 26 26 27 27 This group of classes forms the nucleus of the administration facets of SDMX objects. They provide features which are reusable by derived classes to support horizontal functionality such as identity, versioning etc. 28 28 29 -All classes derived from the abstract class //AnnotableArtefact// may have Annotations (or notes): this supports the need to add notes to all SDMX-ML elements. The Annotation is used to convey extra information to describe any SDMX construct. This information may be in the form of a URL reference and/or a multilingual text (represented by the association to 29 +All classes derived from the abstract class //AnnotableArtefact// may have Annotations (or notes): this supports the need to add notes to all SDMX-ML elements. The Annotation is used to convey extra information to describe any SDMX construct. This information may be in the form of a URL reference and/or a multilingual text (represented by the association to InternationalString). 30 30 31 -InternationalString). 32 - 33 33 The //IdentifiableArtefact// is an abstract class that comprises the basic attributes needed for identification. Concrete classes based on //IdentifiableArtefact// all inherit the ability to be uniquely identified. 34 34 35 35 The //NamableArtefact// is an abstract class that inherits from //IdentifiableArtefact //and in addition the +description and +name roles support multilingual descriptions and names for all objects based on //NameableArtefact//. The InternationalString supports the representation of a description in multiple locales (locale is similar to language but includes geographic variations such as Canadian French, US English etc.). The //LocalisedString// supports the representation of a description in one locale. ... ... @@ -40,70 +40,62 @@ 40 40 41 41 The inheritance chain from //AnnotableArtefact// through to //MaintainableArtefact// allows SDMX classes to inherit the features they need, from simple annotation, through identity, naming, to versioning and maintenance. 42 42 43 - **3.2.2.2 Definitions**41 +==== 3.2.2.2 Definitions ==== 44 44 45 -|**Class**|**Feature**|**Description** 46 -|//AnnotableArtefact//|((( 43 +(% style="width:902.294px" %) 44 +|**Class**|(% style="width:246px" %)**Feature**|(% style="width:480px" %)**Description** 45 +|//AnnotableArtefact//|(% style="width:246px" %)((( 47 47 Base inheritance sub classes are: 48 - 49 49 //IdentifiableArtefact// 50 -)))|Objects of classes derived from this can have attached annotations. 51 -|Annotation| |Additional descriptive information attached to an object. 52 -| |id|((( 48 +)))|(% style="width:480px" %)Objects of classes derived from this can have attached annotations. 49 +|Annotation|(% style="width:246px" %) |(% style="width:480px" %)Additional descriptive information attached to an object. 50 +| |(% style="width:246px" %)id|(% style="width:480px" %)((( 53 53 Identifier for the Annotation. 54 - 55 55 It can be used to disambiguate one Annotation from another where there are several Annotations for the same annotated object. 56 56 ))) 57 -| |title // //|A title used to identify an annotation.58 -| |type|Specifies how the annotation is to be processed. 59 -| |url|A link to external descriptive text. 60 -| |+text|An International String provides the multilingual text content of the annotation via this role. 61 -|//IdentifiableArtefact//|((( 54 +| |(% style="width:246px" %)title|(% style="width:480px" %)A title used to identify an annotation. 55 +| |(% style="width:246px" %)type|(% style="width:480px" %)Specifies how the annotation is to be processed. 56 +| |(% style="width:246px" %)url|(% style="width:480px" %)A link to external descriptive text. 57 +| |(% style="width:246px" %)+text|(% style="width:480px" %)An International String provides the multilingual text content of the annotation via this role. 58 +|//IdentifiableArtefact//|(% style="width:246px" %)((( 62 62 Superclass is 63 - 64 64 //AnnotableArtefact// 65 - 66 -Base inheritance sub classes are~:// // 67 - 61 +Base inheritance sub classes are: 68 68 //NameableArtefact// 69 -)))|Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact. 70 -| |id|The unique identifier of the object. 71 -| |uri|Universal resource identifier that may or may not be resolvable. 72 -| |urn|Universal resource name – this is for use in registries: all registered objects have a urn. 73 -|//NameableArtefact//|((( 63 +)))|(% style="width:480px" %)Provides identity to all derived classes. It also provides annotations to derived classes because it is a subclass of Annotable Artefact. 64 +| |(% style="width:246px" %)id|(% style="width:480px" %)The unique identifier of the object. 65 +| |(% style="width:246px" %)uri|(% style="width:480px" %)Universal resource identifier that may or may not be resolvable. 66 +| |(% style="width:246px" %)urn|(% style="width:480px" %)Universal resource name – this is for use in registries: all registered objects have a urn. 67 +|//NameableArtefact//|(% style="width:246px" %)((( 74 74 Superclass is 75 - 76 76 //IdentifiableArtefact// Base inheritance sub classes are: 77 - 78 78 //VersionableArtefact// 79 -)))|Provides a Name and Description to all derived classes in addition to identification and annotations. 80 -| |+description|A multi-lingual description is provided by this role via the International String class. 81 -| |+name|A multi-lingual name is provided by this role via the International String class 82 -|InternationalString| |The International String is a collection of Localised Strings and supports the representation of text in multiple locales. 83 -|LocalisedString| |The Localised String supports the representation of text in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.). 84 -| |label|Label of the string. 85 -| |locale|The geographic locale of the string e.g French, Canadian French. 86 -|//VersionableArtefact//|((( 71 +)))|(% style="width:480px" %)Provides a Name and Description to all derived classes in addition to identification and annotations. 72 +| |(% style="width:246px" %)+description|(% style="width:480px" %)A multi-lingual description is provided by this role via the International String class. 73 +| |(% style="width:246px" %)+name|(% style="width:480px" %)A multi-lingual name is provided by this role via the International String class 74 +|InternationalString|(% style="width:246px" %) |(% style="width:480px" %)The International String is a collection of Localised Strings and supports the representation of text in multiple locales. 75 +|LocalisedString|(% style="width:246px" %) |(% style="width:480px" %)The Localised String supports the representation of text in one locale (locale is similar to language but includes geographic variations such as Canadian French, US English etc.). 76 +| |(% style="width:246px" %)label|(% style="width:480px" %)Label of the string. 77 +| |(% style="width:246px" %)locale|(% style="width:480px" %)The geographic locale of the string e.g French, Canadian French. 78 +|//VersionableArtefact//|(% style="width:246px" %)((( 87 87 Superclass is 88 - 89 89 //NameableArtefact// Base inheritance sub classes are: 90 - 91 91 //MaintainableArtefact// 92 -)))|Provides versioning information for all derived objects. 93 -| |version|A version string following an agreed convention 94 -| |validFrom|Date from which the version is valid 95 -| |validTo|Date from which version is superceded 96 -|//MaintainableArtefact//|((( 82 +)))|(% style="width:480px" %)Provides versioning information for all derived objects. 83 +| |(% style="width:246px" %)version|(% style="width:480px" %)A version string following an agreed convention 84 +| |(% style="width:246px" %)validFrom|(% style="width:480px" %)Date from which the version is valid 85 +| |(% style="width:246px" %)validTo|(% style="width:480px" %)Date from which version is superceded 86 +|//MaintainableArtefact//|(% style="width:246px" %)((( 97 97 Inherits from 98 98 99 99 //VersionableArtefact// 100 -)))|An abstract class to group together primary structural metadata artefacts that are maintained by an Agency. 101 -| |final|Defines whether a maintained artefact is draft or final. 102 -| |isExternalReference|If set to “true” it indicates that the content of the object is held externally. 103 -| |structureURL|The URL of an SDMX-ML document containing the external object. 104 -| |serviceURL|The URL of an SDMX-compliant web service from which the external object can be retrieved. 105 -| |+maintainer // //|Association to the Maintenance Agency responsible for maintaining the artefact.106 -|Agency| |See section on “Organisations” 90 +)))|(% style="width:480px" %)An abstract class to group together primary structural metadata artefacts that are maintained by an Agency. 91 +| |(% style="width:246px" %)final|(% style="width:480px" %)Defines whether a maintained artefact is draft or final. 92 +| |(% style="width:246px" %)isExternalReference|(% style="width:480px" %)If set to “true” it indicates that the content of the object is held externally. 93 +| |(% style="width:246px" %)structureURL|(% style="width:480px" %)The URL of an SDMX-ML document containing the external object. 94 +| |(% style="width:246px" %)serviceURL|(% style="width:480px" %)The URL of an SDMX-compliant web service from which the external object can be retrieved. 95 +| |(% style="width:246px" %)+maintainer|(% style="width:480px" %)Association to the Maintenance Agency responsible for maintaining the artefact. 96 +|Agency|(% style="width:246px" %) |(% style="width:480px" %)See section on “Organisations” 107 107 108 108 == {{id name="_Toc370972"/}}3.3 Basic Inheritance == 109 109 ... ... @@ -169,7 +169,8 @@ 169 169 170 170 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_a2879920.jpg||height="602" width="614"]] 171 171 172 -====== Figure 12 The Item Scheme Pattern ====== 162 +(% class="wikigeneratedid" id="HFigure12TheItemSchemePattern" %) 163 +**Figure 12 The Item Scheme Pattern** 173 173 174 174 ===== {{id name="_Toc370981"/}}3.5.3 Explanation of the Diagram ===== 175 175 ... ... @@ -195,73 +195,47 @@ 195 195 196 196 ==== 3.5.3.2 Definitions ==== 197 197 198 -|**Class**|**Feature**|**Description** 199 -|//ItemScheme//|((( 189 +(% style="width:911.294px" %) 190 +|**Class**|(% style="width:246px" %)**Feature**|(% style="width:478px" %)**Description** 191 +|//ItemScheme//|(% style="width:246px" %)((( 200 200 Inherits from: 201 - 202 202 //MaintainableArtefact// 203 - 204 204 Direct sub classes are: 205 - 206 206 CategoryScheme 207 - 208 208 ConceptScheme 209 - 210 210 Codelist 211 -)))|The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common. 212 -| |((( 198 +)))|(% style="width:478px" %)The descriptive information for an arrangement or division of objects into groups based on characteristics, which the objects have in common. 199 +| |(% style="width:246px" %)((( 213 213 ReportingTaxonomy 214 - 215 215 //OrganisationScheme// 216 - 217 217 Transformation Scheme 218 - 219 219 CustomTypeScheme 220 - 221 221 NamePersonasationScheme 222 - 223 223 RuletScheme 224 - 225 225 VtlMappingScheme 226 - 227 227 UserDefinedOperatorScheme 228 -)))| 229 -| |isPartial|Denotes whether the Item Scheme contains a sub set of the full set of Items in the maintained scheme. 230 -| |items|Association to the Items in the scheme. 231 -|//Item//|((( 208 +)))|(% style="width:478px" %) 209 +| |(% style="width:246px" %)isPartial|(% style="width:478px" %)Denotes whether the Item Scheme contains a sub set of the full set of Items in the maintained scheme. 210 +| |(% style="width:246px" %)items|(% style="width:478px" %)Association to the Items in the scheme. 211 +|//Item//|(% style="width:246px" %)((( 232 232 Inherits from: 233 - 234 234 //NameableArtefact// 235 - 236 -Direct sub classes are 237 - 238 -Category 239 - 214 +Direct sub classes are Category 240 240 Concept 241 - 242 242 Code 243 - 244 244 ReportingCategory 245 - 246 246 //Organisation// 247 - 248 248 Transformation 249 - 250 250 CustomType 251 - 252 252 NamePersonlisation 253 - 254 254 Ruleset 255 - 256 256 VtlMapping 257 - 258 -UserDefinedOperator// // 259 -)))|((( 224 +UserDefinedOperator 225 +)))|(% style="width:478px" %)((( 260 260 The Item is an item of content in an Item Scheme. This may be a node in a taxonomy or ontology, a code in a code list etc. 261 - 262 262 Note that at the conceptual level the Organisation is not hierarchic 263 263 ))) 264 -| |hierarchy|This allows an Item optionally to have one or more child Items. 229 +| |(% style="width:246px" %)hierarchy|(% style="width:478px" %)This allows an Item optionally to have one or more child Items. 265 265 266 266 == {{id name="_Toc370982"/}}3.6 The Structure Pattern == 267 267 ... ... @@ -277,7 +277,8 @@ 277 277 278 278 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_b6478a73.png||height="774" width="556"]] 279 279 280 -====== Figure 14: Representation within the Structure Pattern ====== 245 +(% class="wikigeneratedid" id="HFigure14:RepresentationwithintheStructurePattern" %) 246 +**Figure 14: Representation within the Structure Pattern** 281 281 282 282 === {{id name="_Toc370985"/}}3.6.3 Explanation of the Diagrams === 283 283 ... ... @@ -301,7 +301,7 @@ 301 301 302 302 __ReportStructure__: MetadataAttribute 303 303 304 -Each Component takes its semantic (and possibly also its representation) from a Concept in 773a ConceptScheme. This is represented by the conceptIdentity association to Concept.270 +Each Component takes its semantic (and possibly also its representation) from a Concept in a ConceptScheme. This is represented by the conceptIdentity association to Concept. 305 305 306 306 The //Component// may also have a localRepresentation, This allows a concrete class, such as Dimension, to specify its representation which is local to the //Structure// in which it is contained (for Dimension this will be DataStructureDefinition), and thus overrides any coreRepresentation specified for the Concept. 307 307 ... ... @@ -316,126 +316,98 @@ 316 316 317 317 The //Structure// may be used by one or more //StructureUsage//. An example of this in terms of concrete classes is that a DataflowDefinition (sub class of //StructureUsage//) may use a particular DataStructureDefinition (sub class of //Structure//), and similar constructs apply for the MetadataflowDefinition (link to MetadataStructureDefinition). 318 318 319 - **3.6.3.2 Definitions**285 +==== 3.6.3.2 Definitions ==== 320 320 321 -|**Class**|**Feature**|**Description** 287 +(% style="width:1001.29px" %) 288 +|**Class**|**Feature**|(% style="width:537px" %)**Description** 322 322 |//StructureUsage//|((( 323 323 Inherits from: 324 - 325 325 //MaintainableArtefact// 326 - 327 327 Sub classes are: 328 - 329 329 DataflowDefinition 330 - 331 -MetadataflowDefinition// // 332 -)))|An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow Definition which is linked to a given structure – in this case the Data Structure Definition. 333 -| |structure|An association to a Structure specifying the structure of the artefact. 294 +MetadataflowDefinition 295 +)))|(% style="width:537px" %)An artefact whose components are described by a Structure. In concrete terms (sub-classes) an example would be a Dataflow Definition which is linked to a given structure – in this case the Data Structure Definition. 296 +| |structure|(% style="width:537px" %)An association to a Structure specifying the structure of the artefact. 334 334 |//Structure//|((( 335 335 Inherits from: 336 - 337 337 //MaintainableArtefact// 338 - 339 339 Sub classes are: 340 - 341 341 DataStructure 342 - 343 343 Definition 344 - 345 345 MetadataStructure 346 - 347 347 Definition 348 -)))|Abstract specification of a list of lists to define a complex tabular structure. A concrete example of this would be statistical concepts, code lists, and their organisation in a data or metadata structure definition, defined by a centre institution, usually for the exchange of statistical information with its partners. 349 -| |grouping|A composite association to one or more component lists. 305 +)))|(% style="width:537px" %)Abstract specification of a list of lists to define a complex tabular structure. A concrete example of this would be statistical concepts, code lists, and their organisation in a data or metadata structure definition, defined by a centre institution, usually for the exchange of statistical information with its partners. 306 +| |grouping|(% style="width:537px" %)A composite association to one or more component lists. 350 350 |//ComponentList//|((( 351 351 Inherits from: 352 - 353 353 //IdentifiableArtefact// 354 - 355 355 Sub classes are: 356 - 357 357 DimensionDescriptor 358 - 359 359 GroupDimension 360 - 361 361 Descriptor 362 - 363 363 MeasureDescriptor 364 - 365 365 AttributeDescriptor 366 - 367 367 MetadataTarget 368 - 369 369 ReportStructure 370 -)))|An abstract definition of a list of components. A concrete example is a Dimension Descriptor which defines the list of Dimensions in a Data Structure Definition. 371 -| |components|An aggregate association to one or more components which make up the list. 318 +)))|(% style="width:537px" %)An abstract definition of a list of components. A concrete example is a Dimension Descriptor which defines the list of Dimensions in a Data Structure Definition. 319 +| |components|(% style="width:537px" %)An aggregate association to one or more components which make up the list. 372 372 |//Component//|((( 373 373 Inherits from: 374 - 375 375 //IdentifiableArtefact// 376 - 377 377 Sub classes are: 378 - 379 379 PrimaryMeasure 380 - 381 381 DataAttribute 382 - 383 -//DimensionComponent// 384 - 385 -//TargetObject// 386 - 326 +//DimensionComponent 327 +TargetObject// 387 387 MetadataAttribute 388 -)))|A component is an abstract super class used to define qualitative and quantitative data and metadata items that belong to a Component List and hence a Structure. Component is refined through its sub-classes. 389 -| |conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component 390 -| |localRepresentation|Association to the Representation of the Component if this is different from the coreRepresentation of the Concept which the Component uses (ConceptUsage) 391 -|Representation| |The allowable value or format for Component or Concept 392 -| |+enumerated|Association to an enumerated list that contains the allowable content for the Component when reported in a data or metadata set. The type of enumerated list that is allowed for any concrete Component is shown in the constraints on the association (e.g. Identifier Component can have any of the sub classes of Item Scheme, whereas Measure Dimension must have a Concept Scheme). 393 -| |+nonEnumerated|Association to a set of Facets that define the allowable format for the content of the Component when reported in a data or metadata set. 394 -|Facet| |Defines the format for the content of the Component when reported in a data or metadata set. 395 -| |facetType|A specific content type which is constrained by the FacetType enumeration 396 -| |facetValueType|((( 329 +)))|(% style="width:537px" %)A component is an abstract super class used to define qualitative and quantitative data and metadata items that belong to a Component List and hence a Structure. Component is refined through its sub-classes. 330 +| |conceptIdentity|(% style="width:537px" %)Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component 331 +| |localRepresentation|(% style="width:537px" %)Association to the Representation of the Component if this is different from the coreRepresentation of the Concept which the Component uses (ConceptUsage) 332 +|Representation| |(% style="width:537px" %)The allowable value or format for Component or Concept 333 +| |+enumerated|(% style="width:537px" %)Association to an enumerated list that contains the allowable content for the Component when reported in a data or metadata set. The type of enumerated list that is allowed for any concrete Component is shown in the constraints on the association (e.g. Identifier Component can have any of the sub classes of Item Scheme, whereas Measure Dimension must have a Concept Scheme). 334 +| |+nonEnumerated|(% style="width:537px" %)Association to a set of Facets that define the allowable format for the content of the Component when reported in a data or metadata set. 335 +|Facet| |(% style="width:537px" %)Defines the format for the content of the Component when reported in a data or metadata set. 336 +| |facetType|(% style="width:537px" %)A specific content type which is constrained by the FacetType enumeration 337 +| |facetValueType|(% style="width:537px" %)((( 397 397 The format of the value of a Component when reported in a data or metadata set. 398 398 399 399 This is contrained by the FacetValueType enumeration. 400 400 ))) 401 -| |+itemSchemeFacet|Defines the format of the identifiers in an Item Scheme used by a Component. Typically this would define the number of characters (length) of the identifier. 402 -|ExtendedFacet| |This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute 342 +| |+itemSchemeFacet|(% style="width:537px" %)Defines the format of the identifiers in an Item Scheme used by a Component. Typically this would define the number of characters (length) of the identifier. 343 +|ExtendedFacet| |(% style="width:537px" %)This has the same function as Facet but allows additionally an XHTML representation. This is constrained for use with a Metadata Attribute 403 403 404 -The specification of the content and use of the sub classes to ,,ComponentList,,and,,Component,,can be found in the section in which they are used (DataStructureDefinition and MetadataStructureDefinition)345 +The specification of the content and use of the sub classes to ComponentList and Component can be found in the section in which they are used (DataStructureDefinition and MetadataStructureDefinition) 405 405 406 406 ==== 3.6.3.3 Representation Constructs ==== 407 407 408 408 The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, 818 and have equivalents in most current implementation platforms: 409 409 410 -: 411 - 412 412 ((( 413 -|**SDMX Facet Value Type**|**XML Schema Data Type **|**.NET Framework Type**|**Java Data Type** 414 -|String|xsd:string|System.String|java.lang.String 415 -|Big Integer|xsd:integer|System.Decimal|java.math.BigInteger 416 -|Integer|xsd:int|System.Int32|int 417 -|Long|xsd.long|System.Int64|long 418 -|Short|xsd:short|System.Int16|short 419 -|Decimal|xsd:decimal|System.Decimal|java.math.BigDecimal 420 -|Float|xsd:float|System.Single|float 421 -|Double|xsd:double|System.Double|double 422 -|Boolean|xsd:boolean|System.Boolean|boolean 423 -|URI|xsd:anyURI|System.Uri|Java.net.URI or java.lang.String 424 -|DateTime|xsd:dateTime|System.DateTime|javax.xml.datatype.XMLG regorianCalendar 425 -|Time|xsd:time|System.DateTime|javax.xml.datatype.XMLG regorianCalendar 426 -|GregorianYear|xsd:gYear|System.DateTime|javax.xml.datatype.XMLG regorianCalendar 427 -|GregorianMonth|xsd:gYearMonth|System.DateTime|javax.xml.datatype.XMLG regorianCalendar 428 -|GregorianDay|xsd:date|System.DateTime|javax.xml.datatype.XMLG regorianCalendar 429 -|Day, MonthDay, Month|xsd:g*|System.DateTime|javax.xml.datatype.XMLG regorianCalendar 430 -|Duration|xsd:duration|System.TimeSpan|javax.xml.datatype.Dura tion 352 +(% style="width:1034.29px" %) 353 +|(% style="width:222px" %)**SDMX Facet Value Type**|(% style="width:229px" %)**XML Schema Data Type**|(% style="width:216px" %)**.NET Framework Type**|(% style="width:354px" %)**Java Data Type** 354 +|(% style="width:222px" %)String|(% style="width:229px" %)xsd:string|(% style="width:216px" %)System.String|(% style="width:354px" %)java.lang.String 355 +|(% style="width:222px" %)Big Integer|(% style="width:229px" %)xsd:integer|(% style="width:216px" %)System.Decimal|(% style="width:354px" %)java.math.BigInteger 356 +|(% style="width:222px" %)Integer|(% style="width:229px" %)xsd:int|(% style="width:216px" %)System.Int32|(% style="width:354px" %)int 357 +|(% style="width:222px" %)Long|(% style="width:229px" %)xsd.long|(% style="width:216px" %)System.Int64|(% style="width:354px" %)long 358 +|(% style="width:222px" %)Short|(% style="width:229px" %)xsd:short|(% style="width:216px" %)System.Int16|(% style="width:354px" %)short 359 +|(% style="width:222px" %)Decimal|(% style="width:229px" %)xsd:decimal|(% style="width:216px" %)System.Decimal|(% style="width:354px" %)java.math.BigDecimal 360 +|(% style="width:222px" %)Float|(% style="width:229px" %)xsd:float|(% style="width:216px" %)System.Single|(% style="width:354px" %)float 361 +|(% style="width:222px" %)Double|(% style="width:229px" %)xsd:double|(% style="width:216px" %)System.Double|(% style="width:354px" %)double 362 +|(% style="width:222px" %)Boolean|(% style="width:229px" %)xsd:boolean|(% style="width:216px" %)System.Boolean|(% style="width:354px" %)boolean 363 +|(% style="width:222px" %)URI|(% style="width:229px" %)xsd:anyURI|(% style="width:216px" %)System.Uri|(% style="width:354px" %)Java.net.URI or java.lang.String 364 +|(% style="width:222px" %)DateTime|(% style="width:229px" %)xsd:dateTime|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar 365 +|(% style="width:222px" %)Time|(% style="width:229px" %)xsd:time|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar 366 +|(% style="width:222px" %)GregorianYear|(% style="width:229px" %)xsd:gYear|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar 367 +|(% style="width:222px" %)GregorianMonth|(% style="width:229px" %)xsd:gYearMonth|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar 368 +|(% style="width:222px" %)GregorianDay|(% style="width:229px" %)xsd:date|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar 369 +|(% style="width:222px" %)Day, MonthDay, Month|(% style="width:229px" %)xsd:g*|(% style="width:216px" %)System.DateTime|(% style="width:354px" %)javax.xml.datatype.XMLG regorianCalendar 370 +|(% style="width:222px" %)Duration|(% style="width:229px" %)xsd:duration|(% style="width:216px" %)System.TimeSpan|(% style="width:354px" %)javax.xml.datatype.Dura tion 431 431 ))) 432 432 433 -There are also a number of SDMX data types which do not have these direct 822correspondences, often because they are composite representations or restrictions of a823broader data type. These are detailed in Section 6 of the standards.373 +There are also a number of SDMX data types which do not have these direct correspondences, often because they are composite representations or restrictions of a broader data type. These are detailed in Section 6 of the standards. 434 434 435 -The ,,Representation,,is composed of,,Facet,,s, each of which conveys characteristic826information related to the definition of a value domain. Often a set of Facets are needed to827convey the required semantic. For example, a sequence is defined by a minimum of two828Facets: one to define the start value, and one to define the interval.375 +The Representation is composed of Facets, each of which conveys characteristic information related to the definition of a value domain. Often a set of Facets are needed to convey the required semantic. For example, a sequence is defined by a minimum of two Facets: one to define the start value, and one to define the interval. 436 436 437 -: 438 - 439 439 ((( 440 440 |**Facet Type**|**Explanation**| 441 441 |isSequence|The isSequence facet indicates whether the values are intended to be ordered, and it may work in combination with the interval, startValue, and endValue facet or the timeInterval, startTime, and endTime, facets. If this attribute holds a value of true, a start value or time and a numeric or time interval must supplied. If an end value is not given, then the sequence continues indefinitely.|