Re: [core] Link target attributes in CoRAL (was: Review of CoRAL)

[Christian M. Amsüss <[e-mail]>]

On Tue, Nov 06, 2018 at 09:21:36AM +0100, Klaus Hartke wrote:
> Of course, we could for new link target attributes, as they pop up,
> define an equivalent more semantic link relation type. In Link Format
> you would use the link target attribute; in CoRAL, the link relation
> type. If a converter encounters a new, unknown attribute, it would fail.

It just occurred to me that there is another point to be made for
per-relation rules: There are target attributes that are URI-valued.
That's something I'd recommend to avoid in the first place, but still
does happen (eg. ol= in protocol-negotiation, or even base= in RD which
I can't really rip up now).

It's a trade-off, though: While making the resulting data semantically
more palatable, it makes link filtering odder (a `GET
/.well-known/core?ol=coap://x/`  CoRAL response one'd need to
think `GET /.w-k/c?anchor=coap://x/&rel=attr:ol`). I still think it's
worth it (speaking as someone who'll have to implement the lookups).

Christian

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom