Changes for page 3 SDMX Base Package

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -282,118 +282,92 @@
282	282
283	283	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).
284	284
285		-**3.6.3.2 Definitions**
	285	+==== 3.6.3.2 Definitions ====
286	286
287		-|**Class**|**Feature**|**Description**
	287	+(% style="width:1001.29px" %)
	288	+|**Class**|**Feature**|(% style="width:537px" %)**Description**
288	288	|//StructureUsage//|(((
289	289	Inherits from:
290		-
291	291	//MaintainableArtefact//
292		-
293	293	Sub classes are:
294		-
295	295	DataflowDefinition
296		-
297		-MetadataflowDefinition//    //
298		-)))|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.
299		-| |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.
300	300	|//Structure//|(((
301	301	Inherits from:
302		-
303	303	//MaintainableArtefact//
304		-
305	305	Sub classes are:
306		-
307	307	DataStructure
308		-
309	309	Definition
310		-
311	311	MetadataStructure
312		-
313	313	Definition
314		-)))|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.
315		-| |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.
316	316	|//ComponentList//|(((
317	317	Inherits from:
318		-
319	319	//IdentifiableArtefact//
320		-
321	321	Sub classes are:
322		-
323	323	DimensionDescriptor
324		-
325	325	GroupDimension
326		-
327	327	Descriptor
328		-
329	329	MeasureDescriptor
330		-
331	331	AttributeDescriptor
332		-
333	333	MetadataTarget
334		-
335	335	ReportStructure
336		-)))|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.
337		-| |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.
338	338	|//Component//|(((
339	339	Inherits from:
340		-
341	341	//IdentifiableArtefact//
342		-
343	343	Sub classes are:
344		-
345	345	PrimaryMeasure
346		-
347	347	DataAttribute
348		-
349		-//DimensionComponent//
350		-
351		-//TargetObject//
352		-
	326	+//DimensionComponent
	327	+TargetObject//
353	353	MetadataAttribute
354		-)))|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.
355		-| |conceptIdentity|Association to a Concept in a Concept Scheme that identifies and defines the semantic of the Component
356		-| |localRepresentation|Association to the Representation of the Component if this is different from the coreRepresentation of the Concept which the Component uses (ConceptUsage)
357		-|Representation| |The allowable value or format for Component or Concept
358		-| |+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).
359		-| |+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.
360		-|Facet| |Defines the format for the content of the Component when reported in a data or metadata set.
361		-| |facetType|A specific content type which is constrained by the FacetType enumeration
362		-| |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" %)(((
363	363	The format of the value of a Component when reported in a data or metadata set.
364	364
365	365	This is contrained by the FacetValueType enumeration.
366	366	)))
367		-| |+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.
368		-|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
369	369
370		-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)
371	371
372	372	==== 3.6.3.3 Representation Constructs ====
373	373
374	374	The majority of SDMX FacetValueTypes are compatible with those found in XML Schema, 818 and have equivalents in most current implementation platforms:
375	375
376		-:
377		-
378	378	(((
379		-|**SDMX Facet Value Type**|**XML Schema Data Type     **|**.NET Framework Type**|**Java Data Type**
380		-|String|xsd:string|System.String|java.lang.String
381		-|Big Integer|xsd:integer|System.Decimal|java.math.BigInteger
382		-|Integer|xsd:int|System.Int32|int
383		-|Long|xsd.long|System.Int64|long
384		-|Short|xsd:short|System.Int16|short
385		-|Decimal|xsd:decimal|System.Decimal|java.math.BigDecimal
386		-|Float|xsd:float|System.Single|float
387		-|Double|xsd:double|System.Double|double
388		-|Boolean|xsd:boolean|System.Boolean|boolean
389		-|URI|xsd:anyURI|System.Uri|Java.net.URI or java.lang.String
390		-|DateTime|xsd:dateTime|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
391		-|Time|xsd:time|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
392		-|GregorianYear|xsd:gYear|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
393		-|GregorianMonth|xsd:gYearMonth|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
394		-|GregorianDay|xsd:date|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
395		-|Day, MonthDay, Month|xsd:g*|System.DateTime|javax.xml.datatype.XMLG regorianCalendar
396		-|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
397	397	)))
398	398
399	399	There are also a number of SDMX data types which do not have these direct 822 correspondences, often because they are composite representations or restrictions of a 823 broader data type. These are detailed in Section 6 of the standards.