ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> xml-dev
xml-dev
Re: [xml-dev] An approach to describing the relationships between units-of-measure
by Emmanuil Batsis (Manos) other posts by this author
Jul 21 2003 12:13PM messages near this date
Re: [xml-dev] An approach to describing the relationships between units-of-measure | Re: [xml-dev] An approach to describing the relationships between units-of-measure
Hi Roger,

Roger L. Costello wrote:
>  Recall that <kilometer> may be considered as a function:
>  
>      kilometer(length(Yangtze)) --> 6340
>  
>  "kilometer maps the length of the Yangtze to 6340."


Does not feel right. For the above to be a meaningfull function, one 
should assume that Yangtze has a length property in some internal 
representation (attribute value) L so that length is

function length()
{
    return this.L;
}

and kilometer is

function kilometer(someNumber)
{
    return toKilometers(someNumber);
}

but parts of the equasion are missing:

1) What kind of unit is used to internally store L?
2) What formula should be used to convert L to kilometers in kilometer()?

Thus, the signature to kilometer indicates a function signature where 
two parameters are passed, one for the number to convert and one for the 
type to convert from:

function kilometer(someNumber, someType)
{
    if(someType.equals("meters"))
       return fromMetersToKilometers(someNumber);
    // rest of elseif statements mapped to expected
    // input types here
}

which is bad, as the kilometer function can only accept a finite number 
of input types at first glance.

IMHO the above practically becomes something like:

L = length(Yangtze)
T = L.type()

kilometer(L,T)

 >  Issue #1: Above I said that:
<snip about="tolerance" eg="(6340 k, 3914 m) in {k, m | k = m * 1.62}"/> 



Cause tolerance should be specified as above. If tolerance is just a 
third parameter, it's power grows weaker while numbers get higher.

Unless tolerance is a float used to construct

k > = m * 1.61 && k >= m * 1.63

from

k, m | k = m * 1.62

as in
tolerance = 0.01

Very interesting approach. Please do give this stuff an online home or 
something.

-- 
Manos Batsis

Netsmart S.A.

Snail mail:
Panepistimiou 58,
10678, Athens, Hellas

URL:    http://www.netsmart.gr
Email:  mbatsis at netsmart dot gr
Tel:    (+30) 210 33 02 608
Fax:    (+30) 210 33 02 658
FOAF:   http://forte.netsmart.gr/foaf/manos_foaf.rdf






-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl> 
Thread:
Roger L. Costello
=?ISO-8859-1?Q?Bill_de_h=D3ra?=
Emmanuil Batsis (Manos)
John Cowan
David Carlisle
Thomas B. Passin

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved