Task #2305

MIWP-8 (J) Metadata for SDS Resource locator

Added by Ine de Visser over 5 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

Resource locator (TG SDS 4.5.2)

The Resource Locator metadata element set out in Regulation (EU) No 1205/2008 shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such using the resource locator function code element as defined in Implementation Requirement 3.

The access point of the service contained in the Resource Locator metadata element, shall be unambiguously identified as such using the CI_OnlineFunctionCode (table 3) as specified in Annex B.

Actions:

  1. Check defenitions of resouce locator in IR MD, TG MD and TG SDS, .. are they in line with each other?
  2. Update TG MD 2.2.4  Resource locator (use TG SDS table 2)
  3. Update TG MD with the element Function code   (use TG SDS table 3)
  4. give examples, explain condition, ...
  5. provide a codelist for the CI_OnlineFunctionCode

 


Related issues

Copied from MIWP-8: Metadata - Task #2304: MIWP-8 (J) Metadata for SDS Category Submitted 17 Sep 2014
Copied to MIWP-8: Metadata - Task #2306: MIWP-8 (J) Metadata for SDS Specification Submitted 17 Sep 2014

History

#1 Updated by Ine de Visser over 5 years ago

For this metadata element the following is written down in;

COMMISSION REGULATION (EU) No 1312/2014 of 10 December 2014 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data services

The Resource Locator metadata element set out in Regulation (EC) No 1205/2008 shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such.

...

‘31. "end point" means the internet address used to directly call an operation provided by a spatial data service,

32. "access point" means an internet address containing a detailed description of a spatial data service, including a list of end points to allow its execution,

 

COMMISSION REGULATION (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards

metadata

The resource locator defines the link(s) to the resource and/or the link to additional information about the resource.

The value domain of this metadata element is a character string, commonly expressed as uniform resource locator

(URL).

 

TG SDS;

Implementation Requirement 2 The Resource Locator metadata element set out in Regulation (EU) No 1205/2008 shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such using the resource locator function code element as defined in Implementation Requirement 3.

Implementation Requirement 3 The access point of the service contained in the Resource Locator metadata element, shall be unambiguously identified as such using the CI_OnlineFunctionCode (table 3) as specified in Annex B.

The values contained in the standard [ISO 19115, Section B.5.3] codelist cannot be used to unambiguously identify the access point provided in the resource locator. That’s why a new codelist with a set of proper code to unambiguously identify the access point is needed.

CI_OnlineFunctionCode <<CodeList>>

Name

Description

accessPoint

Used to describe an access point of the service

accessPoint-selfDescribing

Used to describe an access point of the service that describe itself in a machine readable format (e.g. WSDL)

providesServiceMetadata

Used to specify an address to a document that describe the service metadata (such as GetCapabilities or a WSDL containing a reference to the getCapabilities operation)

 

TG MD;

TG Requirement 3 If a linkage for data is available, the Resource Locator shall be a valid

URL providing one of the following:

- a link to a web with further instructions

- a link to a service capabilities document

- a link to the service WSDL document (SOAP Binding)

- a link to a client application that directly accesses the service

 

A Resource Locator could be described, moreover, by other additional elements as a Title, a Description and a Function. In that case, the Title and the Description shall be free text and the Function shall be filled by the CI_OnLineFunctionCode (ISO 19115 codelist).

Example of Resource Locator with these additional elements:

• Linkage:

http://edo.jrc.ec.europa.eu/chm/ows.php?VERSION=1.3.0&SE

RVICE=WMS&REQUEST=GetCapabilities

• Title: JRC EDO (European Drought Observatory) - Drought

Indexes WMS

• Description: WMS delivering maps of drought indexes

provided by the European Drought Observatory (EDO).

• Function: information

 

Proposed change in TG MD;

TG Requirement 3 If a linkage for data is available, the Resource Locator shall be a valid

URL providing one of the following:

link(s) to the resource access and/or endpoint and/or the link to additional information about the resource

- a link to a web with further instructions

- a link to a service capabilities document

- a link to the service WSDL document (SOAP Binding)

- a link to a client application that directly accesses the service

 

TG Requirement  X  For spatial dataset services a link to at least one access point is required.

 

The values contained in the standard [ISO 19115, Section B.5.3] codelist cannot be used to unambiguously identify the access point provided in the resource locator. That’s why a new codelist with a set of proper code to unambiguously identify the function of the link provided..

 

CI_OnlineFunctionCode <<CodeList>>

Name

Description

accessPoint

Used to describe an access point of the service

accessPoint-selfDescribing

Used to describe an access point of the service that describe itself in a machine readable format (e.g. WSDL)

providesServiceMetadata

Used to specify an address to a document that describe the service metadata (such as GetCapabilities or a WSDL containing a reference to the getCapabilities operation)

endPoint Used to directly call an operation provided by a spatial data service
information

Used to call online information about the resource

 

 

 

#2 Updated by Age Sild over 5 years ago

A note about a proposal: TG Requirement  X  For spatial dataset services a link to at least one access point is required.

COMMISSION REGULATION (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata says:

Multiplicity of Resource locator for services is 0..*

In TG MD there is now TG Recommendation 7 (about dataset) and TG Recommensdation 8 (about services), that are saying - If no direct link to a resource is available, provide link to a contact point where more information about the resource is available.

As I understand at least one access point is definitely required if service is an invocable SDS or an interoperable SDS or a harmonised SDS, otherwise if no direct link to a service is available, there is still possible to provide link to a contact point where more information about the resource is available...?

My proposal is: TG Requirement  X  If spatial dataset service is an invocable SDS or an interoperable SDS or a harmonised SDS a link to at least one access point is required.

#3 Updated by Ine de Visser over 5 years ago

I agree

#4 Updated by Michael Östling over 5 years ago

If a service is protected and you need a written Agreement to access the service then maybe the Access point
will not be available in metadata even for invocable SDS-services.   So I'm not sure we can have a requerement to have an access-point.
But for me the definition of an access-point is not fully clear. I understand it can point to a wsdl but could an access-point also point to
website with instructions for on-line order of access to service? Is an access point always a machine-readable URL?

 

#5 Updated by Marc Leobet over 5 years ago

From the discussions in INSPIRE Committee, I can say Yes. We have to give at least one endpoint. It may be protected behind a password, but that is another question. We could talk longer during the web-meeting.

Best regards

#6 Updated by Ine de Visser over 5 years ago

this is a ment to give function codes for both, the exsisting resource locators as in the TG MD and the resource locators as in TG SDS. But your signal is clear better descriptions are needed.

about the protected access points, in the definitions about invocable services is said it must have at least an access point.

 

#7 Updated by Ine de Visser over 5 years ago

To come back to the discussion in in the telecon about definitions of endpoint and access point, they are given in te regulation, see at the top of this ticket, but not clear.

If those definitions are not clear the codes and descriptions for functions in the codelist to identify those  access points are also subject off discussion.

I tried to clarify the definitions, but both in ISO and OGC terms are no endpoint or access point definitions.

An access point, conform the definition of accessppoint as given in the regulation, can be a any document or description published somewhere on the web, containing endpoints...

 

W3C has perhaps definitions we can use;

end point;

From Web Services Glossary (2004-02-11)

service description;

An association between a binding and a network address, specified by a URI, that may be used to communicate with an instance of a service. An end point indicates a specific location for accessing a service using a specific protocol and data format. [WSD Reqs]

From Web Services Glossary (2004-02-11)

A service description is a set of documents that describe the interface to and semantics of a service.

service;

From ISO 19119:2005

distinct part of the functionality that is provided by an entity through interfaces

interface;

From ISO 19119:2005

named set of operations that characterize the behaviour of an entity

 

proposed definition access point :

If we use the INSPIRE defnition of accesspoint in combination with the definition of service description and service interface, we get;

"access point" means an internet address containing a set of documents that describe the named set of operations that characterize the behaviour of an entity and semantics of a spatial data service, including a list of end points to allow its execution.

Is this an acceptable definition?

 

#8 Updated by Peter Kochmann over 5 years ago

I did not follow the discussion about the meaning of accessPoint completely, I want to give a comment on the proposed table for CI_OnlineFunctionCode instead:

Why does it include "information" again? This is already contained in the ISO-CodeList.

 

#9 Updated by Ine de Visser over 5 years ago

In the current TG MD a resource locator coulb be "- a link to a web with further instructions" It's not mandatory to use a function code in the metadata on datasets and services, but it's mandatory for SDS. So i think it should be better to add also funcioncodes that supports the existing resource locator metadata.

The codelist is a replacement of the orginal ISO codelist.

Also available in: Atom PDF