Re: request to register 'profile' link relation (http://tools.ietf.org/html/draft-wilde-profile-link-03)

tried to digest this over and over again, and failed.

#1 is there somewhere that says that a describedby link should be
dereferenced _automatically_ when encountered? (that is what you're saying,
right? i mean, you should be able to dereference all links)

#2
Relation Name: describedby

Description: The relationship A "describedby" B asserts that
resource B provides a description of resource A. There are no
constraints on the format or representation of either A or B,
neither are there any further constraints on either resource.

This description makes me think that although describedby is not very
specific, it can be very well used to point out what type of constraints
this resource/media-type abides (e.g. json schema) - while you could very
well have only a literal description in plain text.

#3 when you say " the intention is not that clients should follow that
link; the semantics are in the identifier itself", I guess you refer to
both a link with rel=profile (in the Link header or in the payload), and to
the profile param of a media-type ?
I can understand that as a param to a media-type, it acts as an identifier,
just like the media-type itself "application/json" or
"application/vnd.andrei+json"
but as a link, it has to be "deference-able", so that the client can follow
it. Otherwise, and maybe I am wrong, but it is not a link anymore.

#4 "resource follows additional conventions"
If I have a media-type "application/vnd.andrei+json" - which under
http://tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-04means
that it has JSON syntax, and some additional semantics of
"vnd.andrei". Accepting such a media-type means that the client is already
aware of such syntax and semantics, so pointing the client to "additional
conventions" is not really the term here. Instead I would say that this
link (may it be describeby or profile) is a description of those
conventions which are already shared between server and client i.e. a json
schema of application/vnd.andrei+json


Thanks for sharing some knowledge.
Sorry if I'm not seeing some trivial things.

On Sun, Sep 23, 2012 at 12:19 AM, Erik Wilde <[email protected]> wrote:

> describedby is intended to be dereferenced and link to a description of a
> resource (and since this is from the semweb world, this means "metadata
> about the resource", and often it will be in a the form of some RDF media
> type). profile, on the other hand, is intended to serve as a signal that a
> resource follows additional conventions (as described in
> http://tools.ietf.org/html/**draft-wilde-profile-link-03#**section-3<http://tools.ietf.org/html/draft-wilde-profile-link-03#section-3>),
> but the intention is not that clients should follow that link; the
> semantics are in the identifier itself.
>



-- 
andreineculau.com <http://www.andreineculau.com> -- Emails should be five
sentenc.es <http://five.sentenc.es> or less.