Ok, <x:profile ref="{uri}" /> works very well I think.
profileElement = element x:profile {
attribute ref ( URI ),
undefinedContent
}
Now for some processing questions...
1. Can a profile element appear in an atom:feed/atom:source? If so,
what does it mean? I think it should with the caveat that the profile
attribute should only impact the feed and should not reflect on the
individual entries within that feed.
2. Can multiple profile elements be specified? I think it should. That
way we can mark an entry, for instance, as being both a blog entry and a
podcast.
3. What standard profiles should we consider?
* Weblog (for atom:feed).. BlogEntry (for atom:entry)
* Wiki (for atom:feed).. WikiPage (for atom:entry)
* Podcast
* Archive
* Search Results
* what else?
For each of the profiles, we need to specify what it means to
conform to that profile
4. How can we foster the community development and adoption of profiles?
- James
Bill de hÓra wrote:
'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
