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

Upgrade from ISO 19103:2015 to ISO 19103:2024 #102

Open
desruisseaux opened this issue Nov 15, 2024 · 4 comments
Open

Upgrade from ISO 19103:2015 to ISO 19103:2024 #102

desruisseaux opened this issue Nov 15, 2024 · 4 comments
Milestone

Comments

@desruisseaux
Copy link
Contributor

desruisseaux commented Nov 15, 2024

ISO published a new revision of ISO 19103. This task is the continuation of #17. Some significant changes are:

  • CodeList replaced by CodeSet.
  • GenericName and sub-types removed.

The following changes have no direct incidence on GeoAPI, but impact ISO 19111:

  • Union stereotype removed.
  • Set and Sequence data types removed.
@desruisseaux desruisseaux added this to the 3.1 milestone Nov 15, 2024
@paulushub
Copy link

paulushub commented Dec 11, 2024

CodeList replaced by CodeSet.

Any other changes beside the name?

GenericName and sub-types removed.

What are the replacements for the GenericName and its subtypes?

@desruisseaux
Copy link
Contributor Author

The replacement of CodeList by CodeSet seems more fundamental than only a name change. ISO 19103:2024 has a full annex about that (annex H). It refers to three other standards: ISO/IEC TR 2382, 9789 and 15944-10. They apparently try to put some order in the way to expand a code set with values defined outside the standard, e.g. by defining what should be the coding scheme. CodeSet seems to be a more general concept than CodeList as used in GeoAPI, where the latter is a special case of code set using mnemonic coding scheme. They also discuss how code sets should be published. My understanding is that they suggest using something like the above, instead of putting the code values in the standard:

In short, the big difference seems to be that pre-defined code values would no longer be enumerated in the CodeList class, but instead would be fetched dynamically from a file in one of above formats. Note: it does not mean that GeoAPI should remove CodeList values. It is common in programming languages to have pre-defined constants for commonly used values, so we could decide to change nothing.

About GenericName, ISO 10193:2024 said "Search for the extension data types in the package with identifier https://standards.isotc211.org/harmonized-model/common-types, see §7.11.3" and §7.11.3 said "(…snip…) managed in the Harmonized Model and is overseen by the HMMG under the ISO/TC 211 Harmonized Resources Maintenance Agency". I do not yet know what it means, neither where to find those resources. I presume that we will discuss this issue in the ISO 19111 working group for the ongoing revision of that standard, since it uses GenericName.

@paulushub
Copy link

Code List Representation (genericode) (an OASIS standard)

A very useful resource - thank you. The specification of the code-list is very extensive, I will study it.

but instead would be fetched dynamically from a file in one of above formats.

I think it will make a lot of sense for custom enumeration - was wondering how the custom enumerations will be introduced into the system.
GeoAPI may just check if a loaded enumeration matches a pre-defined, and skip or create accordingly.

I presume that we will discuss this issue in the ISO 19111 working group for the ongoing revision of that standard, since it uses GenericName.

Thank you, until something comes out, we can just continue with the current uses.

desruisseaux added a commit that referenced this issue Dec 11, 2024
This is incomplete, the following tasks still need to be done:

* Review the UML schemas
* Verify the Metanorma rendered pages, including reference in bibliography
* Review section on `Record` (removed from ISO 19103 but still used in GeoAPI).
* Review section on `GenericName` (removed from ISO 19103 but still used in GeoAPI).
* Review section on `InternationalString` for replacing the standard source by `PT_FreeText`.

#102
@desruisseaux
Copy link
Contributor Author

Updated the specification. But the following tasks still need to be done:

  • Review the UML schemas.
  • Verify the Metanorma rendered pages, including reference in bibliography.
  • Review section on Record (removed from ISO 19103 but still used in GeoAPI).
  • Review section on GenericName (removed from ISO 19103 but still used in GeoAPI).
  • Review section on InternationalString for replacing the standard source by PT_FreeText.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants