Cool! Some quick feedback:
* you should explicitly accommodate target attributes (i.e., extension fields)
* 'rev' was only included in 5988 for backwards compatibility with some fairly
esoteric use cases; don't think it's necessary or good here.
* you need to specify how to determine the context of the link (using RFC5988
terminology).
Cheers,
On 27 Feb 2015, at 3:25 am, Andrew Newton <andy(_at_)hxr(_dot_)us> wrote:
On Wed, Jan 28, 2015 at 2:12 AM, Mark Nottingham <mnot(_at_)mnot(_dot_)net>
wrote:
The document effectively gives a "type" for the URI by associating a value
from the ENUM service registry. While that makes sense from the standpoint of
ENUM, if this mechanism is truly generic to *all* URIs, it seems to me that
it'd be much more sensible to use the typing system already in place for URIs
-- link relations <http://tools.ietf.org/html/rfc5988>.
Such a good idea that there is already a draft with just such an approach:
https://datatracker.ietf.org/doc/draft-newton-link-rr/
-andy
--
Mark Nottingham https://www.mnot.net/