Re: Re: draft-wilde-profile-link-02 published

hello philipp.

On 2012-06-15 5:46 , Philippe Rathé wrote:
> would it be a bad idea to extend text/plain with a profile link to add
> basic hypermedia controls? I'm speaking of controls that would be
> displayed as plain text, maybe appended at the end of the text
> representation as a tiny domain specific language. Nothing would
> change to the processing rule of text/plain. But the presence of a
> certain link relation would allow a user agent to parse the dsl and
> allow a person to activate them. In the context of a command line
> interface, that could be practical.

that's an interesting idea, and to some extent (just thinking beyond 
only links here) you're proposing some form of markdown (i am using this 
term generically here), right? i am afraid there are many variants of 
that, and i haven't seen any one standardized, but maybe the original 
one does have quite a bit of adoption. if a markdown variant would 
officially declare what its profile URI is, then it would be quite a 
smart way of telling clients that they could do a better job of 
rendering content, if they received text/plain associated with that 
profile URI.

> How could a link relation could be add to a text/plain response?

since text/plain has no standardized way where to put links that could 
be used, the only possible way would be the context, so in case of HTTP 
that would be a Link header. if text/plain were redefined to also allow 
a media type parameter named "profile" (as recommended in 
http://tools.ietf.org/html/draft-wilde-profile-link-02#section-3.1), 
then this would be another good place to put it (and one that could be 
used in emails as well, which is not the case for the HTTP Link header).

great idea, are you planning to implement this in some way? cheers,

dret.

-- 
erik wilde | mailto:[email protected]  -  tel:+1-510-2061079 |
            | UC Berkeley  -  School of Information (ISchool) |
            | http://dret.net/netdret http://twitter.com/dret |