DataLink 1.1 Proposed Recommendation: Request for Comments
DataLink describes the linking of data discovery metadata to access
to the data itself, further detailed metadata, related resources, and to
services that perform operations on the data.
The main changes in v1.1 are
- Generalize by adding use cases for links to content other than data files
- VOSI-availability and VOSI-capabilities endpoints are now optional
- Service descriptors can include exampleURL and contentType param(s)
- Added optional link_auth and link_authorized to signal whether authentication is necessary to use the link
- INFO element with standardID mandatory in {links} response
Latest version of
DataLink can be found at:
Reference Interoperable Implementations
Server side
GAVO implemented the following changes = content_qualifier and local_semantics, service descriptor additional features such as DESCRIPTION? name, content_type, etc....
As a matter of example, a couple of links response for various obscore/sia/ssa tables in GAVO server
All these are combined with various semantics or content_type values
Client side
TopCAT prototype (
http://andromeda.star.bristol.ac.uk/releases/topcat/pre/topcat-full_datalink11.jar) displays additional features in service descriptor and makes use of additional links table FIELD such as content_qualifier, authorization and local_semantics; The tool behavior is adapted to the content of these new FIELDS. For example Actions suggested by
TopCat for the links not only depend on content_type but also from content_qualifier.
AladinDesktop is going to adapt to those new features too.
Implementations Validators
The following validators are available for
DataLink
Comments from the IVOA Community during RFC/TCG review period: RFC_start_date - RFC_end_date
The comments from the TCG members during the RFC/TCG review should be included in the next section.
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.
Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document
Comments from TCG member during the RFC/TCG Review Period: TCG_start_date - TCG_end_date
WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.
IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.
TCG Chair & Vice Chair
TCG Vote : Vote_start_date - Vote_end_date
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
Group |
Yes |
No |
Abstain |
Comments |
TCG |
|
|
|
|
Apps |
|
|
|
|
DAL |
|
|
|
|
DM |
|
|
|
|
GWS |
|
|
|
|
Registry |
|
|
|
|
Semantics |
|
|
|
|
DCP |
|
|
|
|
Edu |
|
|
|
|
KDIG |
|
|
|
|
Ops |
|
|
|
|
Radio |
|
|
|
|
SSIG |
|
|
|
|
Theory |
|
|
|
|
TD |
|
|
|
|
StdProc |
|
|
|
|