-
Notifications
You must be signed in to change notification settings - Fork 27
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
Use/Align with EU location vocabularies #46
Comments
W.r.t. EU controlled vocabularies: refer to https://op.europa.eu/en/web/eu-vocabularies/authority-tables (and Eurostat). For EU (and EU Member State) administrations, these are normative. If official administrative data would be required to be provided these will be imposed. |
Hi. Yes - this is a good suggestion (for authoritative EU vocab). Thank you. Do you know if these represent EU membership, and where the current UK and adequacy situations are? It would be great if we have an external resource that defines countries / regions (and keeps them updated), so that DPV can focus on linking the information (e.g. authorities, laws) and only add what is missing (e.g. adequacy decisions). |
The corporate-body encodes the EU and its agencies. The NAL Country covers the countries: exact the same content as is DPV-Legal, with EU managed persistent URIs. |
This is great! Thanks for finding and suggesting. I don't know why I didn't realise eurovoc should have already had this. We will discuss removing the duplicate terms (countries and EU membership) from dpv-legal and keeping the rest. I know that for laws, the EU publications office has identifiers for each publication that state whether they are in force, etc. but AFAIK no relation to locations or authorities. Same for adequacy decisions. So if that is still the case, then that's what dpv-legal should retain. |
Normally, I would expect those to have a namespace as the Commission and the Publication Office are deep into RDF. So we could just make an open connector to this, because NIST and BST etc will have their own taxonomies. |
@rigow Hi! Yes, they have RDF & IRIs. I did not understand what you meant by "open connector", could you please elaborate? My earlier comment was that we can remove the DPV duplicate concepts and just use the EU ones? The NIST and BST etc. will have to be mapped anyway - so instead of DPV, now they will map to EUVOC? |
We discussed this in DPVCG meeting SEP-28, and agreed to remove the duplicate concepts from DPV and use the EUVoc ones instead since they are authoritative. Minutes - https://www.w3.org/2022/09/28-dpvcg-minutes.html |
Adds a red-text warning to DPV-LEGAL HTML pages referring to #46 about reusing EU vocabs and removal of duplicates.
Adds a red-text warning to DPV-LEGAL HTML pages referring to #46 about reusing EU vocabs and removal of duplicates.
I went through the EU vocabularies (authority tables, thesauri, taxonomy) and there are a lot of IRIs for concepts that can be reused in DPV-LEGAL, including Country and Places, but there are several things missing. We can provide these as a wrapper on top of EUvocs (and other vocabularies) in the future. See below for a summary, with the full set at https://harshp.com/dev/dpv/notes-reuse-euvoc. Specific tasks we can do include providing
Ideally, all this should be contributed back to the Publications Office and including in that list, but I have no idea what additional work is needed, or how to do integrate this back into the current vocabs. |
More references I've looked at:
IMHO what we can do next: we continue using existing DPV terms, e.g. Aside, while we do the above, we should ask EU Publications Office and/or SEMIC if there is value in them providing this data given that it is commonly required in all use-cases. |
The NosLegal Taxonomy has a mature Locations Dictionary which maybe useful. It also contains memberships and treaties which might also be useful. I can introduce you to the team managing NosLegal if that will help. |
Hi. Thanks, NosLegal looks good, though two issues with NosLegal taxonomy: (1) Its not 'authoritative' in the sense that EU vocabs or SEMIC or OMG or ISO is. (2) No RDF serialisation (easily fixed, so minor issue). Separate from these, NosLegal is a limited company - so there is uncertainty how it will be maintained on an ongoing basis and in long-term. We should prefer authoritative and (known to be) well-maintained sources for the purposes of this work. |
Update from today's meeting https://www.w3.org/2022/12/14-dpvcg-minutes.html - we will add a note regarding uncertainty of vocabulary, turn the spec into a guidance for using other authoritative vocabularies (starting with EU vocabs), and provide only the additional information relevant for DPVCG's scope, i.e. laws and authorities. So the 'contribution' of DPV-Legal would be to guide how to use authoritative vocabularies, provide datasets for ease of use, tables for reference, and only add missing concepts with the intention to suggest their standardisation in appropriate initiatives. |
Comment by @coolharsh55 via IRC channel #dpvcg on irc.w3.org this was discussed in today's meeting with consensus to drop alignment with EUVOC and continue with DPV-LEGAL modelling of jurisdictions and other information, and to ask for help in aligning it with other vocabularies. The issue will remain open for discussion and continued contribution. |
Comment by @coolharsh55 via IRC channel #dpvcg on irc.w3.org the group agreed in today's meeting to continue with DPV's modelling of location |
The DPV locations are now associated with EU Voc locations - see https://w3id.org/dpv/loc#vocab where the table provides links to ISO and EU Voc pages for each country. These links are only present in the table. They should be added to RDF with |
To review and close this issue, see -
|
The concepts from DPV-LEGAL regarding locations (e.g. nations), memberships, their corresponding ISO 3166 codes are already provided with multi-language labels by the Getty Thesaurus of Geographic Names (TGN) under a Open Data Commons Attribution License. This is more comprehensive than the one in DPV-LEGAL, and contains other information regarding the locations. However, it is not up to date, as evidenced by UK still being depicted as a member of EU.
Suggestion: declare relation between DPV-LEGAL and TGN, e.g. skos:exactMatch, and provide information about TGN on the DPV-LEGAL page.
The text was updated successfully, but these errors were encountered: