I use elements w/ rels. I some cases, i’ve actually enclosed all the links for the document in a element to make discovery easy, but not often.

Also, I sometimes add a method attribute with parameters within the link:

that starts to break down for anything other than simple content-type formats, tho.

FWIW, I still use ‘unqualified’ rels “proceed”, “next”, “drop”, etc. rather than following the full URI pattern; proly gonna hafta cave on that one.

cheers.

Thanks for the comment. An <a/> tag is, as you point out, just as good – as long as the media type guides the client to identify that as a hypermedia control. I’ve been living with Atom for too long, perhaps. The general point is: closed set (plus media type processing model) is better than open set, if only from a pragmatic point of view.

Kind regards

ian

Thanks for the comment.

Yep. I wasn’t tackling media types here, but yes, the media type specifies the processing model, and a really good (hyper) media type will tell you how to identify hypermedia controls.

Kind regards

ian

Link discovery requires semantics specified by the media type or some other means. Of course, a human reader may be able to guess the intent, and possibly use it right, but that’s not the case for machine clients.