[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes of Pacific UBL TC call 20 July 2016 01:00UTC - voting meeting
Minutes of Pacific UBL TC call 20 July 2016 01:00UTC - voting meeting ATTENDANCE Kenneth Bengtsson G. Ken Holman (convener) Tim McGrath Andy Schoka REFERENCING THE SPECIFICATION - the following should be used as a specific citation: OASIS Universal Business Language (UBL) v2.1 (ISO/IEC 19845:2015) - the following would be used for a general (any version) citation: OASIS UBL (ISO/IEC 19845) - the canonical documents are available in the OASIS repository: http://docs.oasis-open.org/ubl/os-UBL-2.1/ - the ISO/IEC catalogue entry is found at: http://www.iso.org/iso/catalogue_detail.htm?csnumber=66370 - the ISO/IEC document and attachments are found at: http://standards.iso.org/ittf/PubliclyAvailableStandards/ STANDING ITEMS Additions to events calendar: http://ubl.xml.org/events - 28th Forum for UN/CEFACT Bangkok, Thailand - 26 to 30 September 2016 http://www.unece.org/28thuncefactforum - TC204 meeting Auckland, New Zealand - 2 to 7 October 2016 http://www.itsnz.org/events.html Review of Atlantic call minutes https://lists.oasis-open.org/archives/ubl/201607/msg00004.html Review of Pacific call minutes https://lists.oasis-open.org/archives/ubl/201607/msg00001.html Membership status review <https://www.oasis-open.org/policies-guidelines/tc-process#membership>https://www.oasis-open.org/policies-guidelines/tc-process#membership https://www.oasis-open.org/committees/membership.php?wg_abbrev=ubl <https://www.oasis-open.org/apps/org/workgroup/ubl/members/roster.php?num_items=80>https://www.oasis-open.org/apps/org/workgroup/ubl/members/roster.php?num_items=80 - voting status is determined by the following: - existing voting members must not miss two consecutive meetings to maintain voting status - non-voting members must attend two consecutive meetings to obtain voting status - members formally on leave by prior request must not attend and their voting status is not impacted - committee officers (alphabetical): - Jon Bosak (secretary) - G. Ken Holman (co-chair) - Tim McGrath (co-chair) - current UBL TC voting member list (alphabetical) and relationships: - Oriol Bausa - Member OASIS BDXR, Member OASIS ebXML, Editor TC434 Validation - Kenneth Bengtsson - Chair OASIS BDXR, Member OASIS ebXML - Kees Duvekot - Member OASIS BDXR - G. Ken Holman - Member OASIS BDXR, CA Member JTC 1/SC32, CA Expert UN/CEFACT - Ole Madsen - DK Member CEN/TC440, CEN/TC440 Liaison JTC 1/SC 32 - Tim McGrath - EESPA Observer CEN/TC434, AU Expert UN/CEFACT - Andy Schoka - Member ISO/TC204, US Member JTC 1/SC 32 - active non-voting member - Roberto Cisternino - members approaching losing voting status: - Kees Duvekot UBL 2.2 - the initial suggestion period for UBL 2.2 is now closed - the TC is now expecting each of the Transportation, Pre-award and Post-award subcommittees to make the recommendations for 2.2 additions to be agreed upon by the TC; this is done by way of a JIRA ticket - Andy managing requirements for transportation documents - Kees managing requirements for post-award documents - Ole managing requirements for pre-award documents - Roberto managing requirements for party information document - more than a business card and less than a company dossier - the initial master UBL 2.2 spreadsheet is found here: https://docs.google.com/spreadsheets/d/1qXmbTu4aNak7s7yxHeKxj5mmfiIBj_CQqq7rJT3Vizg/view - the latest working draft release of UBL 2.2 using only the 2.1 model: https://lists.oasis-open.org/archives/ubl/201606/msg00031.html - documentation requirements - a Google text document of the hub document is here: https://docs.google.com/document/d/1yv2y6EQkHhGjjgIpwBNpWdxi5tDY3l0-NwkwDM0MpYg/edit - committee members have been given permissions to edit the document - Ken will try to move the content into XML when the edits are complete - removing hanging paragraphs by adding introductory sections - disambiguating section titles - each submitter of new documents and objects must consider what additional documentation is needed in the UBL hub document: - general business rules - sections 2.1.x - business objects - sections 2.x - party roles - section 2.19 - example instances - sections 3.1.x - do we need to create RELAX-NG schemas for UBL 2.2? - Ken can poll the UBL-Dev mail list to ask the community there - Tim observed that what we could do is just point people to the tool that creates RELAX-NG from W3C Schema: https://github.com/relaxng/jing-trang - do we need to create ASN.1 and UML deliverables for UBL 2.2? - ASN.1 still important for user communities such as TC204 - UML is still important, but it is not an automated process nor trivial - Ken has questions regarding property term possessive noun and property term primary noun used in the tendering business objects, as an example, those found in the ABIE TenderedProject - will fix these as encountered - note that the property term is comprised of the possessive noun and the primary noun in such a manner that the primary noun should be the noun of what the object is, and the possessive noun should be such that the natural language is as adding the possessive "apostrophe s" - example: "Tender Amount" - the primary noun is "Amount" and the possessive noun is "Tender" as if one would say "the tender's amount" - note also that the property term should not rely on the reader knowing representation term to understand what is the business object - example: "Tender Amount" - it would be inappropriate for the primary noun to be "tender" even when the element name becomes "TenderAmount" because one would need to know the representation term is "Amount" - when the element name is derived and the primary noun is equal to the representation term, the duplication doesn't show up in the name - please review all JIRA tickets and comment and/or act where necessary: https://issues.oasis-open.org/issues/?filter=12972 - all of the issues are to be closed by September 1, 2016 in order to create the first committee specification draft and public review draft - please remember to document your actions on the ticket and then assign the ticket to the next person (usually Ken) to deal with the ticket, as others won't know what is being done UBL-28 Open Unresolved - Support for Verified Gross Mass - Ole has posted on this UBL-27 Open Unresolved - Code lists for UBL 2.2 UBL-26 Open Unresolved - Handle Encryption - Ole will update Pre-award spreadsheet with a new BBIE for the coded item UBL-25 Open Unresolved - Pre-award SC put the changes forward to the TC - changes for 2.2. discussed with Oriol, Tim will focus on generalizing the EU terminology and aligning, where possible, with existing structures - cleaning up naming components UBL-24 Applied - Comment submission re: document version history - propose we close this now: https://issues.oasis-open.org/browse/UBL-24 - AGREED (pending Atlantic call) - unanimous by those present UBL-23 Applied - Comment submission re: freight credit note - propose we close this now: https://issues.oasis-open.org/browse/UBL-23 - AGREED (pending Atlantic call) - unanimous by those present UBL-22 Applied - Comment submission from Norway re: tender receipt - propose we close this now: https://issues.oasis-open.org/browse/UBL-22 - AGREED (pending Atlantic call) - unanimous by those presentUBL-21 Open Unresolved - Pre-award documents will need to engage the language code list in the second-pass validation
- Oriol will update Pre-award spreadsheet with "Language" as qualified data type for the BBIEs affected - the ISO code list for languages is suitable to be engaged for the default second-pass validation UBL-19 Open Unresolved - Minor changes based on applying new NDR to UBL 2.1 - changes made in the lab documents and will be available in next draftUBL-18 Open Unresolved - Align CreditNote with Invoice document around withholding tax information
UBL-16 Open Unresolved - Allow for requested document distribution in Waybill and Bill of Lading document types
UBL-7 Open Unresolved - Adding OrderChangeDocumentReference to OrderResponse/OrderResponseSimple documents
UBL-2 Open Unresolved - Documents for party information exchange UBL-1 Open Unresolved - Documents for integrating supply chain Naming and Design Rules - Business Document Naming and Design Rules Version 1.0 Committee Specification Draft 02 vote held and passed, CS01 being prepared:<https://issues.oasis-open.org/browse/TCADMIN-2405>https://issues.oasis-open.org/browse/TCADMIN-2405
- UBL Naming and Design Rules Version 3.0 Committee Note 01 is now ready to be accepted in order to be published: - non-material changes to the last public review: - proper date for the reference to BD-NDR Committee Specification - proper release information - aligned annexes to BD-NDR annexes (former Annex C had been removed) - vote: Does the committee agree to accept as final the following as UBL Naming and Design Rules Version 3.0 Committee Note 01 and request TC Administration to publish it with any metadata or other non-material changes as requested from TC Admin? https://www.oasis-open.org/committees/document.php?document_id=58522 - AGREED (pending Atlantic call) - unanimous by those present JSON Task Group - notes from last week: - it was suggested that we create a JSON task group to explore the appropriateness of the technology w.r.t. UBL- JSON and noSQL database solutions are good for working *with* UBL documents
- XML is good for representing UBL documents for interchange - many vendors are coming out with solutions incorporating JSON, but they are all bespoke and incompatible with each other - if we ended up with a methodology for applying UBL structures in a JSON environment, this may be helpful to the community - no action this week; still looking for a lead to take on this review UBL 2.1 spreadsheet/information errata found (non-material) - Tim reported that the additions to UBL 2.2 Pre-award were difficult to determine because the version value for the new items were not properly set - for the record, new NDR consistency checks have revealed that the "current version" column of the UBL 2.1 model has incorrect values for 27 entries, rather than the proper value of "2.1": Consignment. Shipping Priority Level Code. Code: "2.0" Declaration. Evidence Supplied: "1.0" Document Reference. Result Of Verification: "2.0" External Reference. Hash Algorithm Method. Text: "1.0" Pickup. Pickup_ Party. Party: "2.0" Shipment. Return_ Address. Address: "2.0" Status. Condition: "2.0" Transport Execution Plan Request. Signature: "2.0" Transport Execution Plan. Signature: "2.0" Transportation Status Request. Details: "2.0" Transportation Status Request. UBL Version Identifier. Identifier: "2.0" Transportation Status Request. Customization Identifier. Identifier: "2.0" Transportation Status Request. Profile Identifier. Identifier: "2.0" Transportation Status Request. Identifier: "2.0" Transportation Status Request. Carrier Assigned_ Identifier. Identifier: "2.0" Transportation Status Request. UUID. Identifier: "2.0" Transportation Status Request. Issue Date. Date: "2.0" Transportation Status Request. Issue Time. Time: "2.0" Transportation Status Request. Name: "2.0" Transportation Status Request. Description. Text: "2.0" Transportation Status Request. Note. Text: "2.0" Transportation Status Request. Shipping Order Identifier. Identifier: "2.0" Transportation Status Request. Other_ Instruction. Text: "2.0" Transportation Status Request. Consignment: "2.0" Transportation Status Request. Document Reference: "2.0" Transportation Status Request. Signature: "2.0" Web Site Access. URI. Identifier: "2.0" - this does not affect schema validity, so this is a non-material issue, so no need to change the UBL 2.1 deliverables - these values have been repaired in the UBL 2.2 model (they will point to 2.1) so that the new additions in UBL 2.2 can be checked for having the correct value in this column - it also seems that 59 items marked as coming from UBL 2.1 actually came from earlier versions of UBL: Mislabelled version number for old BIEs: 59 Address. Address Type Code. Code Address. Address Format Code. Code Address. Country Subentity Code. Code Allowance Charge. Allowance Charge Reason Code. Code Application Response. Version. Identifier Application Response. Document Response Bill Of Lading. UUID. Identifier Certificate Of Origin. Version. Identifier Classification Scheme. Note. Text Contact. Name Contact. Note. Text Credit Note Line. Note. Text Debit Note Line. Note. Text Despatch Line. Note. Text Goods Item. Identifier Invoice Line. Note. Text Item Comparison. Price Amount. Amount Item Property. Name Item Property. Value. Text Line Item. Sales_ Order Identifier. Identifier Line Item. Note. Text Monetary Total. Allowance_ Total Amount. Amount Monetary Total. Charge_ Total Amount. Amount Order Change. Customer_ Reference. Text Order Change. Payment Means Order Line. Note. Text Order Reference. Sales_ Order Identifier. Identifier Order Response. Customer_ Reference. Text Order Response. Payment Means Order. Customer_ Reference. Text Order. Payment Means Packing List. Version. Identifier Party. Contact Party. Person Payment Terms. Payment Means Identifier. Identifier Quotation Line. Note. Text Receipt Line. Note. Text Receipt Line. Oversupply_ Quantity. Quantity Reminder Line. Note. Text Remittance Advice Line. Note. Text Request For Quotation Line. Note. Text Response. Reference. Identifier Response. Response Code. Code Shipment. Details Shipment. Consignment Shipment. Origin_ Address. Address Signature. Note. Text Signature. Validator. Identifier Signature. Signatory_ Party. Party Statement Line. Note. Text Statement Line. Balance Brought Forward_ Indicator. Indicator Statement. Payment Means Status. Condition Code. Code Status. Reference Date. Date Status. Reference Time. Time Status. Description. Text Status. Status_ Reason. Text Status. Sequence Identifier. Identifier Status. Text - the UBL 2.2 model is being updated to reflect the values used in UBL 2.0 for the above entries - many items labeled 2.0 actually come from 1.0 ... should we abandon the 1.0 values and simply change them to 2.0 so that all versions are from the 2.x family? - Ken will change all versions 1.x to be 2.0 JIRA tickets https://issues.oasis-open.org/issues/?filter=12972 (note that the view can be changed using the box icon at top right; the list view provides the most summary information, without the detail view obscuring the screen space) - when creating tickets, remember to distinguish the following components by how they are described to be used as categories: <https://issues.oasis-open.org/browse/UBL/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel>https://issues.oasis-open.org/browse/UBL/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel - status and resolution values: - NEW - the issue has been created but not yet agreed to be in consideration or not for the development distribution - DEFERRED - the issue is not in consideration for the development distribution - OPEN - the issue is in consideration for the development distribution - RESOLVED + Applied - the issue is implemented in test but not released - RESOLVED + Fixed - the issue is implemented in a released test version; (record which one) - RESOLVED + Cannot Reproduce - considered as no action for distribution - APPLIED - the issue is included in a public review (record which one) - see also the discussion on the status workflows here: https://lists.oasis-open.org/archives/ubl/201606/msg00022.html - members please note to discuss ticket issues as comments to the ticket so that we can audit the discussion when making decisions about the ticket, without having to find the discussion on the main mail list UBL TC next steps - what promotional issues need to be addressed? - do we need a travelling road show along the lines of UBL International? - can anyone volunteer to create more short video segments to be shared? TC CONCALL SCHEDULE Next meetings: 2016-07-20 Pacific 01:00UTC/21:00EDT, Atlantic 14:00UTC/16:00CEST/10:00EDT 2016-07-27 No UBL teleconferences Proposed: 2016-08-03 No UBL teleconferences 2016-08-10 Pacific 01:00UTC/21:00EDT, Atlantic 14:00UTC/16:00CEST/10:00EDT 2016-08-17 Pacific 01:00UTC/21:00EDT, Atlantic 14:00UTC/16:00CEST/10:00EDT 2016-08-24 Pacific 01:00UTC/21:00EDT, Atlantic 14:00UTC/16:00CEST/10:00EDT 2016-08-31 Pacific 01:00UTC/21:00EDT, Atlantic 14:00UTC/16:00CEST/10:00EDT Will anyone be requesting a leave of absence in the near future? For privacy reasons, this discussion will be kept off of the minutes. TC calendar: <http://www.oasis-open.org/committees/calendar.php?wg_abbrev=ubl>http://www.oasis-open.org/committees/calendar.php?wg_abbrev=ubl TC calendar iCal subscription link: <http://www.oasis-open.org/apps/org/workgroup_feeds/ical/my_vcalendar.ics?token=fa658a7994a6cefb10c10be09e139af3&workgroup_id=50>http://www.oasis-open.org/apps/org/workgroup_feeds/ical/my_vcalendar.ics?token=fa658a7994a6cefb10c10be09e139af3&workgroup_id=50 OTHER BUSINESS - none -- Check our site for free XML, XSLT, XSL-FO and UBL developer resources | Streaming hands-on XSLT/XPath 2 training @US$45: http://goo.gl/Dd9qBK | Crane Softwrights Ltd. _ _ _ _ _ _ http://www.CraneSoftwrights.com/o/ | G Ken Holman _ _ _ _ _ _ _ _ _ _ mailto:gkholman@CraneSoftwrights.com | Google+ blog _ _ _ _ _ http://plus.google.com/+GKenHolman-Crane/posts | Legal business disclaimers: _ _ http://www.CraneSoftwrights.com/legal | --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]