[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: I003: How to reference/use the Unit and Currency code
In bQoS schema, there are many cases use UBL CommonBasicComponents (CBC) element or UnqualifiedDataTypesSchemaModule (UDT) now. This include: <xsd:element name="Amount" type="cbc:AmountType"> <xsd:element name="Duration" type="cbc:DurationMeasureType"> <xsd:element name="Latency" type="cbc:DurationMeasureType"> <xsd:element name="Quantity" type="cbc:BaseQuantityType"> <xsd:element name="Unit" type="cbc:BaseUnitMeasureType"> <xsd:complexType name="PropertyNameType"> <xsd:complexType name="PropertyValueType"> <xsd:element name="StartTime" type="udt:DateTimeType"> Other two schema files also reference many elements from UBL. In other words, including UBL is NOT for just currency code and units. In the feature schema design, more UBL elements will be referenced. This will leverage the existing components and development on UBL, and reduce the complexity of our EERP schema. It is proposed not to change this UBL references. Szu Chang 源郵件: ----------------- 發件人: Hong Zhou eerp_hz@changfeng.org.cn 日期: Wed, 29 Apr 2009 08:40:26 +0200 收件者: eerp_sy@changfeng.org.cn, soa-eerp@lists.oasis-open.org, kyunra@gmail.com 主題: Re: [soa-eerp] New Issue: How to reference/use the Unit and Currency code Issue number: I003 ----- Original Message ----- From: <eerp_sy@changfeng.org.cn> To: <soa-eerp@lists.oasis-open.org> Sent: Sunday, April 26, 2009 11:21 AM Subject: [soa-eerp] New Issue: How to reference/use the Unit and Currency code PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER. The issues coordinators will notify the list when that has occurred. Protocol: bQoS http://www.oasis-open.org/apps/org/workgroup/soa-eerp/download.php/32100/Bus inessQualityOfService-v1.0-spec-wd01.pdf Artifact: schema Type: design Title: How to reference/use the Unit and Currency code Description: This issue was raised during the TC meeting on 4/15/2009 by Bill Cox and Carol. In Use case and example, page 6, embedded - unitCode=each, for example. Bill: UnitCode from UBL. Currency code from there as well. Same as (or derived from) UN-CEFACT. Concerned about pulling in too much of UBL for just currency code and units. Also as much as the reference is interesting, easier to resolve to the value "ea" for readability. End resolution is easier to understand. Agree that supplying a URN is a valuable definition, but simpler when one reads it to see the end result which would be "ea". Carl: Same thing, but one is simpler and easier to read than the other. Need to agree on what put in. Related issues: N/A Proposed Resolution: -------------------------------------------------------------------- mail2web – 從 web 檢查您的電子郵件，網址 http://mail2web.com/ . --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -------------------------------------------------------------------- mail2web – 從 web 檢查您的電子郵件，網址 http://mail2web.com/ .
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]