www-xml-xinclude-comments@w3.org from February 2004 by thread

A possible security issue with accept attributes Elliotte Rusty Harold (Thursday, 26 February)

RE: Ambiguity in treatment of accept attributes Jonathan Marsh (Thursday, 26 February)

RE: Section 4.3 reference to character model Jonathan Marsh (Thursday, 26 February)

RE: accept-charset vs. encoding Jonathan Marsh (Wednesday, 25 February)

RE: accept and accept-charset attributes Jonathan Marsh (Wednesday, 25 February)

RE: Streaming basically impossible in the face of XPointers Jonathan Marsh (Wednesday, 25 February)

RE: Is inclusion stable? Jonathan Marsh (Wednesday, 18 February)

RE: XML Schema WG Comments on Last Call Draft Jonathan Marsh (Tuesday, 17 February)

RE: missing href, parse="text", xpointer="something" Jonathan Marsh (Tuesday, 17 February)

RE: Interpretation of fragment IDs when parse="xml" Jonathan Marsh (Tuesday, 17 February)

RE: Assymettry bewteen xi:include and xi:fallback Jonathan Marsh (Tuesday, 17 February)

RE: white space in parse attribute Jonathan Marsh (Tuesday, 17 February)

RE: New Namespace Jonathan Marsh (Tuesday, 17 February)

RE: Inclusion loops rely only on href, not on xpointer Jonathan Marsh (Tuesday, 10 February)

RE: Comments for WD-xinclude-20031110 Jonathan Marsh (Tuesday, 10 February)

RE: XPointer example error Jonathan Marsh (Tuesday, 10 February)

RE: URI vs IRI in XInclude spec Jonathan Marsh (Tuesday, 10 February)

XOM 1.0d23 implements the latest draft Elliotte Rusty Harold (Monday, 2 February)

XPointer selects an xi:fallback element in another document Elliotte Harold (Sunday, 1 February)

Last message date: Friday, 27 February 2004 07:42:29 UTC