Changes for page Part IV. Data and Metadata Namespaces
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -471,17 +471,21 @@ 471 471 **//TimeSeriesObsType//: **TimeSeriesObsType defines the abstract structure of a time series observation. The observation must be provided a value for the time dimension. This time value should disambiguate the observation within the series in which it is defined (i.e. there should not be another observation with the same time value). The observation can contain an observed value and/or attribute values. The same rules for derivation as the base observation type apply to this specialized observation. 472 472 473 473 Derivation: 474 -* //com:AnnotableType// (extension) 475 -** //ObsType// (restriction) 476 -*** //TimeSeriesObsType// 477 477 475 +//com:AnnotableType// (extension) 476 + //ObsType// (restriction) 477 + //TimeSeriesObsType// 478 + 478 478 Attributes: 480 + 479 479 TIME_PERIOD, REPORTING_YEAR_START_DAY?, OBS_VALUE? 480 480 481 481 Content: 484 + 482 482 com:Annotations? 483 483 484 484 Attribute Documentation: 488 + 485 485 |**Name**|**Type**|**Documentation** 486 486 |TIME_PERIOD|com: ObservationalTimePer iodType|The TIME_PERIOD attribute is an explicit attribute for the time dimension. This is declared in the base schema since it has a fixed identifier and representation. Since this data is structured to be time series only, this attribute is always required. If the time dimension specifies a more specific representation of time the derived type will restrict the type definition to the appropriate type. 487 487 |REPORTING_YEAR_START_DAY|xs:gMonthDay|The REPORTING_YEAR_START_DAY attribute is an explict attribute for the reporting year start day, which provides context to the time dimension when its value contains a reporting period (e.g. 2010-Q1). This attribute is used to state the month and day that the reporting year begins (e.g. ~-~-07-01 for July 1st). In the absence of an explicit value provided in this attribute, all reporting period values will be assumed to be based on a reporting year start day of January 1. This is declared in the base schema since it has a fixed identifier and representation. The derived observation type may either require or prohibit this attribute, depending on whether the data structure declared the reporting year start day attribute and if so, the attribute relationship and assignment status assigned to it. ... ... @@ -488,10 +488,13 @@ 488 488 |OBS_VALUE|xs:anySimpleType|The OBS_VALUE attribute is an explicit attribute for the primary measure, which is intended to hold the value for the observation. This is declared in the base schema since it has a fixed identifier. This attribute is un-typed, since the representation of the observed value can vary widely. Derived types will restrict this to be a type based on the representation of the primary measure. In the case that an explicit measure is used, the derived type for a given measure might further restrict the type of the primary measure to be more specific to the core representation for the measure concept. Note that it is required that in the case of multiple measures being used, that the representation of the primary measure is broad enough to handle the various representations of the measure concepts. 489 489 490 490 Element Documentation: 495 + 491 491 |**Name**|**Type**|**Documentation** 492 492 |com:Annotations|com:AnnotationsType|Annotations is a reusable element the provides for a collection of annotations. It has been made global so that restrictions of types that extend AnnotatableType my reference it. 493 493 494 -=== Simple Types === 499 +1. 500 +11. 501 +111. Simple Types 495 495 496 496 **DataScopeType: **DataScopeType is an enumeration of the possible validity scopes for a data set. These scopes indicate the level at which the data is stated to be valid. 497 497 ... ... @@ -498,6 +498,7 @@ 498 498 Derived by restriction of xs:string . 499 499 500 500 Enumerations: 508 + 501 501 |**Value**|**Documentation** 502 502 |DataStructure|The data set conforms simply to the data structure definition as it is defined, without regard to any constraints. 503 503 |ConstrainedDataStructure|The data set conforms to the known allowable content constraints applied to the data structure definition. ... ... @@ -504,35 +504,46 @@ 504 504 |Dataflow|The data set conforms to the known allowable content constraints applied to the dataflow. 505 505 |ProvisionAgreement|The data set conforms to the known allowable content constraints applied to the provision agreement. 506 506 507 -== Generic Metadata Namespace == 515 +1. 516 +11. Generic Metadata Namespace 508 508 509 509 **http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/metadata/generic** 510 510 511 -=== Summary === 520 +1. 521 +11. 522 +111. Summary 512 512 513 513 Referenced Namespaces: 525 + 514 514 |**Namespace**|**Prefix** 515 515 |http:~/~/www.sdmx.org/resources/sdmxml/schemas/v2_1/common|com 516 516 |http:~/~/www.w3.org/2001/XMLSchema|xs 517 517 518 518 Contents: 531 + 519 519 6 Complex Types 520 520 521 -=== Complex Types === 534 +1. 535 +11. 536 +111. Complex Types 522 522 523 523 **MetadataSetType: **MetadataSetType describes the structure for a metadata set, which contains a collection of reported metadata against a set of values for a given full or partial target identifier, as described in a metadata structure definition. The metadata set may contain reported metadata for multiple report structures defined in a metadata structure definition. 524 524 525 525 Derivation: 526 -* //com:AnnotableType// (extension) 527 -** MetadataSetType 528 528 542 +//com:AnnotableType// (extension) 543 + MetadataSetType 544 + 529 529 Attributes: 546 + 530 530 structureRef, setID?, action?, reportingBeginDate?, reportingEndDate?, validFromDate?, validToDate?, publicationYear?, publicationPeriod? 531 531 532 532 Content: 550 + 533 533 com:Annotations?, com:Name*, DataProvider?, Report+ 534 534 535 535 Attribute Documentation: 554 + 536 536 |**Name**|**Type**|**Documentation** 537 537 |structureRef|xs:IDREF|The structureRef contains a reference to a structural specification in the header of a data or reference metadata message. The structural specification details which structure the data or reference metadata conforms to, as well as providing additional information such as how the data is structure (e.g. which dimension occurs at the observation level for a data set). 538 538 |setID|com:IDType|The setID provides an identification of the data or metadata set.