Author: Marco Molinaro
Date last changed: 2019-04-12
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.SODAThis 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.
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.ref.uri;meta.dataset
amending so the typo, the reference to a dataset rather than an organization and using a UCD referring to an identifier rather than a resource locator. Using meta.id won't work together with meta.ref.uri being both P UCD words.
Being the UCD only used in SODA to describe uniquely the ID parameter using the 3-factor semantics, this change won't probably have any impact on the service provider's side (requiring only a change in the service description). On the client side it has o be evaluated whether applications need changes. However it has to be noticed that there are few SODA service currently in place (and none registered).