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

Re: Please no UOM (was Re: maps)

Re:  Please no UOM (was Re: maps)
Maybe there is an 80/20 point in there somewhere. It seems like breaking
complex values into simpler ones makes good sense lexically. Also, it makes
good sense in a value space. Combining these also seems to make good sense.
So the question is what are the limits to defining value. What if you drew
the line at conversion between types? This way, defining a value space for a
"type" or "unit" of a type would be useful for sorting or comparison or
other operations only of that type. Conversion or comparison between types
would be the 20% that would be avoided. Again, theoretically it sounds good,
but I don't know how useful this is in markup-land. Once you get to a type
like dates you need co-occurrence constraints between units again... (e.g.
if Feb then max days = 28 unless leap year...)-- then it all seems like a
bad idea.

Jeff Rafter
Defined Systems
XML Development and Developer Web Hosting


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.