> Date: Fri, 27 Jan 2006 09:58:16 -0500
> From: Mark Hinnebusch <[log in to unmask]>
>
>>> The two "type" attributes in question here are from different
>>> namespaces, mods and xlink, so there is no conflict.
>
> While this resolves the immediate problem, it doesn't solve the
> basic problem, as Ko points out. Oracle is not the only system that
> doesn't like elements in different parts of the document to have the
> same name, even though it is perfectly legal XML. In fact, the
> Microsoft engine that used to be in IE would regularly barf on it,
> although newer versions appear to be OK.
>
> The only thing to take from this is that it is wise to use names
> that are not terribly generic when creating schemas. (or use market
> pressure, but look at the size of these guys!)
Yikes, I can't believe we're so ready to fold in the face of
big-market-cap incompetence. If Oracle really have screwed up
something as basic as namespaces (and notice that you have to go out
of your way to screw them up -- a totally naive, namespace-unaware XML
parser will correctly see x:foo and y:foo as two separate attributes)
then they need to be shamed into fixing it. Please, let's not go
advising people to "work around" such an egregious fault -- especially
when it's impossible anyway, in cases such as these where both the
schemas in use are from external sources and can't be changed.
_/|_ ___________________________________________________________________
/o ) \/ Mike Taylor <[log in to unmask]> http://www.miketaylor.org.uk
)_v__/\ The Unix command to kill processes is not "kill -9". The Unix
command to make a tape archive is not "tar cv". Options are
optional.
|