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

Re: Re: Identifying the Top 10 xml Issues.. somethingwith lega

• To: xml-dev@l...
• Subject: Re: Re: Identifying the Top 10 xml Issues.. somethingwith legacy support.. carries business data better..
• From: David Lyon <david.lyon@p...>
• Date: Mon, 24 Jul 2006 19:38:34 +1000
• In-reply-to: <7.0.1.0.0.20060724073352.03efb840@c...>
• References: <44C2A214.2010903@a...> <001a01c6ade2$374c4fc0$6401a8c0@turtle> <7.0.1.0.0.20060723100223.03e64260@c...> <1153684981.30211.276.camel@l...> <7.0.1.0.0.20060723223938.03e6b6e0@c...> <1153693413.30211.289.camel@l...> <7.0.1.0.0.20060723233604.02212b20@c...> <1153706409.30211.325.camel@l...> <7.0.1.0.0.20060724073352.03efb840@c...>

Hi Peter,

>   <Product Item> PLU&="A256" Qty#=5 Rate$=4.56</>
> ..
> 
> Somewhere, I assume, you have to encode the fact that Rate is in 
> dollars of some sort. Otherwise you cannot reliably convert it. 

Actually that is reading too much into it. The $ only defines that it is
a currency type field equivalent to the database column type currency.

I guess if I was in the UK it could be expressed like:

  <Product Item> PLU&="A256" Qty#=5 Rate£=4.56</>

in Germany with english,

  <Product Item> PLU&="A256" Qty#=5 Rateâ?¬=4,56</>

in Japan,

  <Product Item> PLU&="A256" Qty#=5 Rate¥=456</>

other countries that don't have their own character, like Malaysia who
have RM, would most likely end up having to use the $ character. My
small study sample of malaysians say this wouldn't be a problem for
them.

On Windows these days, all the locale information is available via the
windows api. So obtaining it is trivial.

If there is any actual currency conversion, showing conversion rates and
so forth, these would be at a different level. Like the UBL level for
example. We're only doing basic data recording here.

> 
> Therefore you have to have at least a partial schema or ontology CML 
> does this by having an extensible dictionary system and an extensible 
> system of units (which does not but could include currency).

None!

Just some field types that correspond to the sql field types:

 & - Text
 @ - Date
 # - Number
 ! = Integer
 $ = Currency
 ? = Logical
 % = Mime encoded binary data (not yet implemented)

Add ~ to denote an encrypted field.

I've done this all from memory. It becomes rather second nature after a
while. 

Regards

David

• References:
  • Re: [SUMMARY #1] Why is there little usage of XML on the'visible Web'?
    • From: Mitch Amiano <mitch.amiano@a...>
  • RE: [SUMMARY #1] Why is there little usage of XML on the 'visible Web'?
    • From: "Michael Kay" <mike@s...>
  • RE: [SUMMARY #1] Why is there little usage of XML on the 'visible Web'?
    • From: peter murray-rust <pm286@c...>
  • RE: [SUMMARY #1] Why is there little usage of XML on the'visible Web'?
    • From: David Lyon <david.lyon@p...>
  • RE: [SUMMARY #1] Why is there little usage of XML on the 'visible Web'?
    • From: peter murray-rust <pm286@c...>
  • Identifying the Top 10 xml Issues.. something with legacysupport.. carries business data better..
    • From: David Lyon <david.lyon@p...>
  • Re: Identifying the Top 10 xml Issues.. something with legacy support.. carries business data better..
    • From: peter murray-rust <pm286@c...>
  • Re: Re: Identifying the Top 10 xml Issues.. somethingwith legacy support.. carries business data better..
    • From: David Lyon <david.lyon@p...>
  • Re: Re: Identifying the Top 10 xml Issues.. something with legacy support.. carries business data better..
    • From: peter murray-rust <pm286@c...>

• Prev by Date: Re: [SUMMARY #1] Why is there little usage of XML on the 'visible Web'?
• Next by Date: Re: CLAX - Client-side functionality
• Previous by thread: Re: Re: Identifying the Top 10 xml Issues.. something with legacy support.. carries business data better..
• Next by thread: Re: Re: Identifying the Top 10 xml Issues.. something with legacy support.. carries business data better..
• Index(es):
  • Date
  • Thread