>
> The best answer is to do everything using XML-based processing  
> languages
> (XSLT and XQuery) rather than spending 75% of your programming effort
> converting your data between one type system and another.

When I first read Roger's post, the first thing I thought about was  
XML Schema processors are fine.

But, XQuery processors differences is closer to the analogy of browser  
wars. Not the W3 spec defined aspects, just the things that most  
people use them for it seems. (I am thinking mostly of the XML  
database vendor's approach to using XQuery as a webapp templating  
language)

I wonder if anybody in the real world actually create cross processor  
XQuery code.

-Rob

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php