On 14 May 2012 03:16, Mark Nottingham <
mnot@...> wrote:
> On 12/05/2012, at 4:16 AM, James M Snell wrote:
>> 2. I mentioned this before in off-line direct conversation with you,
>> but I think it would be worthwhile to have a "profile" hint whose
>> value is an array of absolute URIs that identify the higher level
[...]
> Of course, it's still useful to say that this particular collection of resources and representations they produce will meet a certain task, but that can be done in documentation; making it machine readable is an attractive nuisance. IMO.
The idea occurs that you might be able to provide the "hints" in the
form of link relations. Of course, then it's turtles all the way
down...
It's tempting to think of 'hints' as the result of a HEAD request for
the resource. Which leads then me to speculate about the nature and
usefulness of HEAD with respect to POST/PATCH/PUT/etc... Think about
specifying Accept: headers in responses.
Then we can all sing the metadata song. Metadata, metadata,
meta-meta-metadata...
_______________________________________________
apps-discuss mailing list
apps-discuss@...
https://www.ietf.org/mailman/listinfo/apps-discuss
