[
Lists Home |
Date Index |
Thread Index
]
Michael,
This is a walk-in-the-park for CAM to handle.
You can see this by inspecting the CAM template in the tutorial ZIP
file publically available from the OASIS CAM area - the Soccer Catalogue Order
example.
Basically you can tailor the structure to the localization needed - driven by a
dynamic context parameter - and essential select the correct instance structure
(and rules) accordingly.
If you use CAM to also drive your online form generation - you have an even
better synchronization - you merely ask people the context variable value up
front - in this case its obvious - please select your country (actually they
could figure it out for you from your URL domain too if they were really
clever...).
Cheers, DW
Quoting Michael Kay <michael.h.kay@ntlworld.com>:
> Incidentally, it happens less often nowadays, but just yesterday I made an
> online purchase from a US supplier who required me to enter a two-letter
> code in the "State" box and a numeric value in the "postal code" box,
> despite the fact that I had entered UK as the country; so of course I lied,
> and they now have my state recorded as "ZZ" and the postal code as 12345.
> They also required a ten-digit phone number. Which reinforces another of my
> arguments: the more validation you do, the more you force people to supply
> incorrect information.
>
> Michael Kay
>
|
