Bill,
I'm sorry, I don't think I get what you're saying; the words all make sense, but I don't know how you got here.
Atom currently constrains feed data (e.g., you MUST have a title, there MUST only be one) based on the most common use case; bloggling/news syndication. How does this move towards "agents enforcing policy on one another?" If anything, the Pace makes it *less* likely that publishers will make assumptions about how data will be processed downstream; as Atom is currently specified, there are lots of such assumptions built in.
The Pace doesn't place any requirements on Atom Processors WRT @profile; it's just an advisory flag that tells it what kinds of metadata it can count on appearing in the feed.
On Feb 4, 2005, at 1:53 AM, Bill de h�ra wrote:
One concern I have is that I don't want to see feed data constrained according to usecases (ie system monitoring); that makes the data less useful and goes down the route of publishers telling clients how to write their applications or making assumptions on how data will be processed downstream. While I believe that claiming Atom is a container for metadata is good, I doubt that profiling represents a more flexible approach - it moves us away from agents coordinating together to agents enforcing policy on one another via a profiling mechanism.
-- Mark Nottingham http://www.mnot.net/
