Task #2219

MIWP-8 (J) Metadata for SDS

Added by Michael Östling almost 6 years ago. Updated over 5 years ago.

Status:SubmittedStart date:17 Sep 2014
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Proposed change or action:

Description

*WIKI:* https://ies-svn.jrc.ec.europa.eu/projects/metadata/wiki/MIWP-8_(J)_Metadata_for_SDS Update TG Metadata with the extended elements defined for Spatial Data Services The extended elements for SDS are now defined and it is suggested that an implementation of these is defined in the TG using an extension to EN ISO 19115:2005 /ISO 19119:2005


Related issues

Copied to MIWP-8: Metadata - Task #2303: MIWP-8 (J) Metadata for SDS Category TG SDS 4.5.1 Submitted 17 Sep 2014
Copied to MIWP-8: Metadata - Task #2304: MIWP-8 (J) Metadata for SDS Category Submitted 17 Sep 2014

History

#1 Updated by Michael Östling over 5 years ago

  • Description updated (diff)

#2 Updated by James Reid over 5 years ago

  • Description updated (diff)

Have issuses 2 & 3 be addressed?

#3 Updated by Ine de Visser over 5 years ago

Michael Lutz is tomorrow back in office, so i hope to get some answers soon

#4 Updated by Geraldine Nolf over 5 years ago

I was out for months (maternity leave), so this comment is not on time. But I really think it is a shame that it is forced to declair how good the service is in metadata, by extended elements (!), instead of just testing that by INSPIRE via a good monitoring tool, and get the real numbers on those quality elements of each service. 

In that way the impact on member states would have been minor, instead of huge. 

#5 Updated by Ine de Visser over 5 years ago

@ Geraldine,

What do you think is the best solution possible with the fact that the commision regulation on SDS is accepted?

#6 Updated by Peter Kochmann over 5 years ago

I just got aware that there is no ticket for the issue of "Restrictions related to the access and use" in SDS so I have to post it here on the "global" level:

The examples for that issue given in TG SDS (chapter 4.6.4) show something interesting: in contrast to the existing TG metadata the restrictions on SDS are put in ISO-element otherConstraints (that's the place where they are designated to be following ISO) and not in ISO-element useLimitation (where TG metadata put them).

So maybe this is the (neccessary) attempt to have a correction of this?

In MIWP-8 (A) the discussion went on how to address useLimitation. I missed the discussion on how to find a way for the future to use useConstraints/accessConstraints togehter with otherConstraints instead! I will post this statement there as well.

#7 Updated by Peter Kochmann over 5 years ago

Maybe I've drawn the wrong conclusions with this issue. So I'm afraid I have to recall my statement #6.

I read the example in TG SDS 4.6.4 like that for SDS there's the opportunity to have "conditions applying to access and use" in ISO element accessConstraints/otherConstraints (where it is designated by ISO to be) and not to be bound to have it in useLimitation (like TG Metadata says by now).

Reality is that "Restrictions related to the access and use" with SDS are required to be documented in "CONSTRAINT RELATED TO ACCESS AND USE set out in IR Metadata". And behind that we still have "Conditions applying to access and use" (TG Metadata 2.9.2) and "Limitations on public access" (TG Metadata 2.9.1).

Sorry for causing confusion! I had the hope that we could find a way to have an end of the misinterpretation of useLimitation and the Mapping in TG Metadata 2.9.2 (what I consider to be wrong).

Also available in: Atom PDF