Discussion #2831
Best Practices for registers and registries & Technical Guidelines for the INSPIRE register federation
| Status: | Feedback | ||
|---|---|---|---|
| Priority: | High | ||
| Assignee: | - |
Description
Dear MIWP-6 members,
Te release candidate 1 of the Best Practices for registers and registries & Technical Guidelines for the INSPIRE register federation is now available attached to this issue.
We ask you to read and provide your feedback using this issue until the 12th of September.
Thank you in advance,
The JRC Registry team
History
#1
Updated by Daniele Francioli over 4 years ago
- Description updated (diff)
#2
Updated by Daniele Francioli over 4 years ago
- Priority changed from Normal to High
#3
Updated by Michael Lutz over 4 years ago
- Status changed from New to Feedback
Dear MIWP-6 members,
The release candidate 1 of the Best Practices for registers and registries & Technical Guidelines for the INSPIRE register federation is now available attached to this issue.
We ask you to read and provide your feedback using this issue until the 12th of September.
Thank you in advance,
The JRC Registry team
#4
Updated by Michael Lutz over 4 years ago
After a discussion in the JRC registry team, we concluded that there may be an additional case of reusing register items, where items are re-used 1:1. This is e.g. the case of "externally governed" code lists in INSPIRE, where INSPIRE simply adopts the values already specificed and managed by some other organisation (e.g. EIONET/EEA). We therefore propose to update the introduction to section 4.3 as follows:
Items from one register can be reused in another register in order to support specific thematic, application or national requirements. We use the term profile[1] here for a register that contains additional items, a subset of items or a combination of both or a register that reuses all items from the original register 1:1 (Figure 2).
Figure 2 – Different types of register profiles. The original register is shown in light blue, the register profile in dark blue.
[1] According to [ISO 19106], a profile is a set of one or more base standards or subsets of base standards (…) that are necessary for accomplishing a particular function”, but can also “include extensions within the context permitted in the base standard”.
#5
Updated by Michael Lutz about 4 years ago
- File INSPIRE_Register_Federation_TG_rc1_AT.docx added
- File INSPIRE_Register_Federation_TG_rc1_Comments_ES.docx added
Comments from Austria (Chris) and Spain (Alejandra & Jesus) attached.
#6
Updated by Michael Lutz about 4 years ago
- File INSPIRE_Register_Federation_TG_rc1_avd.docx added
From Andreas von Doemming:
Please find attached my last minute comments (in the document attached) and one general point:
Can a MS add register to the RoR that does not depend on any other register in the RoR ?
Best regards
Andreas
#7
Updated by Michael Lutz about 4 years ago
@Andreas: Of course you can also add registers to the federation that have no relationships to other registers. One of the features of the RoR is to simply search for available registers. In fact, most of the central INSPIRE registers are of that type.
#8
Updated by Daniele Francioli about 4 years ago
Dear MIWP-6 members,
The release candidate 2 of the Best Practices for registers and registries & Technical Guidelines for the INSPIRE register federation is now available attached to this issue.
This version has been updated following the received comments.
The comment resolution document is also attached.
Kind regards,
The Re3gistry Team
#9
Updated by Daniele Francioli about 4 years ago
- File INSPIRE_Register_Federation_TG_rc2.docx added
#10
Updated by Daniele Francioli about 4 years ago
- File INSPIRE_Register_Federation_TG_rc3.docx added
Dear MIWP-6 members,
The release candidate 3 of the Best Practices for registers and registries & Technical Guidelines for the INSPIRE register federation is now available attached to this issue.
This version has been updated following the comments received during the 16th MIWP-6 sub-group meeting (virtual), 2016-09-21.
Kind regards,
The Re3gistry Team
#11
Updated by Michael Lutz about 4 years ago
- File deleted (
INSPIRE_Register_Federation_TG_rc3.docx)
#12
Updated by Michael Lutz about 4 years ago
- File INSPIRE_Register_Federation_TG_rc3.docx added
Minor update to the document attached.
