Datalink vocabulary additions

[Markus Demleitner]

Dear Semantics activists,

On Fri, Nov 13, 2015 at 02:09:09PM +0100, Markus Demleitner wrote:
> Dear Semantics,
> 
> At the Sydney Semantics Session
> (http://wiki.ivoa.net/twiki/bin/view/IVOA/InteropOct2014Semantics) I
> had a little talk on the maintenance of the vocabulary for the
> [and so on]

This is an update to the post-Sydney mail[1] quoted above.
unfortunately, I didn't make it to the vocabulary maintenance
breakout in Stellenbosch, but it seems there's now a better agreement
on how our vocabulary lists are maintained (and discussed).

So, here's a few proposals regarding the Datalink vocabulary.  Is there
anything else I should do to push them ahead for inclusion/further
discussion?


(1) I'd like to have a term for larger chunks of metadata in separate
files.  I'd need that to link to observation logs, but I could also
see logs a pipeline has written, or an extensive provenance, or
similar.

Proposed term(s): #metadata?  #documentation?  (as a child of
#auxiliary, I guess)


(2) I'd like to have a term for things like a rebinned (higher S/N)
version of the dataset, or perhaps the data in a different waveband on a
multi-band instrument, or the same observation with a different
instrument setup (as in V500/COMB vs.  V1200 in Califa), etc.  Essentially:
Science data that was obtained "together with" #this but that's not
identical with #this.

Proposed term(s): #science? (but that's a bit too broad)  #alternate?
  (as a child of #this?)


(3) I'd like to have a term for a different representation of the same
dataset, e.g., a spectrum that was originally a FITS image formatted  as
a FITS table, an SDM VOTable, or a CSV file (where of course the SDM
VOTable would be the #this).  Essentially, the same data as #this modulo
the different expressivenesses of container formats.

Proposed term(s): #alt-format?  (as a child of #this?)


(4) I'd like to have a term for a previous version of a dataset.  I have
that in califa, where I'd like to have *some* way to get DR1 and DR2
data, but I really don't want to clutter all-VO SSA or obscore searches
with these guys.  So, I'm adding links to old files (where they exist)
in datalink results for new files.  This isn't really #progenitor, since
the old files aren't in the provenance chain of the new files (which are
generated from yet other data files).  It's... well, a previous version,
and hence I'd like to see

Proposed term: #previous-version (as child of #auxiliary?)


That concludes the proposed concepts for this time; #fault from the
original proposals I've dropped.  One other thing I'd like:

(5) #proc currently has "Server-side data processing result" as its
explanation.  What really is in such datalink rows is, I submit,
better described by "reference to a server-side processing service"
-- so, can we change that explanation?

Opinions?  Proposals for sharper descriptions, better terms?  Any
contributions are welcome.

Thanks,

         Markus


[1] http://mail.ivoa.net/pipermail/semantics/2015-November/002495.html