International Virtual Observatory Alliance

Difference: PubDataLink (1 vs. 2)

Revision 22011-03-03 - DougTody

META TOPICPARENT	name="ObsDMCoreComponents"

+ Various uses and possibilities for obs_publisher_did

How the user will be able to make use of it.

This is not a ObsTAP issue, it is a more generic question: Within the IVOA architecture, how to use a obs_publisher_did? For publications? To find again the data? For programmatic access?

Given it is a CLOB field, nobody can actually use it to find the same data again (and access_url is volatile).

The IVOA should seriously think how to consume it.

Added:

>
>

Added:

>
>

The dataset identifier is an existing IVOA and ADS standard. It is already in use in the VO registry and in existing DAL standards such as SSA. Hence, there really should be no confusion over the purpose and use of the field. Its main purpose is to identify a specific dataset and allow for later retrieval or access. The current ObsTAP spec is incorrect in specifying that the publisher DID (or creator DID etc.) cannot be used in a WHERE clause to search for datasets; this is the whole purpose of the attribute (unfortunately this was not caught until the current draft was released so we are taking up the discussion here instead).

Added:

>
>

In addition to the IVOA documents, here is a reference to the original ADS-IVOA agreement where dataset identifiers were originally defined: http://vo.ads.harvard.edu/dv/

Added:

>
>

This should help to clarify their intended purpose and usage. -- DougTody 2 March 2011

<-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Revision 12011-02-28 - MireilleLouys

META TOPICPARENT	name="ObsDMCoreComponents"

+ Various uses and possibilities for obs_publisher_did

How the user will be able to make use of it.

This is not a ObsTAP issue, it is a more generic question: Within the IVOA architecture, how to use a obs_publisher_did? For publications? To find again the data? For programmatic access?

Given it is a CLOB field, nobody can actually use it to find the same data again (and access_url is volatile).

The IVOA should seriously think how to consume it.

<-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

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