msdemlei/datalink-xslt

An XSLT stylesheet to turn IVOA datalink into HTML documents.

You can run this (or something somewhat updated) on your own datalink documents at https://dc.g-vo.org/shomydl/q/f

If you hand out datalink documents, consider using the files provided here on your site. See below for adoption instructions.

Notes:

This hardcodes the VOTable namespace to version 1.3, which is what the VO will keep for the rest of VOTable 1. If you really still use version 1.2, you will need to update your VOTable writer.
This could certainly use quite a bit more styling, in particular for the non-javascript version. PRs are welcome.
Without javascript, multiple datasets in one response are not terribly conspicuous.

Adoption Instructions

You can of course organise the various files differently, but here is a run-down of things needed for having your datalinks formatted.

make a directory on your web server that will contain the XSLT and the auxiliary files; we'll call it X, and the place it is visible at Y.
Copy datalink-to-html.xsl, sodapars.js, and footprintedit.js from this distribution to X.
Make a sufficiently recent jquery available through the web server, e.g., by installing libjs-jquery on Debian or by pulling it from https://jquery.com/
Get samp.js from https://github.com/astrojs/sampjs.git and put it into X.
Get https://aladin.u-strasbg.fr/AladinLite/api/v2/latest/aladin.min.js and https://aladin.u-strasbg.fr/AladinLite/api/v2/latest/aladin.min.css and put them into X.
In datalink-to-html.xsl, look for <script and fix the paths to jquery.js (wherever that is), and samp.js and sodapars.js (which would be in Y).
At the top of sodapars.js, fix the three paths at the top of to file to the aladin files and footprintedit javascript (which would be in Y).
After all these preparations, simply arrange for:
```
<?xml-stylesheet href='X/datalink-to-html.xsl' type='text/xsl'?>
```
to be output at the top of your datalink documents.