Changes for page Part II.Common Namespace

Summary

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

Details

Page properties

Content

...	...	@@ -619,19 +619,21 @@
619	619
620	620	Attribute Documentation:
621	621
622		-|**Name**|**Type**|**Documentation**
623		-|structureID|xs:ID|The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
624		-|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
625		-|namespace|xs:anyURI|The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message.
626		-|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
627		-|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
	622	+(% style="width:1007.29px" %)
	623	+|**Name**|**Type**|(% style="width:802px" %)**Documentation**
	624	+|structureID|xs:ID|(% style="width:802px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
	625	+|schemaURL|xs:anyURI|(% style="width:802px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
	626	+|namespace|xs:anyURI|(% style="width:802px" %)The namespace attribute is used to provide the namespace for structure-specific formats. By communicating this information in the header, it is possible to generate the structure specific schema while processing the message.
	627	+|serviceURL|xs:anyURI|(% style="width:802px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
	628	+|structureURL|xs:anyURI|(% style="width:802px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
628	628
629	629	Element Documentation:
630	630
631		-|**Name**|**Type**|**Documentation**
632		-|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against.
633		-|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against.
634		-|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata.
	632	+(% style="width:1014.29px" %)
	633	+|(% style="width:162px" %)**Name**|(% style="width:277px" %)**Type**|(% style="width:573px" %)**Documentation**
	634	+|(% style="width:162px" %)ProvisionAgreement|(% style="width:277px" %)ProvisionAgreementReferenceType|(% style="width:573px" %)ProvisionAgreement references a provision agreement which the metadata is reported against.
	635	+|(% style="width:162px" %)StructureUsage|(% style="width:277px" %)MetadataflowReferenceType|(% style="width:573px" %)StructureUsage references a metadataflow which the metadata is reported against.
	636	+|(% style="width:162px" %)Structure|(% style="width:277px" %)MetadataStructureReferenceType|(% style="width:573px" %)Structure references the metadata structure definition which defines the structure of the metadata.
635	635
636	636	**GenericMetadataStructureType:** GenericMetadataStructureType defines the structural information for a generic metadata message.
637	637
...	...	@@ -649,18 +649,20 @@
649	649
650	650	Attribute Documentation:
651	651
652		-|**Name**|**Type**|**Documentation**
653		-|structureID|xs:ID|The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
654		-|schemaURL|xs:anyURI|The schemaURL attribute provides a location from which the structure specific schema can be located.
655		-|serviceURL|xs:anyURI|The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
656		-|structureURL|xs:anyURI|The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
	654	+(% style="width:997.294px" %)
	655	+|**Name**|**Type**|(% style="width:792px" %)**Documentation**
	656	+|structureID|xs:ID|(% style="width:792px" %)The structureID attribute uniquely identifies the structure for the purpose of referencing it from the payload. This is only used in structure specific formats. Although it is required, it is only useful when more than one data set is present in the message.
	657	+|schemaURL|xs:anyURI|(% style="width:792px" %)The schemaURL attribute provides a location from which the structure specific schema can be located.
	658	+|serviceURL|xs:anyURI|(% style="width:792px" %)The serviceURL attribute indicates the URL of an SDMX SOAP web service from which the details of the object can be retrieved. Note that this can be a registry or and SDMX structural metadata repository, as they both implement that same web service interface.
	659	+|structureURL|xs:anyURI|(% style="width:792px" %)The structureURL attribute indicates the URL of a SDMX-ML structure message (in the same version as the source document) in which the externally referenced object is contained. Note that this may be a URL of an SDMX RESTful web service which will return the referenced object.
657	657
658	658	Element Documentation:
659	659
660		-|**Name**|**Type**|**Documentation**
661		-|ProvisionAgreement|ProvisionAgreementReferenceType|ProvisionAgreement references a provision agreement which the metadata is reported against.
662		-|StructureUsage|MetadataflowReferenceType|StructureUsage references a metadataflow which the metadata is reported against.
663		-|Structure|MetadataStructureReferenceType|Structure references the metadata structure definition which defines the structure of the metadata.
	663	+(% style="width:1001.29px" %)
	664	+|(% style="width:181px" %)**Name**|(% style="width:280px" %)**Type**|(% style="width:537px" %)**Documentation**
	665	+|(% style="width:181px" %)ProvisionAgreement|(% style="width:280px" %)ProvisionAgreementReferenceType|(% style="width:537px" %)ProvisionAgreement references a provision agreement which the metadata is reported against.
	666	+|(% style="width:181px" %)StructureUsage|(% style="width:280px" %)MetadataflowReferenceType|(% style="width:537px" %)StructureUsage references a metadataflow which the metadata is reported against.
	667	+|(% style="width:181px" %)Structure|(% style="width:280px" %)MetadataStructureReferenceType|(% style="width:537px" %)Structure references the metadata structure definition which defines the structure of the metadata.
664	664
665	665	=== 2.1.4 Simple Types ===
666	666
...	...	@@ -885,8 +885,9 @@
885	885
886	886	Enumerations:
887	887
888		-|**Value**|**Documentation**
889		-|unbounded|Object has no upper limit on occurrences.
	892	+(% style="width:625.294px" %)
	893	+|(% style="width:144px" %)**Value**|(% style="width:478px" %)**Documentation**
	894	+|(% style="width:144px" %)unbounded|(% style="width:478px" %)Object has no upper limit on occurrences.
890	890
891	891	**ActionType:** ActionType provides a list of actions, describing the intention of the data transmission from the sender's side. Each action provided at the data or metadata set level applies to the entire data set for which it is given. Note that the actions indicated in the Message Header are optional, and used to summarize specific actions indicated with this data type for all registry interactions. The "Informational" value is used when the message contains information in response to a query, rather than being used to invoke a maintenance activity.
892	892
...	...	@@ -894,11 +894,12 @@
894	894
895	895	Enumerations:
896	896
897		-|**Value**|**Documentation**
898		-|Append|Append - this is an incremental update for an existing data/metadata set or the provision of new data or documentation (attribute values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in version 1.0 of the SDMX Technical Standards.
899		-|Replace|Replace - data/metadata is to be replaced, and may also include additional data/metadata to be appended. The replacement occurs at the level of the observation - that is, it is not possible to replace an entire series.
900		-|Delete|Delete - data/metadata is to be deleted. Deletion occurs at the lowest level object. For instance, if a delete data message contains a series with no observations, then the entire series will be deleted. If the series contains observations, then only those observations specified will be deleted. The same basic concept applies for attributes. If a series or observation in a delete message contains attributes, then only those attributes will be deleted.
901		-|Information|Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system.
	902	+(% style="width:1005.29px" %)
	903	+|**Value**|(% style="width:905px" %)**Documentation**
	904	+|Append|(% style="width:905px" %)Append - this is an incremental update for an existing data/metadata set or the provision of new data or documentation (attribute values) formerly absent. If any of the supplied data or metadata is already present, it will not replace that data or metadata. This corresponds to the "Update" value found in version 1.0 of the SDMX Technical Standards.
	905	+|Replace|(% style="width:905px" %)Replace - data/metadata is to be replaced, and may also include additional data/metadata to be appended. The replacement occurs at the level of the observation - that is, it is not possible to replace an entire series.
	906	+|Delete|(% style="width:905px" %)Delete - data/metadata is to be deleted. Deletion occurs at the lowest level object. For instance, if a delete data message contains a series with no observations, then the entire series will be deleted. If the series contains observations, then only those observations specified will be deleted. The same basic concept applies for attributes. If a series or observation in a delete message contains attributes, then only those attributes will be deleted.
	907	+|Information|(% style="width:905px" %)Informational - data/metadata is being exchanged for informational purposes only, and not meant to update a system.
902	902
903	903	**WildCardValueType:** WildCardValueType is a single value code list, used to include the '%' character - indicating that an entire field is wild carded.
904	904
...	...	@@ -906,8 +906,9 @@
906	906
907	907	Enumerations:
908	908
909		-|**Value**|**Documentation**
910		-|%|Indicates a wild card value.
	915	+(% style="width:505.294px" %)
	916	+|(% style="width:169px" %)**Value**|(% style="width:333px" %)**Documentation**
	917	+|(% style="width:169px" %)%|(% style="width:333px" %)Indicates a wild card value.
911	911
912	912	**CascadeSelectionType:**
913	913
...	...	@@ -920,8 +920,9 @@
920	920
921	921	Enumerations:
922	922
923		-|**Value**|**Documentation**
924		-|excluderoot|
	930	+(% style="width:504.294px" %)
	931	+|(% style="width:165px" %)**Value**|(% style="width:336px" %)**Documentation**
	932	+|(% style="width:165px" %)excluderoot|(% style="width:336px" %)
925	925
926	926	**ObservationDimensionType:** ObservationDimensionType allows for the dimension at the observation level to be specified by either providing the dimension identifier or using the explicit value "AllDimensions".
927	927