[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Updated XInclude DoC

• To: jcowan@r...
• Subject: Re: Updated XInclude DoC
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Sat, 24 Jan 2004 07:52:15 -0500
• Cc: Paul Grosso <pgrosso@a...>, xml-dev@l...
• In-reply-to: <20040123195459.GO14690@s...>
• References: <DF1BAFBC28DF694A823C9A8400E71EA202548B37@R...> <4.3.2.7.2.20040123092148.067e21f8@172.27.10.30><20040123195459.GO14690@s...>

At 2:54 PM -0500 1/23/04, jcowan@r... wrote:

Hmm, did you really mean to send this to the xml-dev list?

>2.14:  Using parse="text" and an xpointer should mean that whatever 
>the xpointer
>points to is converted to text and included as such.

Regardless, I will comment on point 2.14. This is very tricky because 
the XPointer will typically be resolved through an API such as DOM, 
JDOM, SAX, or XOM that does not provide full access to the original 
text content. That is, it eliminates white space in tags, removes the 
distinction between <tag/> and <tag></tag>, and so forth. The data 
would need to be reserialized to be included as text, and the 
reserialization might well not match the original text. At a minimum 
these issus need to be addressed in the spec, and perhaps XPointers 
hodul be forbidden when parse="text". If the document is parsed as 
text, then does an XPOinter fragment identifier even apply? (Hmm, is 
there a fragment identifier type defined for text/plain?)
-- 

   Elliotte Rusty Harold
   elharo@m...
   Effective XML (Addison-Wesley, 2003)
   http://www.cafeconleche.org/books/effectivexml
   http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA

• Follow-Ups:
  • Re: Re: Updated XInclude DoC
    • From: John Cowan <cowan@m...>

• References:
  • Re: Updated XInclude DoC
    • From: jcowan@r...

• Prev by Date: RE: Microsoft files for XML patents, says C|Net
• Next by Date: RE: XLink and mixed vocabulary design
• Previous by thread: Re: Updated XInclude DoC
• Next by thread: Re: Re: Updated XInclude DoC
• Index(es):
  • Date
  • Thread