OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Enlightenment via avoiding the T-word

 From: "Christian Nentwich" <c.nentwich@cs.ucl.ac.uk>
 > >   <xsl:template match="x:name">
> >      <xsl:if select="parent::x:person">
> >          <!-- oops I need this extra test because name is reused--
> >         those darned people at x:: namespace keep on adding
> >         new local elements and our code is written to just use
> >         the markup. Why cannot they just use vanilla XML.... -->
> Isn't this cheating slightly ? If you work based on a context, you would
> quite likely call a template
> instead of matching one. I am with Nicolas here in that I think it's
> quite unlikely that you want to process name without being in the
> process of processing (sorry :) a particular parent node.

Either way doesn't change the point.  If you have a script written
(using names not vapor-PSVI)
under the assumption that there are no local types (or, at least, 
a known set of local types, the others being global, and the
local type not being a compatible restriction of the global type), then
introducing local types forces you to do some more programming
to fix it.  It is not robust.

The reuse of the element may cause some failure, but it is just
as likely to introduce spurious data.  

Contrast this with adding a new global--per-namespace name.
Your script will already have handled this: either strip or fail, probably.

Rick Jelliffe