Difference: SODA-1_0-Err-1 (2 vs. 3)

Revision 32019-04-17 - JamesDempsey

 
META TOPICPARENT name="SODA-1_0-Errata"

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 

<-- Date accepted|rejected: 20NN-MM-DD -->

Rationale

Changed:
<
<		SODA protocol uses the ID parameter to specify opaque identifiers to the dataset or file to be accessed.
>
>		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
Deleted:
<
<		The UCD specified in the SODA-embedded 3-factor semantics is reported in the REC text as
 
meta.ref.url;meta.curation.SODA
Deleted:
<
<		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.
 
Added:
>
>		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

Changed:
<
<		This Erratum proposes to change, in §3.2.1 "*ID*" of SODA - Version 1.0
>
>		This Erratum proposes to change, in §3.2.1 "*ID*" of SODA - Version 1.0 the UCD in the sentence
Deleted:
<
<		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
Changed:
<
<
  • reference to a dataset rather than an organization
>
>
  • 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

Changed:
<
<		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
>
>		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).
Deleted:
<
<		on the service provider's side (requiring the UCD amendment a releasing it). 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).
  
<--  
-->
View topic | History: r8 < r7 < r6 < r5 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback