Re: Broken RELAX NG Grammar in Appendix B of draft-06

2005-03-19 Thread David Powell 


I noticed another bug in the RNG. The collected RNG is missing a '?'
after atomIcon:

 atomSourceFeed =
element atom:source-feed {
   atomCommonAttributes,
   (  atomTitle
atomUpdated
atomLink+
atomIcon

should be:

 atomSourceFeed =
element atom:source-feed {
   atomCommonAttributes,
   (  atomTitle
atomUpdated
atomLink+
atomIcon?


-- 
Dave

Re: Broken RELAX NG Grammar in Appendix B of draft-06

2005-03-19 Thread Julian Reschke 
David Powell wrote:
Two more things I've just noticed:
PersonConstructs aren't currently allowing extension elements.
anyForeignAttribute and anyForeignElement are currently not
used anywhere.
Proposal for test procedure:
- please publish an updated RNC file somewhere (on atomsub.org?)
- those who already produce experimental atom-06 feeds, please check 
them with that RNC

(my test feeds are http://greenbytes.de/tech/webdav/webdav.atom and 
http://greenbytes.de/tech/webdav/webdav-ietf.atom)

Best regards, Julian
--
green/bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

Re: Broken RELAX NG Grammar in Appendix B of draft-06

2005-03-19 Thread Robert Sayre 
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