Hi Jim, Yes, you can handle those in errata. What I suggest is simply requesting an errata template at
https://www.oasis-open.org/resources/tc-admin-requests/work-product-registration-template-request Then use that to draft a simple explanation of the changes. Have the TC approve that along with the fixed schemas as an errata and request publication and public review using
https://www.oasis-open.org/resources/tc-admin-requests/errata-committee-draft-creation-upload-request and
https://www.oasis-open.org/resources/tc-admin-requests/15-day-errata-committee-draft-public-review-request I will handle running those. Then after the public review, the TC can approve the Approved Errata with a Full Majority Vote and we'll take it from there. /chet On Tue, Oct 8, 2013 at 4:51 PM, James E Cabral <
jec@mtgmc.com > wrote: Chet, We have identified the following 3 minor schema issues with the ECF 4.01 Specification (an OASIS Standard): 1. 1 schema should be encoded as UTF-8 rather than UTF-16. 2. 1 element definition is missing a substitutionGroup attribute. 3. 3 import statements refer to old versions of UBL 2.1 that should be updated (see below). Can we deal with these in an errata document? If so, what is the process for creating and publishing errata? Thanks, Jim Cabral MTG Management Consultants, L.L.C.
www.mtgmc.com <../AppData/Roaming/Microsoft/Word/
www.mtgmc.com > (206) 442-5010 Phone (502) 509-4532 Mobile Helping our clients make a difference in the lives of the people they serve. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any computer. From:
legalxml-courtfiling@lists.oasis-open.org [mailto:
legalxml-courtfiling@lists.oasis-open.org ] On Behalf Of Graham, Gary Sent: Tuesday, October 08, 2013 12:43 PM To:
legalxml-courtfiling@lists.oasis-open.org Subject: [legalxml-courtfiling] ECF 4.01 Erratta The specified schemalocation in ECF 4.01 for UBL 2.1 in the three affected messages is not consistent: PaymentMessage: <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" schemaLocation="
http://docs.oasis-open.org/ubl/prd2-UBL-2.1/xsd/common/UBL-CommonAggregateComponents-2.1.xsd "/> FeesCalculationResponseMessage: <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" schemaLocation="
http://docs.oasis-open.org/ubl/cs-UBL-2.0/xsd/common/UBL-CommonAggregateComponents-2.0.xsd "/> PaymentReceiptMessage: <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" schemaLocation="
http://docs.oasis-open.org/ubl/prd2-UBL-2.1/xsd/common/UBL-CommonAggregateComponents-2.1.xsd "/> I presume that PaymentMessage and PaymentReceiptMessage are correct, and It's the FeesCalculationResponseMessage that requires correction. Is there any requirement by UBL to continue to make older draft copies of schema available? If not, how will newer ECF 4.01 implementers get access to these normative schema? -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society
http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 Check your work using the Support Request Submission Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:
http://linkd.in/OASISopen Twitter:
http://twitter.com/OASISopen Facebook:
http://facebook.com/oasis.open