Skip to Content

Changes for page Schema and Documentation

Last modified by Helena on 2025/09/10 11:19
From version 5.1
edited by Artur
on 2025/07/14 10:19
Change comment: Imported from XAR
To version 1.1
edited by Helena
on 2025/07/03 14:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Schema and Documentation
1 +SDMX-ML: Schema and Documentation
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.arturkryazhev
1 +xwiki:XWiki.helena
Content
... ... @@ -24,23 +24,23 @@
24 24  * Generic schema for [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] sets (“SDMXMetadataGeneric.xsd”)
25 25  * Metadata-structure-definition-specific schema for [[metadata sets>>doc:sdmx:Glossary.Metadata set.WebHome]] (“SDMXMetadataStructured.xsd”)
26 26  
27 -== 1.3. Fostering the Use of a Standard SDMX-ML ==
27 += 2. Fostering the Use of a Standard SDMX-ML =
28 28  
29 29  In addition to these different formats, standard mappings and corresponding transformation tools have been developed for the creation of data structure-specific schemas from structure descriptions, to transform XML data instances from one XML data description format to another, and from these formats into the corresponding [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] messages. This (% style="color:#e74c3c" %)level(%%) of free tools support will foster the early use of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] and permit the data to be easily used across all processes, which is otherwise a difficult requirement to meet. Ultimately, it is the fact that all formats share a common information model that enables this approach to meet the wide set of [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] requirements.
30 30  
31 -= 2. NORMATIVE REFERENCES =
31 += 3. NORMATIVE REFERENCES =
32 32  
33 33  W3C XML Schema Definition Language, (% style="color:#e74c3c" %)version(%%) 1.0 (URL: http:~/~/www.w3c.org/XML/Schema#dev), World Wide Web Consortium
34 34  
35 35  W3C Extensible Markup Language, (% style="color:#e74c3c" %)version(%%) 1.0, Third Edition (URL: http:~/~/www.w3c.org/TR/2004/REC-xml-20040204/), World Wide Web Consortium
36 36  
37 -= 3. CONFORMANCE =
37 += 4. CONFORMANCE =
38 38  
39 39  Part IV (SDMX_2_1_SECTION_03A_PART_IV_DATA) of this document is normative, providing rules for the creation of conformant [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] XML instances and W3C XML Schemas.
40 40  
41 -= 4. DESIGN OVERVIEW =
41 += 5. DESIGN OVERVIEW =
42 42  
43 -== 4.1 Scope and Requirements ==
43 +== 5.1 Scope and Requirements ==
44 44  
45 45  To understand the relationships between the several document types, it is important to have some familiarity with the requirements they are designed to fulfil.
46 46  
... ... @@ -67,7 +67,7 @@
67 67  
68 68  This is a very broad set of requirements, and in examining these it becomes evident that some of the requirements are very much at cross-purposes. It is almost impossible to design a single XML document type for any single function (exchange of data, exchange of [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]], querying, etc.) which will satisfy all of these requirements. At the same time, it was very much felt that whatever design was adopted should have a clear relationship with the information model.
69 69  
70 -== 4.2 Design Approach ==
70 +== 5.2 Design Approach ==
71 71  
72 72  The basic design for the XML Schema started with the information model. Just as the model does, the [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] objects are built up from the abstract classes on which they are based. This approach means that more advanced XML tools that understand such inheritance can use thes constructs to more easily deserialize the XML instances into object based on the models.
73 73  
... ... @@ -79,7 +79,7 @@
79 79  
80 80  Another new approach that has been introduced in this (% style="color:#e74c3c" %)version(%%) is to remove some of the generalities from the messages that existed to allow for web services to be more specific as to the contract of their functions. As opposed to have a single query message that can accomodate any [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] query and data and [[reference metadata>>doc:sdmx:Glossary.Reference metadata.WebHome]] queries serving as the input into a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query function­­–a specific message is created that only allows for what a [[codelist>>doc:sdmx:Glossary.Code list.WebHome]] query should reasonably be expected to handle.
81 81  
82 -== 4.3 SDMX-ML Packaging: Namespace Modules ==
82 +== 5.3 SDMX-ML Packaging: Namespace Modules ==
83 83  
84 84  In the proposed XML Schema design, there is a packaging scheme based on the idea that XML namespaces can be used as “modules”, so that any given user or application need only be familiar with a subset of the entire library in order to use it. This approach fit very well with the design described above, and is often used in major XML standards for other domains.
85 85  
... ... @@ -102,7 +102,7 @@
102 102  
103 103  The following sections describe in detail the proposed XML formats, which should be examined alongside the documentation provided. These proposed schemas are divided into the generic schemas, for which a complete set of schema definitions can be provided, and data structure-specific schemas, for which a core structure is provided (with schema code), plus a guide to how a specific data structure or [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] can be (% style="color:#e74c3c" %)mapped(%%) onto the core structure.
104 104  
105 -= 5. RELTATED DOCUMENTS =
105 += 6. RELTATED DOCUMENTS =
106 106  
107 107  To all for more managable doucments, the remainder of this document has been divided into seven different parts, each a separate document. These parts are as follows:
108 108  
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,1 +1,0 @@
1 -1
SUZ.Methodology.Code.MethodologyClass[0]