Couple of errors/questions on XInclude WD 26 October 2000

1) 3.3. Included Items when parse="text"
   Issue XInclude-62-text-encoding raises an interesting question,
 but even assuming that one get an encoding for example it's ASCII,
 how should characters out of the XML range i.e. production [2]
 http://www.w3.org/TR/REC-xml#charsets
 be handled.
  - accepting them looks really bad, we would get an Infoset with chars
    out of the range accepted by XML
  - dropping the full text include is a reasonable option, but how many
    times are we gonna loose the full include due to a misplaced BEL or BS
  - dropping the out of range chars from the resulting infoset seems an
    even better option

2) 3.4. Creating the Result Infoset 
    The example is wrong:
    <xinclude:include href="#xpointer(x/xinclude:include[1])"
      parse="text"/>
 is not allowed per Note in 3.3. about fragment and 3.3. when parse="text".
 s/text/xml/ should be sufficient

3) 4. Syntax
    The DTD example seems wrong:
    s/ELEMENT include EMPTY/ELEMENT xinclude:include EMPTY/

4) 3.2.2. Multiple Nodes
    I may not have understood it but the second paragraph sounds really
strange to me:
--------------------
If the document element in the source infoset is an include element,
it is an error to attempt to replace it with more than a single element.
--------------------

   - when parse="xml" it sounds clear that multiple nodes can result
     for the infoset insertion
   - all document element in the source infoset should be XInclude
     element now.

  Is this a remain of the attribute syntax which should be removed ?
Or did I simply missed the point of this sentence ?

Daniel

-- 
Daniel.Veillard@w3.org | W3C, INRIA Rhone-Alpes  | libxml Gnome XML toolkit
Tel : +33 476 615 257  | 655, avenue de l'Europe | http://xmlsoft.org/
Fax : +33 476 615 207  | 38330 Montbonnot FRANCE | Rpmfind search site
 http://www.w3.org/People/all#veillard%40w3.org  | http://rpmfind.net/

Received on Monday, 6 November 2000 13:21:18 UTC