International Virtual Observatory Alliance

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

Revision 22019-04-16 - MarcoMolinaro

  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
- META TOPICPARENT
+  name="SODA-1_0-Errata"
-<
<
+Date last changed: 2019-04-12
->
>
+Date last changed: 2019-04-16
 <-- Date accepted|rejected: 20NN-MM-DD -->

 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.ref.uri;meta.dataset
->
>
+meta.id;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.
->
>
+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 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
->
>
+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 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).

<-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Revision 12019-04-12 - MarcoMolinaro

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-12

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

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

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.

Impact Assessment

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).

<-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

View topic | History: r8 < r7 < r6 < r5 | More topic actions...