[From nobody Fri Aug  6 17:05:26 2004
X-Mozilla-Status2: 00000000
Message-ID: <3A3EAE7B.177B09EA@collab.net>
Date: Mon, 18 Dec 2000 16:40:27 -0800
From: Jason Hunter <jhunter@collab.net>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Elliotte Rusty Harold <elharo@metalab.unc.edu>,
	JDOM Interest <jdom-interest@jdom.org>
Subject: Re: [jdom-interest] Additional namespace issues
References: <3A39AED6.E7D8D911@collab.net>	
	<p04330101b65fdd4af532@[192.168.1.6]> <3A3A6A74.7AB28278@collab.net>
	<p04330100b663c19bfd77@[192.168.1.6]> <3A3E8F0A.F635BA44@collab.net>
	<p04330100b6644d7b3b86@[192.168.1.6]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> This is the same issue we've been going over for the last six months.
> The problem is not namespace qualified names in attribute NAMES. It's
> namespace qualified names in attribute VALUES. 

Ah, sorry.  As I said, I was confused.  :-)

> <xsl:template match="sg:title">
>    Various instructions to work with the matched element...
> </xsl:template>
> 
> Given the Attribute object for the above match attribute, I need to
> determine the namespace to which the sg prefix is mapped. Schemas do
> the same thing. I think XPointers and RDF do too, and there are
> probably other cases. getNamespacePrefix() and getNamespaceURI() only
> work for the attribute name.

OK, you've convinced me.  Any dissenting opinions?

> Probably, and I suspect getDefaultNamespace() should just be
> syntactic sugar that calls getNamespace(""). However, if we don't
> include getDefaultNamespace(), we're just going to have answer that
> question on the jdom-interest mailing list every two days :-)

getDefaultNamespace() to the uninitiated might look like it returns the
namespace on this particular element.  There are so many *Namespace*()
methods I'm leery of adding anything not really necessary.

-jh-


]