XOM API for Processing XML with Java

[Nils_Kilden-Pedersen AT Countrywide.Com]

How about making it explicit, i.e. adding a boolean argument: 
preserveBaseURI. Would that work?

Nils
>From hip AT cs.okstate.edu  Tue Mar 23 12:52:39 2004
Return-Path: <hip AT cs.okstate.edu>
Delivered-To: xom-interest AT lists.ibiblio.org
Received: from csa.cs.okstate.edu (a.cs.okstate.edu [139.78.113.1])
        by happyhouse.metalab.unc.edu (Postfix) with ESMTP id 5835020150
        for <xom-interest AT lists.ibiblio.org>;
        Tue, 23 Mar 2004 12:52:31 -0500 (EST)
Received: from cs.okstate.edu (localhost [127.0.0.1])
        by csa.cs.okstate.edu (Postfix) with ESMTP
        id B1344A06C6; Tue, 23 Mar 2004 11:52:26 -0600 (CST)
To: John Cowan <cowan AT ccil.org>
Subject: Re: [XOM-interest] Builder argument swap 
In-Reply-To: Your message of "Tue, 23 Mar 2004 12:41:56 EST."
        <20040323174156.GC21568 AT ccil.org> 
Date: Tue, 23 Mar 2004 11:52:26 -0600
From: "Bradley S. Huffman" <hip AT cs.okstate.edu>
Message-Id: <20040323175226.B1344A06C6 AT csa.cs.okstate.edu>
Cc: xom-interest AT lists.ibiblio.org
X-BeenThere: xom-interest AT lists.ibiblio.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: xom-interest.lists.ibiblio.org
List-Unsubscribe: <http://lists.ibiblio.org/mailman/listinfo/xom-interest>,
        <mailto:xom-interest-request AT lists.ibiblio.org?subject=unsubscribe>
List-Archive: <https://lists.ibiblio.org/sympa/arc/xom-interest>
List-Post: <mailto:xom-interest AT lists.ibiblio.org>
List-Help: <mailto:sympa AT lists.ibiblio.org?subject=HELP>
List-Subscribe: <http://lists.ibiblio.org/mailman/listinfo/xom-interest>,
        <mailto:xom-interest-request AT lists.ibiblio.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2004 17:52:39 -0000

John Cowan writes:

> Bradley S. Huffman scripsit:
> 
> > Elliotte Rusty Harold writes:
> > 
> > > We've discussed this in the past, and the result was the current 
> > > behavior. However, I could be convinced that elements should retain 
> > > their base URI on being detached from the parent. Right now that 
> > > isn't obviously right though.
> > 
> > Right now sometimes they retain there base URI when they're detached, 
> > sometimes they don't, it all depends on how the base URI is set.
> 
> I think that violates the Law of Least Astonishment, and on reflection I
> also now think that elements should retain their base URIs when detached.
> The base URI is an essential part of an element's meaning if the element
> contains relative URIs in its content or attribute values; moving it
> around from one document (or part of a document) to another shouldn't
> implicitly change the meaning.
> 
> If this is to be done, the question is, how?  Shall detaching an element
> just cause the base URI to be set internally, and leave generating
> xml:base attributes up to the Serializer, or should it actually generate
> an Attribute object at detach time?  I incline to the former.

After more thought and when base URIs come up again on the JDOM mailing
list, I think I'm going to suggest that parent nodes carry the actual base
URI with methods to set/get the actual base URI only, and move all code for
resolution to a seperate class (XBase).  It means a extra class, but it
would keep things simple in the core with no infomation hidden and moves
the troubling parts to single class that could be subclassed when ambiguities
arise. To me this approach seems to follow the K.I.S.S. principle.

Brad