David Powell wrote:
PersonConstructs aren't currently allowing extension elements.
anyForeignAttribute and anyForeignElement are currently not used anywhere.
The second point reflects a problem with the draft. I noticed this while writing it, but figured the WG needed to spot it.
"The atom:entry element MAY contain any namespace-qualified [W3C.REC-xml-names-19990114] elements as children."
Ok, but does that imply foreign content is not allowed elsewhere? I suggest the WG did not intend for that to be the case, the sentence from 6.4 more accurately reflects WG opinion:
"Atom allows foreign markup anywhere in an Atom document. Child elements of atom:entry and atom:feed are considered "metadata" elements, and are described below. Child elements of Person Constructs are considered to apply to the construct. The role of other foreign markup is undefined by this specification."
My personal view was that Person constructs should not define the meaning of foreign content, but the WG clearly favored it.
Robert Sayre
