David Powell wrote:
I think it would be bad to have two different mappings for the same
extension depending on whether the instance happenned to contain any
tags.
I'm not sure why you would have two different mappings. Wouldn't it just be an XML property every time?
I can't think of a use case for extension properties in the Person construct. I think we should leave those undefined. The only thing I can
think of putting in there is FOAF, but that works just as well as a child of entry.
There can be multiple Person constructs per entry though. One author,
plus several contributors.
Right, what's the use case? FOAF doesn't need to be contained by atom:person. Again, I'm not up for banning it, just making it undefined.
Robert Sayre
