Ok, so I walked away from this for a few days then thought about it again. Practically speaking, I don't really give a damn whether or not it's a <x:profile /> or a <link rel="profile" /> because folks who want to do this type of thing will adapt to whatever the mechanism is. The profile thing is a) and identifier and b) an reference to a document that defines the profile. There can be many different ways a profile can be defined so having a media type makes sense. There could be several different profiles defined so to help differentiate, a title or label would be helpful. I had said before that "while the URI of the profile reference should be dereferenceable, most of the time the profile value is going to be used as an identifier" and used that as a justification for not using link. Then I looked over at my link[rel="license"] extension and realized that the exact same argument applies there also. Given this, even tho <x:profile /> would work just fine, I think it's best just to stick to the original <link rel="profile" /> idea. It's a link to a profile; let's call it for what it is.

<link rel="profile" type="some/media-type" href="http://example.com/some-kind-of-profile"; />

- James

Bill de hÓra wrote:

James M Snell wrote:
James Holderness wrote:

James M Snell wrote:

Hmm.. the more I think about this and the more we discuss it, the
less I think I like link[rel="profile"].  While the URI of the
profile reference should be dereferenceable, most of the time the
profile value is going to be used as an identifier.
<entry>
<x:profile>http://example.com/profiles/weblog</x:profile>
<x:profile>http://example.com/profiles/podcast</x:profile>
</entry>

I agree about not using link, but shouldn't the URI be in an attribute
rather than as content. Something like this:

<entry>
<x:profile href="http://example.com/profiles/weblog"/>
<x:profile href="http://example.com/profiles/podcast"/>
</entry>

Works for me.

'href's can traditionally be dereferenced, no big deal - the upside is
the markup structure does gives you scope to extend later.

'ref' - ?

cheers
Bill




Reply via email to