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.

Sign up for GitHub

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

Jump to bottom

Multiple character encodings for Catalogue Record #103

Open
jakubklimek opened this issue Mar 6, 2024 · 1 comment
Open

Multiple character encodings for Catalogue Record #103

jakubklimek opened this issue Mar 6, 2024 · 1 comment
Labels
release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft type:bug This is broken and to be fixed webinar:2024-04-23 To be discussed in the 2024-04-23 webinar

Comments

@jakubklimek
Copy link
Contributor

jakubklimek commented Mar 6, 2024 •
edited
Loading

Problem statement
GeoDCAT-AP 2.0.0 defines multiplicity 0..n for character encoding on Catalogue Record.

Given that:

  1. It is unclear what exactly this should mean.
  2. The INSPIRE Metadata Technical Guidelines talk only about character encodings of dataset and series, not metadata itself.
  3. In the XSLT transformation of ISO 19139 to GeoDCAT-AP, it looks like only one value of this property is expected on the metadata level.
  4. In the OGC XML Schema for MD_Metadata, this character set code is represented as 0..1

this seems like a bug.

Proposal
Restrict the multiplicity to 0..1
@jakubklimek jakubklimek added type:bug This is broken and to be fixed release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 webinar:2024-04-23 To be discussed in the 2024-04-23 webinar status:resolution-proposed Resolution proposed and will be accepted before the next webinar labels Mar 6, 2024
@jakubklimek jakubklimek added the next-webinar To be discussed in the next webinar label Mar 21, 2024
@jakubklimek jakubklimek added status:resolution-provided Resolution statement present, not yet applied in draft and removed status:resolution-proposed Resolution proposed and will be accepted before the next webinar labels Apr 16, 2024
@jakubklimek
Copy link
Contributor Author

Based on #88 , Character encoding will be removed from CatalogueRecord completely.

@jakubklimek jakubklimek added status:fixed Resolution applied in draft and removed status:resolution-provided Resolution statement present, not yet applied in draft next-webinar To be discussed in the next webinar labels Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
release:3.0.0 Actively being worked on for GeoDCAT-AP 3.0.0 status:fixed Resolution applied in draft type:bug This is broken and to be fixed webinar:2024-04-23 To be discussed in the 2024-04-23 webinar
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jakubklimek