Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify/remove variances in URN class name lists #24

Closed
dosse opened this issue May 11, 2021 · 2 comments
Closed

Clarify/remove variances in URN class name lists #24

dosse opened this issue May 11, 2021 · 2 comments
Labels
bug Something isn't working SDMX-ML SDMX-ML format specification SECTION 5 Section 5 - Registry Specification

Comments

@dosse
Copy link

dosse commented May 11, 2021

The list of URN class names is different between the "SDMX STANDARDS: SECTION 5 SDMX REGISTRY SPECIFICATION" (pages 31-33) and the class names listed in the "ObjectTypeCodelistType" type (in schemas/SDMXCommonReferences.xsd) used for the classes in the "WildcardObjectRefType" type.

The document doesn't have:

  • Any
  • Constraint
  • DefinitionScheme
  • ItemSchemeMap (are abstract classes allowed here?)
  • MeasureDimension (this should have been removed)
  • MetadataSet
  • MetadataTarget (this should have been removed)
  • Organisation
  • OrganisationScheme
  • ReportingYearStartDay
  • VtlMapping

The document wrongly has:

  • IdentifiableObjectTarget --> shouldn't this be removed?
  • ItemMap --> shouldn't this be removed?

Vice-versa, the "WildcardObjectRefType" type doesn't have:

  • DataAttribute
  • Subscription
  • CodelistMap
  • VtlCodelistMapping
  • VtlConceptMapping
  • VtlDataflowMapping

The type wrongly has:

  • Attribute --> should be DataAttribute
  • ItemSchemeMap (if abstract classes aren't allowed here)

Both wrongly have:

  • ReportStructure --> shouldn't this be replaced by MetadataAttributeDescriptor?

Both seem missing:

  • ReportingYearStartDay

Could it please be clarified what the correct class names are?

Also many other types in schemas/SDMXCommonReferences.xsd, many type wrongly use "Attribute" instead of "Data Atrribute".

@sdmx3mdt sdmx3mdt added bug Something isn't working SDMX-ML SDMX-ML format specification SECTION 5 Section 5 - Registry Specification labels Jun 15, 2021
@sdmx3mdt
Copy link
Owner

16 June 2021 TWG / SWG public consultation public review meeting
Action: Stratos Nikoloutsos and J Gager to agree on a definitive list of URN class names and to update both Section 5 and the XML Schemas.

@sdmx3mdt
Copy link
Owner

URN specifications clarified in Section 5 and schemas updated to comply with that specification.

The 02 September 2021 TWG decision to change the version element of the URN to () for versionless artefacts (e.g. Agency schemes) was reversed by mutual agreement through email exchange after technical problems were discovered - specifically conflict of the '' character with other meanings in the REST API. For SDMX 3.0, the version element of the URN for such artefacts remains fixed at (1.0) which is consistent with the approach used for SDMX 2.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working SDMX-ML SDMX-ML format specification SECTION 5 Section 5 - Registry Specification
Projects
None yet
Development

No branches or pull requests

2 participants