• To: "Dare Obasanjo" <dareo@m...>
• Subject: Re: Question for the XPath and DOM folks
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Sat, 20 Jul 2002 14:31:16 -0600
• Cc: "Garland foster" <garland_foster@s...>, xml-dev@l...
• In-reply-to: Message from "Dare Obasanjo" <dareo@m...> of "Sat, 20 Jul 2002 13:15:46 PDT." <8BD7226E07DDFF49AF5EF4030ACE0B7E06621E06@r...>
• Sender: uche.ogbuji@f...

> Thanks for finding the pointer in the WD. This is what our .NET framework implementation does and I was wondering if I could find justification for it by querying the XPath/DOM heads, little did I know it was actually officially specced. 

Well, it's still a WD.  I would simply refuse to implement the DOM L3 XPath 
spec as currently written.  Perhaps it can be "fixed".


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Track chair, XML/Web Services One Boston: http://www.xmlconference.com/
The many heads of XML modeling - http://adtmag.com/article.asp?id=6393
Will XML live up to its promise? - http://www-106.ibm.com/developerworks/xml/li
brary/x-think11.html

• Follow-Ups:
  • Re: Question for the XPath and DOM folks
    • From: "Garland foster" <garland_foster@s...>

• References:
  • RE: Question for the XPath and DOM folks
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: Re: Question for the XPath and DOM folks
• Next by Date: Re: Question for the XPath and DOM folks
• Previous by thread: RE: Question for the XPath and DOM folks
• Next by thread: Re: Question for the XPath and DOM folks
• Index(es):
  • Date
  • Thread