On Thursday, January 13, 2005, at 03:31 PM, David Powell wrote:
Forcing 'atom:notation="structured"' into all structured extensions, whether they have other required attributes or not would have even more impact.If there is some way to lose atom:notation without introducing ambiguity it would be better (if something is needed, what about atom:type as used on content - might that be a suitable replacement?)
How about: "a Structured Extension construct must have at least one required attribute or one required child element"?
Yeah, that would work, but it would mean that a Structured Extension such as:
<ex:info>some <b>mixed</b> content</ex:info>
would need to force an unnecessary attribute in there. Probably not a big problem though.
Just a note: the above example would need to be something like the following to set a default namespace:
<ex:info xmlns="http://foo";>some <b>mixed</b> content</ex:info>
...not that it wouldn't be easy to construct an example that didn't, a la:
<ex:info>some <ex:b>mixed</ex:b> content</ex:info>
