search

sdmx3mdt / public-consultation

0 stars 0 forks source link

Replace leftovers of "Constraint" by "DataConstraint" resp. "MetadataConstraint" #30

Closed dosse closed 3 years ago

dosse commented 3 years ago

Example: see: MaintainableTypeCodelistType

Also replace "Content constraints" terms in the technical specification document.

dosse commented 3 years ago

@sdmx3mdt I have seen also left overs of "Content constraints" in the technical specifications https://metatechltd.sharepoint.com/:w:/s/SDMX30TechnicalSpecifications/EY5Oq7ex2edPr4ZV7oN8QlABcWtiGUuYr6SpJtgv7z-6ig?e=E8AqXT, e.g. "9.3.2 Multiple Content Constraints", "9.3.3 Inheritance of a Content Constraint". Thus the label for documentation should be added too.

sdmx3mdt commented 3 years ago

@dosse concerning the XML schemas, J has reviewed this comment and reports that in the case of MaintainableTypeCodelistType, it is correct to include "Constraint" because it is the full list which includes abstract types. The IM has an abstract Constraint and this is what this enumeration represents.

I can see that ConcreteMaintainableTypeCodelistType by contrast lists "DataConstraint" and "MetadataConstraint" as the concrete maintainables.

sdmx3mdt commented 3 years ago

@stratosn minor editorial corrections are required to Section 6 where it still refers to 'content constraint': "9.3.2 Multiple Content Constraints", "9.3.3 Inheritance of a Content Constraint"

sdmx3mdt commented 3 years ago

Section 6 updated to remove outdated references to 'content constraints'.

The XML Schemas have not been altered. In the case of MaintainableTypeCodelistType, it is correct to include "Constraint" because it represents the full list which includes abstract types. The IM has an abstract Constraint and this is what this enumeration represents.