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
Add some new items in the Protocol Value register #17
Comments
Dear @AntoRot , Thank you for your request. The scrutiny period begins now, and it is open to comments from the Control Body during the next two weeks. Kind regards, INSPIRE Registry team. |
Thank you very much, @hernlor! Please note that this addition will also imply a revision of the definition of the register. Kind regards, |
Dear @AntoRot thank you for the patience. We have discussed internally your proposal. The addition of new values would imply a change in the definition and reasoning behind the code list as you rightly pointed out. Because of the latter, the control body prefers not to approve the change at the moment and invites you to discuss their addition in the frame of "Action 2.3 "Simplification of INSPIRE implementation"[1] of the INSPIRE MIWP 2021-2024[2]. Alternatively, you can create an extension of the code lists to support your use case and share it through the Registry of registers applications. [1] https://github.com/INSPIRE-MIF/gp-data-service-linking-simplification Kind regards on behalf of the INSPIRE Registry control body. |
Dear @hernlor, Thank you for the attention of the INSPIRE Registry control body to the change proposal. Our initial intention indeed was to publish the two items in the Italian registry (included in the INSPIRE register federation) as national extensions to the Protocol Value register, but we thought to first propose this change to the INSPIRE registry as it could be of interest for other Member States. Now we'll proceed as you suggested, by both publishing the national extensions and discussing the proposal under the new action 2.3. Anyway, I think that register should include all the possible reference codes to be used as protocol values and not be limited only to the scope defined under the simplification action. Best regards, |
Thank you @AntoRot, feel free to reopen this issue or link to this one after discussing the options under Action 2.3 "Simplification of INSPIRE implementation" of the INSPIRE MIWP 2021-2024. Kind regards, INSPIRE Registry team |
Dear @AntoRot, |
In the light of the provisions laid down by the Implementing Regulation (EU) 2023/138 (High-value datasets) and specifically the arrangement about the availability of datasets as bulk download, I think that this proposal should be reconsidered. The new proposed item WWW:DOWNLOAD indeed could be used to denote the mandatory bulk download for spatial datasets falling under the above mentioned Regulation. |
URI: http://inspire.ec.europa.eu/metadata-codelist/ProtocolValue
Motivation: We propose to add some items in the Protocol Value register because we need some missing codes to represent two types of resources, i.e.:
Proposed change: new proposed items:
WWW:LINK
Register: http://inspire.ec.europa.eu/metadata-codelist/ProtocolValue Label: Web Address (URL) URI: http://www.w3.org/TR/xlink/ External value: true
WWW:DOWNLOAD
Register: http://inspire.ec.europa.eu/metadata-codelist/ProtocolValue Label: File for download Definition: Link that will get resource URI: http://inspire.ec.europa.eu/metadata-codelist/ProtocolValue/www-download External value: false
Change type: addition
The text was updated successfully, but these errors were encountered: