[rfc-i] The alternateURI element in v3
paul.hoffman at vpnc.org
Thu May 8 08:39:28 PDT 2014
On May 8, 2014, at 8:23 AM, Julian Reschke <julian.reschke at gmx.de> wrote:
> RFC 5988 defines linking. It hasn't to do anything with MIME. It *does* define an HTTP header field, but that's only one way to represent a link.
Good point. I had forgotten that it became more generic as the discussion went on.
> The HTML equivalent is the <link> element, which has a "rel" attribute. One trivial approach would be just to adopt that as a top-level document, and to define those relation types we need (such as "doi").
But that's the point: if we know all the relation types we need, it would be much simpler to just create optional attributes to <rfc> for each of them.
If you can't decide if the problem statement is "we know the types of links we want" or "we want to allow all sorts of links", it is hard to design a solution, and particularly hard to design one that will make sense to authors who are not as familiar with web technologies as you are.
More information about the rfc-interest