Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] XOM 1.0 alpha 1 is here

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Elliotte Rusty Harold <elharo AT metalab.unc.edu>
  • To: "Bradley S. Huffman" <hip AT cs.okstate.edu>
  • Cc: xom-interest AT lists.ibiblio.org
  • Subject: Re: [XOM-interest] XOM 1.0 alpha 1 is here
  • Date: Wed, 9 Jun 2004 15:46:55 -0400

At 10:20 AM -0500 6/9/04, Bradley S. Huffman wrote:

Right, they don't cover cases where documents are broken apart and
recombined so any algorithms they provide are probably going to break
down. That's why I advocate getter and setters for the source URI along
with a default implementation of the XML Base algorithm (which XOM has
right now in getBaseURI).

With the source URI, access to a element's attributes and access to it's
parental hierarchy a application should have the information it needs to
apply it's own resolution alogrithm that works in those use cases where
the default doesn't.

But right now I don't see a way to always get the URI of the source from
which the document was loaded (if it exists). getBaseURI may return it.
Then again, it may not :-(

setBaseURI() and getBaseURI() are not perfectly symmetric. setBaseURI() effectively sets the actual entity URI for the element. getBaseURI() returns the base URI as defined by XML Base, which is the actual entity URI, possibly modified by xml:base attributes. I don't really see the use case for a method that returns the actual entity URI.
--

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




Archive powered by MHonArc 2.6.24.

Top of Page