James M Snell wrote:
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.
I can't see any particular use for atom:source myself, but I would definately want profile support at the feed level. As an aggregator I want to be able to display a custom view for a particular feed based on what it contains (e.g. slideshow view if it's a flickr feed - all images). It would be difficult to do something like that with only entry level profiles.
In fact, most of the profiles that are of interest to me are feed based (see question 3 below). I hope we're still talking about the same thing here and I haven't completely misinterpreted what you're proposing.
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.
I'm not sure about this but when in doubt I think it'd be best leaving the option open (i.e. allow multiple).
3. What standard profiles should we consider?
Some of the ones I'd be interested in: * Image feed (flickr.com) * Calendar feed (eventful.com) * Top N list * Wish list
For each of the profiles, we need to specify what it means to conform to that profile
I'm not sure how much of this we should be trying to do ourselves. See question 4.
4. How can we foster the community development and adoption of profiles?
For many of these profiles you could probably come up with one or two sites which are obvious leaders in the field (for example flickr.com for image feeds). If you can introduce them to the concept of a profile, but let them decide on what is required to conform to that profile, you're probably a whole lot more likely to get their support.
Regards James
