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). 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/ This should help to clarify their intended purpose and usage. -- DougTody 2 March 2011
While in principle it does not make sense to have
By the way, this brings the additional consideration that
Igor Chilingarian in a mail dated 8 Mar 2011 20:19:28 at some points wanted the document to stress that obs_publisher_did could serve as a primary key. While I don't believe this is much of an issue in the standard, I'd like to register my dissent here. Unless I'm severely mistaken about publisher DIDs, they are to identifiy datasets, not concrete files. If I provide a data set in various formats, I may very well have several rows with the same pub DID, no? -- MarkusDemleitner - 09 Mar 2011 | ||||||||
Added: | ||||||||
> > |
Well I follow Doug there. It could be very usefull to get the whole
satabdard description by querying on obs_publisher_did.
-- FrancoisBonnarel - 15 Mar 2011 | |||||||
<--
|