2009/5/20 Nikunj R. Mehta
<nikunj.mehta@xxxxxxxxxx>
Actually, if feed and service are available, then one could use the app:collection mechanism to discover the feeds that are editable as well as its publishing metadata.
Sure, but you'll always need to GET the link@rel="feed" first to discover if it's writable, unlike link@rel="service" where you get the information directly.
Actually, HTML manages its own registry of link rel values and uses a slightly different syntax for this attribute. Mark Nottingham's been working to get a unified Link registry that can be used with a new HTTP header [1]. As to where a link should be specified for collections and services, the HTML5 spec [2] identifies "link" as document metadata and hence expects such links to be placed in the head element. N.B. rel=service has not been included in the initial registry of HTML link types.
XHTML2 spec [3] identifies "link" as metainformation and expects links to be placed in the head document
Is there some other use you have in mind?
I agree that link is a document metadata and should be in the head element, but for certain rel values, it's very common to find them in the body too, as a way to add some semantics. You'll find a lot of pagination links with <a rel="next" href="" for example.
Hadrien