And presumably take the same approach when we generate the RDF - which is where the conversation began :)
*Lloyd McKenzie*, P.Eng. Senior Consultant, Information Technology Services Gevity Consulting Inc. E: lmcken...@gevityinc.com M: +1 587-334-1110 <1-587-334-1110> W: gevityinc.com *GEVITY**Informatics for a healthier world * CONFIDENTIALITY – This communication is confidential and for the exclusive use of its intended recipients. If you have received this communication by error, please notify the sender and delete the message without copying or disclosing it*.* NOTE: Unless explicitly stated otherwise, the opinions and positions expressed in this e-mail do not necessarily reflect those of my employer, my clients nor the organizations with whom I hold governance positions On Tue, Aug 4, 2015 at 7:39 AM, Grahame Grieve < grah...@healthintersections.com.au> wrote: > yes. It appears that for some tool stacks, the code generation schemas > might need to use xs:string instead of xs:decimal - but not others. So I > think that we should make a note about this in the code generation schemas. > > Grahame > > > On Tue, Aug 4, 2015 at 11:36 PM, Lloyd McKenzie <ll...@lmckenzie.com> > wrote: > >> I think the question is whether someone using code that's generated from >> the schema (as opposed to a reference implementation) is going to be in >> trouble because we use the xs:decimal type. >> >> *Lloyd McKenzie*, P.Eng. >> Senior Consultant, Information Technology Services >> Gevity Consulting Inc. >> >> E: lmcken...@gevityinc.com >> M: +1 587-334-1110 <1-587-334-1110> >> W: gevityinc.com >> >> >> *GEVITY**Informatics for a healthier world * >> >> CONFIDENTIALITY – This communication is confidential and for the >> exclusive use of its intended recipients. If you have received this >> communication by error, please notify the sender and delete the message >> without copying or disclosing it*.* >> >> NOTE: Unless explicitly stated otherwise, the opinions and positions >> expressed in this e-mail do not necessarily reflect those of my employer, >> my clients nor the organizations with whom I hold governance positions >> >> On Tue, Aug 4, 2015 at 4:00 AM, James Agnew <jamesag...@gmail.com> wrote: >> >>> On the Java side, parsing and encoding of FHIR primitives into XML is >>> all hand rolled, so no xs:decimal. I'm not sure what the concern is, but if >>> there are any specific areas of concern I'm always hunting for new unit >>> tests... >>> >>> James >>> >>> On Tue, Aug 4, 2015 at 2:15 AM, Paul A. Knapp <pkn...@pknapp.com> wrote: >>> >>>> Are either the Java or C# implementations using standard xml >>>> frameworks? Ones which would implement xs:decimal? (I think that is the >>>> concern.) >>>> >>>> Paul >>>> >>>> At 08:55 PM 2015-08-03, David Booth wrote: >>>> >>>> Content-Transfer-Encoding: 7bit >>>> >>>> Regarding the above action, and last week's discussion of xsd:decimal, >>>> Lloyd reports: "Java uses BigDecimal - so full retention of precision. C# >>>> uses decimal, which also retains precision." >>>> >>>> David Booth >>>> >>>> >>>> *********************************************************************************** >>>> Manage subscriptions - http://www.HL7.org/listservice >>>> <http://www.hl7.org/listservice> >>>> View archives - http://lists.HL7.org/read/?forum=its >>>> <http://lists.hl7.org/read/?forum=its> >>>> Unsubscribe - >>>> http://www.HL7.org/tools/unsubscribe.cfm?email=pkn...@pknapp.com&list=its >>>> <http://www.hl7.org/tools/unsubscribe.cfm?email=pkn...@pknapp.com&list=its> >>>> Terms of use - >>>> http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules >>>> <http://www.hl7.org/myhl7/managelistservs.cfm?ref=nav#listrules> >>>> >>>> >>>> *Paul Knapp *President >>>> Knapp Consulting Inc. >>>> www.pknapp.com >>>> >>>> Tel: +1 604 987-3313 >>>> Fax: +1 604 987-3305 >>>> Cel: +1 604 250-1915 >>>> KSA: +966 56 787 0341 >>>> Skype: paulknapp >>>> >>>> HL7 International ( www.HL7.org <http://www.hl7.org/> ) >>>> Co-Chair: Implementable Technology Specifications WG; Financial >>>> Management WG; Foundation and Technology SD. >>>> Member: FHIR Management Group; Technical Steering Committee; US >>>> Realm Steering Committee; Architecture Review Board >>>> EACOE Certified Enterprise Architect www.EACOE. >>>> <http://www.eacoe.org/> org >>>> >>>> <http://www.eacoe.org/>The information in this communication, >>>> including any attached documentation, is intended only for the person or >>>> entity to which it is addressed, and may contain confidential, personal, >>>> and/or privileged information. Any unauthorized disclosure, copying, or >>>> taking action on the contents is strictly prohibited. If you have received >>>> this message in error, please contact us immediately so we may correct our >>>> records. Thank you. >>>> >>>> >>>> *********************************************************************************** >>>> Manage your subscriptions <http://www.HL7.org/listservice> | View the >>>> archives <http://lists.HL7.org/read/?forum=its> | Unsubscribe >>>> <http://www.HL7.org/tools/unsubscribe.cfm?email=jamesag...@gmail.com&list=its> >>>> | Terms of use >>>> <http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules> >>>> >>>> >>> >>> *********************************************************************************** >>> Manage your subscriptions <http://www.HL7.org/listservice> | View the >>> archives <http://lists.HL7.org/read/?forum=its> | Unsubscribe >>> <http://www.HL7.org/tools/unsubscribe.cfm?email=ll...@lmckenzie.com&list=its> >>> | Terms of use >>> <http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules> >>> >> >> >> *********************************************************************************** >> Manage your subscriptions <http://www.HL7.org/listservice> | View the >> archives <http://lists.HL7.org/read/?forum=its> | Unsubscribe >> <http://www.HL7.org/tools/unsubscribe.cfm?email=grah...@healthintersections.com.au&list=its> >> | Terms of use >> <http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules> >> > > > > -- > ----- > http://www.healthintersections.com.au / grah...@healthintersections.com.au > / +61 411 867 065 >
