James M Snell wrote:
>
> Another subject that has come up in recent discussions is an extension
> that can be used to specify the purpose of a feed. For example, is the
> feed an archive, is it a podcast, is it used for discovering web
> services or publishing blog content, etc.
>
> The approach that I have in mind is to use link[rel="profile"] where the
> href points to a profile document of some sort.
>
> For example,
>
> <feed>
> ...
> <entry>
> <link rel="profile" href="http://example.com/profiles/podcast"; />
> <link rel="profile" href="http://example.com/profiles/weblog"; />
> ...
> </entry>
> </feed>
>
> The profile documents could be anything really, but generally describe
> the kinds of metadata and content that the entry is expected to
> contain. For instance, the podcast profile could indicate that the
> entry should contain at least one link[rel="enclosure"].
> Any single entry may contain multiple profile links. It is up to the
> feed consumer to make sense of it all. If an entry specifies
> contradictory profiles, it's up to the consumer to sort it out.
> The profile documents should be dereferenceable.
>
> Thoughts? Gripes? Praise?
I think you're proposing to enable a kind of Atom microformat - "if you
see profile ?x check for ?a ?b and ?c". Sorting it out on consumer
sounds flaky ('sounds', not 'is'), but this also might be very cool. I
wonder why you need a link to do this instead of foo:profile tag.
cheers
Bill
