OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Draft 2 UBL 2.1 Schema Generation Task Group strategy document


Please forgive my tardy delivery on this package, 
but we've started our family vacation and I was 
unable to devote much time to the last steps 
needed after the end of our week in Montréal.

I believe this package has addressed all of the issues brought up in Montréal:

   http://www.oasis-open.org/committees/document.php?document_id=33945

Of note, the validation processes now 
successfully validate code lists for both UBL 2.0 
and UBL 2.1 in the one second-pass value 
validation task.  The documentation for value 
validation and code list qualifications is now 
encapsulated in the UBL-QualifiedDataTypes-2.1.html report.

Yildiray, because Tony has given me the 2008 code 
list for currency in genericode for use in UBL 
2.1, and UBL 2.0 uses the 2001 code list for 
currency, this demonstration environment now 
incorporates the validation of both "TRL" and 
"TRY" both independently and in the presence of 
the respective instance-level metadata.  To 
restate the requirement as I understand it, a UBL 
2.1 system needs to support the following five 
use cases, where the first four need to succeed:

  [1]  <cbc:TaxAmount currencyID="TRL">17.50</cbc:TaxAmount>
  [2]  <cbc:TaxAmount currencyID="TRY">17.50</cbc:TaxAmount>
  [3]  <cbc:TaxAmount currencyID="TRL"
          currencyCodeListVersionID="2001">17.50</cbc:TaxAmount>
  [4]  <cbc:TaxAmount currencyID="TRY"
          currencyCodeListVersionID="2008">17.50</cbc:TaxAmount>

... while at the same time this fifth invalid combination must be rejected:

  [5]  <cbc:TaxAmount currencyID="TRL"
          currencyCodeListVersionID="2008">17.50</cbc:TaxAmount>

... and I believe this is the case for the test environment I've prepared.

Note that the above bona fide user requirement 
scenario cannot be supported using pure W3C 
Schema 1.0 approaches.  I believe, but I have not 
yet tested it, that W3C Schema 1.1 may be viable 
to implement this scenario because of conditional 
type assignment, but I have not researched this.

So I think we are all set for UBL 2.1 when we get the final spreadsheets.

Would committee members please remember to get 
Tony the latest versions of all of the UBL 2.0 
code lists they are responsible for?  You can see 
the list of qualifications by code lists in the 
UBL-QualifiedDataTypes-2.1.html report in the ZIP 
to remember what is qualified in UBL 2.0.

And you can see the union of UBL 2.0 and UBL 2.1 
code lists for the lists Tony has already given me.

I look forward to your feedback.

. . . . . . . . . . . . . Ken

--
Interested in these classes?  http://www.CraneSoftwrights.com/o/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]