I am starting a new project, which includes the use of heavy xml and schemes on several platforms (windows, windows mobile, Iphone, Ipad, etc., which have yet to be opened!). This xml platform should be able to exchange dates from around the world, as our product is currently being implemented in Australia, as well as in Canada and the United States.
Temporary data is usually of the same type, which causes most problems between different platforms and languages.
Should I trust the built-in date type? or I have to break each date into its subsections, for example. elements or attributes within hours, minutes, seconds, day, month, year, time zone, etc.
I would like to understand pro and con for all of the above options.
EDIT: added 2 questions for clarity
if you are using the simple xml date type, how can I guarantee that all clients correctly write the date in this format?
I know .net I can use DateTime.ToUniversalTime (), do other languages have an equivalent, or is it a dll for writing XML that control the conversion to international time?
Thanks Pete
source
share