Implementation appendix

[Bonnarel]

Some text guiding implementers on how to use DataLink, recognize its endpoints in various contexts was missing. It is here proposed in an Appendix. Related to issue #31

[msdemlei]

While it might be a good idea to give some guidance as to how the main datalink deployment scenarios look like (i.e., datalink resource descriptor on legacy DAL results and datalink documents in an access URL), I think that should be very compact (not more than half a page) and come at the end of the introduction. The appendix proposed here I find rather long and also too convoluted. I would like to drop the PR in its entirety (and would volunteer to draft a PR for the half-page scenarios).

I'll not veto it, though, if everyone else thinks it's useful, except that a few technical points must be addressed before I'd approve this:

• In ivoatex, don't use the appendices environment (for now, at least). Just say \appendix and go on with sections
• Please keep your input lines shorter than 80 characters so later diffs remain sensible and readable
• Please use typographic quotes; in English-language LaTeX, that's `` and ''.

[Bonnarel]

We discussed this point last week during the ESCAPE tech Forum meeting. I think implementation hints are necessary for DataLink. I don't think half a page is enough. If people agree with Markus it's too long I will drop the appendix and transform it in an implementation note ? Thoughts ?

[molinaro-m]

I would be in favour of having an implementation note, for this and maybe other needs.

[Bonnarel]

Any other opinion about Appendix versus implementation note. If everybody OK I close this comment and push the content of the Appendix in an implementation note

[pdowler]

DataLinkImp note PR#40 has been merged. Closing this.