Re: Link: grandfathered format-specific registered relations

I'm not sure what this has to do with my message.

While we could try to optimistically define the semantics of each of  
these in a generic fashion, it's likely to be a shot in the dark --  
i.e., there is as of yet no proven value to more than one application  
in these, just speculation that it may be later.

To reiterate - registered relations are supposed to be generic, while  
extension relations have no such constraint. However, the registry  
currently has some specific relations in, because they're already there.

As such, the proposal is to recognise this in the registry.

On 22/08/2009, at 10:45 AM, Nicolas Alvarez wrote:

> Mark Nottingham wrote:
>> I'm thinking that the following registered relations are in fact
>> specific to one format or application, and this should be noted in
>> their registrations.
>> current
>> edit
>> edit-media
>> enclosure
>> next-archive
>> prev-archive
>> replies
>> service
>> Comments?
> Wondering... As Sam says, relations should be generic and types  
> specific.
> That makes sense for GETtable URis, for example, rel=replies is  
> generic and
> type would say whether it's a RSS feed or an HTML page with replies.
> However, what about POSTable URIs? The type attribute, as I  
> understand it,
> says what data you'll get back, not what data to send. How can you  
> say that
> a rel=edit link is a URI where you can POST a specific data type,  
> maybe
> getting text/html in the response?

Mark Nottingham

Received on Saturday, 22 August 2009 01:44:46 UTC