Re: [apps-discuss] [rest-discuss] Re: Feedback on draft-wilde-profile-link-00

[Julian Reschke <[e-mail]>]

On 2012-04-12 18:39, Erik Wilde wrote:
> hello julian.
>
> On 2012-04-12 09:10 , Julian Reschke wrote:
>> It seems you are using "profile" in a very different way then it was
>> used in HTML4; is this really a good idea?
>
> i certainly do not intend to use it in a different way, because like
> you, i do not think that would be a good idea. my current definition is
> that "a profile are additional semantics that can be used to process a
> resource representation, such as constraints, conventions, extensions,
> or any other aspects that do not alter the basic media type semantics."
>
> my understanding of HTML's profile was always like this. quoting from
> http://www.w3.org/TR/html4/struct/global.html#profiles :
>
> "User agents may be able to recognize the name (without actually
> retrieving the profile) and perform some activity based on known
> conventions for that profile. For instance, search engines could provide
> an interface for searching through catalogs of HTML documents, where
> these documents all use the same profile for representing catalog entries."
>
> mark also noted that he regards a profile mostly as saying something
> about a representation's content, such as a metadata profile in HTML,
> saying that the web page uses dublin core. but even when you look at the
> dublin core HTML profile (http://dublincore.org/documents/dcq-html/), it
> also defines conventions about links
> (http://dublincore.org/documents/dcq-html/#sect-2-4), and not just about
> non-link data. which is the point i was trying to make saying that the
> line between "format extensions" and "links" is fuzzy: essentially, a
> link *is* a format extension, only one that extends beyond the current
> resource.
>
> i am not sure i was able to fully address your concerns, so if you still
> think i am "redefining" what 'profile' is supposed to do, could you be a
> bit more specific why you think that's the case, and how you'd like to
> see it done?
> ...

Maybe we need to switch to examples to get a clearer picture.

With "profile" I understand that the link *target* is a URI describing 
the profile, such as <http://www.w3.org/2006/03/hcard> which describes 
that hcard profile.

If you want to use the profile link relation to declare that something 
is a an AtomPub server, on which resource would you set the link relation?

Best regards, Julian