ISO-TC211 / StandardsTracker

This GitHub repository lets you - our users - log and track issues that you find with our standards and other document. Tag the issue with the standard or standards effected; we will assign it to the relevant group(s) within TC 211.
12 stars 0 forks source link

ISO 19110:2016 Request to make gfc.xsd V1.0 available from https://schemas.tc211.org/ #347

Closed isotc211 closed 2 years ago

isotc211 commented 3 years ago

Justification: Previous version of ISO 19110:2016 gfc.xml should be available from https://schemas.isotc211.org/... Proposal: Copy https://www.isotc211.org/2005/gfc/gfc.xsd to https://schemas.tc211.org/19110/-/gfc/1.0/gfc.xsd

isotc211 commented 3 years ago

Task completed via GitHub TC211/schemas Proposed change implemented, leaving this confusing position!

ISO 19110:2005 (edition 1) Namespace http://www.isotc211.org/2005/gfc

Now at https://schemas.tc211.org/19110/-/gfc/1.0/gfc.xsd as well as https://www.isotc211.org/2005/gfc/gfc.xsd (difference is in the paths they use to import 19115 fragments)

Both have internal schema version still 0.1

ISO 19110:2005/Amd 1:2011 - I'm not sure!

ISO 19110:2016 (edition 2) Namespaces http://standards.iso.org/iso/19110/gfc/1.1 & https://standards.iso.org/iso/19110/fcc/1.0/

using the "old" location pattern, so at

https://schemas.isotc211.org/schemas/19110/gfc/1.1/gfc.xsd as well as https://standards.iso.org/iso/19110/gfc/1.1/gfc.xsd

With internal schema versions set to 1.1

Confusions:

Why does the edition 1 still have schema version = 0.2?

What is the pattern for amendments? In this case, did the amendment affect the XSD?

Would it be good to also have the new / current (1.1) schema also available from/where it would be with the current URI pattern i.e. include 'edition 2' so at https://schemas.isotc211.org/schemas/19110/-/gfc/2.0.0/gfc.xsd (or 2.0.1 for the path change)?

Or would that just be even more confusing? How do we plan to deal with this confusion (for all standards) across the next 5-10 years?

isotc211 commented 3 years ago

Task completed via GitHub TC211/schemas Proposed change implemented, leaving this confusing position!

ISO 19110:2005 (edition 1) Namespace http://www.isotc211.org/2005/gfc

Now at https://schemas.tc211.org/19110/-/gfc/1.0/gfc.xsd as well as https://www.isotc211.org/2005/gfc/gfc.xsd (difference is in the paths they use to import 19115 fragments)

Both have internal schema version still 0.1

ISO 19110:2005/Amd 1:2011 - I'm not sure!

ISO 19110:2016 (edition 2) Namespaces http://standards.iso.org/iso/19110/gfc/1.1 & https://standards.iso.org/iso/19110/fcc/1.0/

using the "old" location pattern, so at

https://schemas.isotc211.org/schemas/19110/gfc/1.1/gfc.xsd as well as https://standards.iso.org/iso/19110/gfc/1.1/gfc.xsd

With internal schema versions set to 1.1

Confusions:

Why does the edition 1 still have schema version = 0.2?

What is the pattern for amendments? In this case, did the amendment affect the XSD?

Would it be good to also have the new / current (1.1) schema also available from/where it would be with the current URI pattern i.e. include 'edition 2' so at https://schemas.isotc211.org/schemas/19110/-/gfc/2.0.0/gfc.xsd (or 2.0.1 for the path change)?

Or would that just be even more confusing? How do we plan to deal with this confusion (for all standards) across the next 5-10 years?