OASIS Universal Business Language (UBL) TC

I understood no more schema changes were going to be made, yet with today's export of the model from the database, a number of sample instances are all of a sudden invalid. The report is below. I also had to hack the exported models with the following changes in order to make for a clean production pass: - "customs identification" -> "customs declaration" in the definition on row 552 - "weekday" -> "day of the week" in the definitions related to "WeekDayCode" - rows 1698, 1697 and 2315 - row 107: "Prize Description " -> "Prize" and "Description" in property term components - row 729: "Energy Water Supply. Energy Water_ Correction. Consumption Correction" -> "Energy Water Supply. Energy Water_ Consumption Correction. Consumption Correction" - row 1495: "Procurement Project. Budget Amount. Requested Tender Total" -> "Procurement Project. Requested Tender Total" Again, I'm surprised to see changes that were not in the previous export from the database. Perhaps this is indicative of something in the database that has been overlooked until it was "restarted" today (I was unable to produce the preview draft package on the weekend because of a "server maintenance" message). I don't know. I'm not going to let this stop me today from creating a preview draft package, but these are issues that must be fixed before I create the final draft package. I don't want to be hacking the exported files in order to make them work. I'm not quite finished preparing the package, so I'll post more if there are more issues that I find. But I am making progress. . . . . . . . . . Ken ############################################################ Validating ../xml/UBL-ForwardingInstructions-2.0-Example-International.xml ############################################################ ============== Phase 1: XSD schema validation ============== Attempting well-formed, namespace-aware parse Error:file:///Users/admin/t/UBL-SGTG-20130128-1740z/xml/UBL-ForwardingInstructions-2.0-Example-International.xml:161:32:cvc-complex-type.2.4.a: Invalid content was found starting with element 'cac:FreightAllowanceCharge'. One of '{"urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":PaymentTerms, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":CollectPaymentTerms}' is expected. Parse succeeded (0.20) with 1 error and no warnings. ############################################################ Validating ../xml/UBL-TransportExecutionPlan-2.1-Example.xml ############################################################ ============== Phase 1: XSD schema validation ============== Attempting well-formed, namespace-aware parse Error:file:///Users/admin/t/UBL-SGTG-20130128-1740z/xml/UBL-TransportExecutionPlan-2.1-Example.xml:253:34:cvc-complex-type.2.4.a: Invalid content was found starting with element 'cac:MainCarriageShipmentStage'. One of '{"urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":TransitCountry, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":TransportContract, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":TransportEvent, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":OriginalDespatchTransportationService, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":FinalDeliveryTransportationService, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":DeliveryTerms, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":PaymentTerms, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":CollectPaymentTerms}' is expected. Parse succeeded (0.31) with 1 error and no warnings. ############################################################ Validating ../xml/UBL-TransportExecutionPlanRequest-2.1-Example.xml ############################################################ ============== Phase 1: XSD schema validation ============== Attempting well-formed, namespace-aware parse Error:file:///Users/admin/t/UBL-SGTG-20130128-1740z/xml/UBL-TransportExecutionPlanRequest-2.1-Example.xml:253:30:cvc-complex-type.2.4.a: Invalid content was found starting with element 'cac:TransportHandlingUnit'. One of '{"urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":TransitCountry, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":TransportContract, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":TransportEvent, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":OriginalDespatchTransportationService, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":FinalDeliveryTransportationService, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":DeliveryTerms, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":PaymentTerms, "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":CollectPaymentTerms}' is expected. Parse succeeded (0.26) with 1 error and no warnings. ############################################################ Validating ../xml/UBL-Waybill-2.0-Example-International.xml ############################################################ ============== Phase 1: XSD schema validation ============== Attempting well-formed, namespace-aware parse Error:file:///Users/admin/t/UBL-SGTG-20130128-1740z/xml/UBL-Waybill-2.0-Example-International.xml:232:32:cvc-complex-type.2.4.a: Invalid content was found starting with element 'cac:FreightAllowanceCharge'. One of '{"urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2":CollectPaymentTerms}' is expected. -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal

Already I have found another piece of evidence that something may be wrong in the database. Here are the BIE counts from three weeks ago and from today: - ABIE (290), BBIE (2253), ASBIE (1570) 20130108-0140z - ABIE (289), BBIE (2243), ASBIE (1564) 20130128-1740z Arianna, could you please analyze these numbers and talk with the database administrators about any discrepancies? Thank you. . . . . . . . . . Ken At 2013-01-28 13:05 -0500, I wrote: I understood no more schema changes were going to be made... ... Perhaps this is indicative of something in the database that has been overlooked until it was "restarted" today (I was unable to produce the preview draft package on the weekend because of a "server maintenance" message). I don't know. -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal

And it appears that the problem I reported at the end of December: "Evidence. Name. Text" ... has returned to the database today. As has the data type qualification "Tenderer Role Code" which had been removed before. This is something else reported in today's database that needs to be repaired: "Tendering Terms/Additional/Conditions" (2) Tendering Terms. Additional_ Conditions. Indicator Tendering Terms. Additional_ Conditions. Text And, it appears that the Consignment definition in today's database is not backward compatible with the UBL 2.0 Consignment definition. This appears to explain why the sample instances all of a sudden stopped working. Two of the definitions in today's database have non-ASCII characters in them: "Item Management Profile. Target Service Percent. Percent" and "Sales Item. Activity Property". I don't know if these are new or old. I think this is all evidence that our model database is corrupted. It needs to be repaired before we can start the public review. Meanwhile, I'm going to still make up a preview distribution package today so that other things can be reviewed, but it isn't a package that is going to be very robust. . . . . . . . . Ken At 2013-01-28 13:09 -0500, I wrote: Already I have found another piece of evidence that something may be wrong in the database. Here are the BIE counts from three weeks ago and from today: - ABIE (290), BBIE (2253), ASBIE (1570) 20130108-0140z - ABIE (289), BBIE (2243), ASBIE (1564) 20130128-1740z Arianna, could you please analyze these numbers and talk with the database administrators about any discrepancies? Thank you. . . . . . . . . . Ken At 2013-01-28 13:05 -0500, I wrote: I understood no more schema changes were going to be made... ... Perhaps this is indicative of something in the database that has been overlooked until it was "restarted" today (I was unable to produce the preview draft package on the weekend because of a "server maintenance" message). I don't know. -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal

At 2013-01-28 14:02 -0500, I wrote: Two of the definitions in today's database have non-ASCII characters in them: "Item Management Profile. Target Service Percent. Percent" and "Sales Item. Activity Property". I don't know if these are new or old. I have determined these non-ASCII characters were introduced by the new definitions files and are not found in the database. They need to be fixed there. For now I have hacked these. . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal