W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > January 2019

Re: [dxwg] draft DCAT 2018 to ISO19115-3 and 19139 mapping (#618)

From: Andrea Perego via GitHub <sysbot+gh@w3.org>
Date: Mon, 07 Jan 2019 22:30:18 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-452105197-1546900217-sysbot+gh@w3.org>
Thanks for the clarification, @smrgeoinfo .

Indeed, the documentation on GeoDCAT-AP mappings does not include XPath expressions. They can actually be derived from the examples in the GeoDCAT-AP specification (Annex B), where the mapping of each of the ISO elements covered by GeoDCAT-AP are explained. Besides the PDF version of the GeoDCAT-AP spec, this can be probably more easily seen in the "live" HTML version:


Said that, the problem is that in many cases the transformation cannot be carried out only with XPath expressions. An example is the value of `@xml:lang` for plain literals, which needs to be inherited by the ISO element for the metadata language. And another one is about the cases where values in ISO metadata needs to be mapped to other ones in the RDF representation (e.g., the resource language, that should be expressed with a URI from a given code list, instead of the ISO code).

About the scope of GeoDCAT-AP, this programmatically covers the union of the metadata elements in INSPIRE and the core profile of ISO 19115:2003. So, it is indeed not complete, but I would not say that the mappings are INSPIRE-specific. The only "specific" aspect concerns the code lists used for languages, etc., which (following DCAT-AP) are those maintained by the EU Publications Office and the INSPIRE Registry. These can be easily replaced in the transformation by other reference code lists - as the LoC ones.

It makes perfect sense to me to complement what not included in GeoDCAT-AP, and to look also at ISO 19115-3, but again it would make sense to build upon the mappings already defined in GeoDCAT-AP. BTW, about ISO 19115-3, the GeoDCAT-AP WG did a preliminary analysis of what was changed, which may turn to be useful. It is included in an annex to the GeoDCAT-AP spec:


GitHub Notification of comment by andrea-perego
Please view or discuss this issue at https://github.com/w3c/dxwg/pull/618#issuecomment-452105197 using your GitHub account
Received on Monday, 7 January 2019 22:30:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 April 2019 13:45:05 UTC