> Potential solutions that occur to me: > > 1. Ignore the problem > 2. PaceEntriesElement could handle this > 3. PaceFeedRecursive could handle this > 4. PaceAtomHeadInEntry could handle this > 5. PaceAggregationDocument could handle this > > I honestly can't say which I prefer. Would anyone like to try to put > together examples of the solution in #2 through #5 so that we can > consider the alternatives? >
6. Handle the problem in a non-core extension. The core Atom syntax does not have to deal with all these cases as long as it does not interfere with someones ability to deal with cases later on. Get version one out the door. Get folks to start implementing it. Start writing up extensions. Get folks to implement those extensions. Figure out which extensions are Really Useful. Add those Really Useful Extensions to the core later. -- - James Snell http://www.snellspace.com [EMAIL PROTECTED]
