This section has now been locked for editing and a draft version have been moved into the draft document.
See page: https://ies-svn.jrc.ec.europa.eu/projects/metadata/wiki/DraftVersionsMIWP-8
Further discussions and comments should be done on the draft
Right now there are number of optional metadata elements spread out over a number of INSPIRE Data Specifications.
The metadata TG will be updated to include those “optional” metadata elements within and updated TG because some data providers are producing theme specific data services already.
This will allow those organizations that wish to use the optional elements to have appropriate 19115 elements in the metadata for this purpose.
Ine de Visser
Pierluigi Cara (Leader)
What problems causes current solution ?¶
Most of the mentioned metadata elements do not have a precise mapping to ISO 19115-elements. In some cases a mapping can be derived from the given examples. A problem in future could be a different view on these theme specific elements and thereby a different mapping.
What can be a solution on current problem ?¶
We need to find an exact mapping of the given metadata "information" to existing ISO 19115-elements especially in case that the given examples do not apply precise metadata elements. One possible way could be to make use of existing draft mapping tables and to transform these information into Technical Guidance "style".
Comment from Peter Kochmann (DE): Last year I built up a German draft mapping table assuming precise ISO 19115-elements (see attached file). Some of them do not match an element by now but a whole structure.
Comment from Manfred Mittlboeck (AT) [15-02-05]: We are working on a mapping table referencing the Austrian metadata profile (profil.AT) with the INSPIRE requirements also referring ISO 19115 and ISO 1915. The referencing is based on INSPIRE documents by November 2014 on the INSPIRE website also including the metadata cardinalities. Right now we compare this list with Peter Kochmanns list published here and are working on the consolidation.
How does it relate to IR ?¶
To be verified: IR metadata contains tables of metadata elements for data and services giving a multiplicity as well. Only mandatory and optional elements are mentioned. In case of data regarding IR interoperability the additional metadata elements could be considered in IR metadata too though they are flagged as optional.
How will the solution affect existing tools ?¶
How will the solution affect existing metadata ?¶
What other issues in MIWG-8 is related to this change ?¶
What other groups within MIG-related workgroups could be linked to this issue ?¶