[
Lists Home |
Date Index |
Thread Index
]
A lot of the time, they don't get that far. It just
breaks and they don't know where to look. Then they
start looking and can't find code to copy that just
works. Then they start asking questions and get answers
back from the hallway like "it works for me" or "never
got that to work; there's a bug somewhere". This
takes time and after some time, they type it all back
in and maybe it works, and if it does, they don't find
out why.
Dare, namespaces ARE a problem. If you haven't figured
that out, you aren't dealing with them in production or
you aren't facing up to the realities of production users
who aren't "in the know". Considering the dominance of
your products on the desktop, we are here to tell you
that it is your problem.
len
-----Original Message-----
From: Mike Champion [mailto:mc@xegesis.org]
They don't find it a teensy bit confusing that a namespace declaration looks
and smells like an attribute in XML syntax and the DOM, but the Infoset (and SAX?)
says that declarations aren't in the attribute list for an element, and
XPath treats the in-scope namespace as a non-attribute property of
an element and doesn't (IIRC) represent the declaration at all?
They aren't confused when HTTP says that various capitalizations of
the same URI retrieve the same representation of a resource, but that
XML namespace processors consider them distinct?
Your users are a lot smarter than I am!
|
