Comments on: why elements in XML can’t be numbers http://uucode.com/blog/2005/04/11/why-elements-in-xml-cant-be-numbers/ advocating olpa's open source developments Sat, 06 Sep 2008 01:03:36 +0000 http://wordpress.org/?v=2.2.3 By: olpa http://uucode.com/blog/2005/04/11/why-elements-in-xml-cant-be-numbers/#comment-15577 olpa Sun, 03 Aug 2008 02:48:08 +0000 http://uucode.com/blog/2005/04/11/why-elements-in-xml-cant-be-numbers/#comment-15577 Because it breaks the semantics of XPath. An expression inside brackets is evaluated as XPath and casted to boolean. The first XPath is a valid XPath: expression in the brackets evaluated to a string "1", which in turn casted to true. You are not allowed to interpret "1" as a child name. Because it breaks the semantics of XPath. An expression inside brackets is evaluated as XPath and casted to boolean. The first XPath is a valid XPath: expression in the brackets evaluated to a string “1″, which in turn casted to true. You are not allowed to interpret “1″ as a child name.

]]> By: Bruno http://uucode.com/blog/2005/04/11/why-elements-in-xml-cant-be-numbers/#comment-15576 Bruno Fri, 01 Aug 2008 14:24:00 +0000 http://uucode.com/blog/2005/04/11/why-elements-in-xml-cant-be-numbers/#comment-15576 Well, that's a good explanation... but shouldn't the element names be within "'"? So, the path should be something like: /World/Widgets['1'] : for the child element /World/Widgets[1] : for the first widget Well, that’s a good explanation… but shouldn’t the element names be within “‘”?

So, the path should be something like:

/World/Widgets[’1′] : for the child element
/World/Widgets[1] : for the first widget

]]>