I vote for option 2. Cheers, Rong
2009/1/29 Thilo Schuler <thilo.schuler at gmail.com>: > Hi > > I also opt for option 2. > > The '.' instead of ',' is a common issue for German XML users. Thus leaving > the '.' as decimal separator would be more consistent. If really needed a > conversion could be done on the rendering/view side. Although in todays > anglophile world most people are used to the '.' decimal separator anyways. > > Cheers, Thilo > > On Thu, Jan 29, 2009 at 6:52 AM, Heath Frankel > <heath.frankel at oceaninformatics.com> wrote: >> >> Hi all, >> >> Our.NET implementation of the openEHR RM DV_QUANTITY is dependent on the >> regional setting on the system, for example a magnitude of 1.0 on a system >> with 'en' regional settings will be represented as 1,0 on a system with 'de' >> regional settings. >> >> >> >> Thilo has recently identified an issue where our serialisation of these RM >> objects when in the 'de' culture produces an XML instance of DV_QUNATITY as >> follows: >> >> >> >> <value xsi:type="DV_QUANTITY"> >> >> <magnitude>1,2</magnitude> >> >> <units>mm</units> >> >> </value> >> >> >> >> When validated against the openEHR XML schema, this is not valid because >> DV_QUANTITY.magnitude is declared as type="xs:double". >> >> >> >> We can resolve this issue in our implementation, but the question is if >> openEHR wants to support DV_QUANTITY.magnitude representations containing a >> comma. >> >> >> >> The openEHR data types specifications indicates that assumes built-in >> primitive types such as Character, Boolean, Integer and Double based on ISO >> 11404 within an implementation environment such as Java, .NET. and XML. >> This was the rational of using the xs:double type in the openEHR XML Schema >> for DV_QUANTITY.magnitude. >> >> >> >> Having said that, the openEHR XML schema has implemented its own ISO8601_x >> assumed Date/Time types because the built-in XML Schema DateTime type does >> not support the openEHR assumed ISO8601 capability of partial date/time, nor >> the separate Date and Time types. The ISO8601_x types implemented in the >> openEHR XML Schema does support both period (.) and comma (,) for fractional >> seconds. >> >> >> >> I have spoken to Tom about this and we feel that openEHR has two options: >> >> 1) Update the XML Schema to implement an culture aware double type to >> be used in DV_QUANTITY.magnitude. This change would not invalidate any >> existing data instances but would make instances based on that new schema >> invalid against previous revisions. >> >> 2) Leave the XML Schema as is and make culture-aware serialisation >> and rending responsible for converting the representation of >> DV_QUNATITY.magnitude into the local cultures representation. >> >> >> >> Can anyone suggest another option? >> >> >> >> It is Thomas and my preference for option 2. >> >> >> >> Are there anyone from the regions that use the comma representation of >> decimal points that feel that option 1 is necessary? >> >> >> >> Regards >> >> >> >> Heath >> >> >> >> Heath Frankel >> Product Development Manager >> >> Ocean Informatics >> >> Ground Floor, 64 Hindmarsh Square >> >> Adelaide, SA, 5000 >> >> Australia >> >> >> >> ph: +61 (0)8 8223 3075 >> >> mb: +61 (0)412 030 741 >> email: heath.frankel at oceaninformatics.com >> >> >> >> _______________________________________________ >> openEHR-implementers mailing list >> openEHR-implementers at openehr.org >> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-implementers > > > > -- > Thilo Schuler > Morgenrainstrasse 9 > CH-8620 Wetzikon > > Festnetz: +41 (0) 43 49 707 85 > Mobil: +41 (0) 78 90 75 490 > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >
