[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Is Anyone Interested In XPath 2.0 Use Cases or Requirement

• To: "Dare Obasanjo" <dareo@m...>
• Subject: Re: Is Anyone Interested In XPath 2.0 Use Cases or Requirements?
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Sat, 06 Jul 2002 23:57:38 -0600
• Cc: xml-dev@l...
• In-reply-to: Message from "Dare Obasanjo" <dareo@m...> of "Sat, 06 Jul 2002 22:14:51 PDT." <8BD7226E07DDFF49AF5EF4030ACE0B7E06621DAF@r...>
• Sender: uche.ogbuji@f...

> -----Original Message----- 
> From: Uche Ogbuji [mailto:uche.ogbuji@f...] 
> Sent: Sat 7/6/2002 12:36 PM 
> To: Dare Obasanjo 
> Cc: xml-dev@l... 
> Subject: Re:  Is Anyone Interested In XPath 2.0 Use Cases or Requirements?
> 
> >> 4.) Lack of value comparators for nodesets
> >I'm not clear on what you mean here, and a brief read of your full article didn't help me.  Can you clarify?  An example, perhaps?
> 
> There is no mechanism to perform comparisons of node sets for equality in the same manner one would for mathematical sets. For instance I can't say a node-set containing (A, B, C) is equivalent to a nodeset containing (B, C, A)


I see, and I concur.  Some sort of is-equivalent() function would be nice for node sets.

Of course the big question would be whether node identity or, say, node text comparison after c14n, would be the criteria for checking nodes within the set.  And whether there should be an ordering imposed before the comparison (and what to do when the spec provides for no normative ordering, e.g. if document() is used).


> >Besides dates, which are provided for in EXSLT, can you say whet sorts of practical problems you've had people report that caused them to >think they needed operations on other schema types?  Or do they just think that because their schema has types, that XPath ought to be >able to do funky things with those types?
> 
> Dates are probably the only types requested with any sort of frequency to establish a trend. Funny enough, adding XSD dates may not satisfy some of our end users who expect to be able to use dates in the format from regular usage (e.g. MM-DD-YYYY or DD/MM/YYYY) and may balk at the ISO 8601 format used by XSD (YYYY-MM-DD) 

I do think that a good date library is the primary thing needed.  I think we differ only in that you'd like to see this as just one aspect of WXS types support, and that I'm happy just to see a nice plug-in library for dates that are independent of WXS (but can handle the needs introduced by WXS date types).


-- 
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/library/x-think11.html

• References:
  • RE: Is Anyone Interested In XPath 2.0 Use Cases or Requirements?
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: Re: XQuery and DTD/Schema?
• Next by Date: Re: XQuery and DTD/Schema?
• Previous by thread: RE: Is Anyone Interested In XPath 2.0 Use Cases or Requirements?
• Next by thread: Re: Is Anyone Interested In XPath 2.0 Use Cases or Requirements?
• Index(es):
  • Date
  • Thread