This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Namespace wildcards


In light of all the issues with namespaces that already exist, I feel 
compelled to ask whether the namespace wildcards introduced in XPath 
2.0 <http://www.w3.org/TR/xpath20/#node-tests> are a good idea. This 
enables expressions like this:


<xsl:template match="*:set">
   This matches MathML set elements, SVG set elements, set elements
   from other  namespaces, and set elements from no namespace at all.
</xsl:template>

In other words the local name matters, but the URI doesn't. Do we 
really want to allow this? Do we actually need this? I'm really 
afraid this is going to further confuse developers about namespaces 
and encourage bad practices.
-- 

+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | elharo@metalab.unc.edu | Writer/Programmer |
+-----------------------+------------------------+-------------------+
|          The XML Bible, 2nd Edition (Hungry Minds, 2001)           |
|              http://www.ibiblio.org/xml/books/bible2/              |
|   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
+----------------------------------+---------------------------------+
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
|  Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/     |
+----------------------------------+---------------------------------+

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]