Server-side Opertaion for Data Access version 1.0 Proposed Erratum 1: ID parameter UCD amendment

Author: Marco Molinaro

Date last changed: 2019-04-16

Rationale

SODA protocol uses the ID parameter to specify opaque identifiers to the dataset or file to be accessed. The UCD specified in the SODA-embedded 3-factor semantics is reported in the REC text as

meta.ref.url;meta.curation.SODA

This is not a valid UCD both for the, probably, typo of the added .SODA part and the fact that meta.curation identifies a man/organization responsible for the data as per the UCD vocabulary.

Erratum Content

This Erratum proposes to change, in §3.2.1 "*ID*" of SODA - Version 1.0 the UCD in the sentence

The UCD describing the ID parameter is meta.ref.url;meta.curation.SODA

from

meta.ref.url;meta.curation.SODA

to

meta.id;meta.dataset

thus achieving:

• typo amendment
• reference to a dataset rather than an organization
• using a UCD referring to an identifier rather than a resource locator
• keeping the identifier opaque as required by the specification

Impact Assessment

Being the UCD only used in SODA to describe uniquely the ID parameter using the 3-factor semantics, this change will have a minimal impact on the service provider's side (requiring the UCD amendment and releasing it). On the client side it has to be evaluated whether applications need changes. However it has to be noticed that there are few SODA service currently in place (and none registered).