← Prev in month
← Prev in thread
Next in thread →
Next in month →
Agenda for Atlantic UBL TC call 09 November 2016 15:00UTC
Agenda for Atlantic UBL TC call 09 November 2016 15:00UTC http://www.timeanddate.com/worldclock/fixedtime.html?iso=2016-11-09T15:00:00 CONFERENCING INFO https://www4.gotomeeting.com/join/806072703 https://app.gotomeeting.com/?meetingid=806072703 Use your microphone and speakers (VoIP) - a headset is recommended. Or call in using your telephone. Australia: +61 (0) 2 8014 4935 Austria: +43 (0) 7 2088 1402 Belgium: +32 (0) 38 08 1856 Canada: +1 (647) 724-3550 Denmark: +45 (0) 69 91 88 64 Finland: +358 (0) 942 41 5780 France: +33 (0) 182 880 458 Germany: +49 (0) 898 7806 6467 Ireland: +353 (0) 14 845 978 Italy: +39 0 553 98 95 67 Netherlands: +31 (0) 208 080 381 New Zealand: +64 (0) 9 909 7888 Norway: +47 21 03 58 98 Spain: +34 955 32 0845 Sweden: +46 (0) 313 613 557 Switzerland: +41 (0) 435 0167 08 United Kingdom: +44 (0) 207 151 1851 United States: +1 (215) 383-1010 Access Code: 806-072-703 Audio PIN: Shown after joining the meeting Meeting ID: 806-072-703 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 - any new events to add at this time? Review of Atlantic call minutes https://lists.oasis-open.org/archives/ubl/201611/msg00004.html Membership status review 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 - 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 - current UBL TC voting member list (alphabetical) and relationships: - Oriol Bausà Peris - Member OASIS BDXR, Member OASIS ebXML, Editor TC434 Validation - Kenneth Bengtsson - Chair OASIS BDXR, Member OASIS ebXML - Erlend Klakegg Bergheim - Member OASIS BDXR, Member OASIS ebXML Core & MS - Member CEN/TC434/WS8 - G. Ken Holman (Chair OASIS UBL TC) - Member OASIS BDXR, CA Member JTC 1/SC32, CA Expert UN/CEFACT - Ole Ellerbæk Madsen - DK Member CEN/TC440, CEN/TC440 Liaison JTC 1/SC 32 - members approaching losing voting status: - Erlend Klakegg Bergheim - active non-voting members - Roberto Cisternino - IT Expert UN/CEFACT - Kees Duvekot - Member OASIS BDXR - Tim McGrath - Audun Vennesland UBL 2.2 - someone is needed to manage requirements for transportation documents - Kees managing requirements for post-award documents - Ole managing requirements for pre-award documents - Roberto managing requirements for party information documents - the current UBL 2.2 csd01wd11 spreadsheet is found here: https://docs.google.com/spreadsheets/d/185sbrn5rodJmu612GGI54_N0eQKNvKZhnoIgksM-MWI/edit - the csd01wd10 working draft release of UBL 2.2 artefacts and hub document is found at: https://www.oasis-open.org/committees/document.php?document_id=59297 https://lists.oasis-open.org/archives/ubl/201611/msg00006.html - documentation requirements - a Google text document of the csd01wd11 hub document is here: https://docs.google.com/document/d/1-w-ChVc6zl0DzCDvWV5wN0bZI8_X9PirYEAyP9eEB-c/edit - committee members have been given permissions to edit the document - please colour additions in red - each submitter of new documents and objects must consider what additional documentation is needed in the UBL hub document: - general business rules - sections 2.2.x http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#S-GENERAL-BUSINESS-REQUIREMENTS - business objects - sections 2.x http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.html#S-OVERVIEW-OF-BUSINESS-PROCESSES - section 2.20 party roles is now managed separately using the XML document "UBL-2.2-Party-summary-information.xml" in this directory: https://docs.google.com/document/d/117EDHqlOIYu7SIFg6ce8gOJs4PvE23nTewdWrMddUTU/edit - section 3.2.x is now managed separately using the XML document "UBL-2.2-Schema-summary-information.xml" in this directory: https://docs.google.com/document/d/11gF7jUG-RliMiTEf109lkwj0blbK7HAXizJvFNLYqik/edit - edit the XML directly, or copy and paste into your favourite editor - please do the process quickly to avoid conflict edits with others - there is no need to maintain alphabetization ... just group new documents at the end by subcommittee - please inform Ken when the changes are made - Ken will draw the diagrams if committee members sketch them out as needed in pencil and send a photograph to Ken's email - please note these documentation issues are on the critical path to the release of our first public review - please review all JIRA tickets and comment and/or act where necessary: https://issues.oasis-open.org/issues/?filter=12972 UBL-53 Add any new process flow swim lane diagrams https://issues.oasis-open.org/browse/UBL-53 UBL-52 Example XML instances must be created by all members https://issues.oasis-open.org/browse/UBL-52 UBL-51 Party role documentation must be completed by all members https://issues.oasis-open.org/browse/UBL-51 UBL-34 Hub document change tracking https://issues.oasis-open.org/browse/UBL-34 - please note on this ticket when you have made changes to the hub document - please remember to colour the additions and changes red when editing JSON Task Group - intermediate work being tracked in this document: https://www.oasis-open.org/committees/document.php?document_id=59159 - emphasize that it is an exchange format - can be mechanically transliterated to and from XML losslessly - emphasize that it may not be suitable for other purposes - e.g. direct consumption by tools such as Oracle and Mongo may not be possible, requiring JavaScript, Python or other programming to create a user's custom internal representation of the information found in the exchange document - what kind of document to describe the warnings? - could be a "usage document" on its own or a chapter of the UBL NDR - specification itself could be a chapter of the BD NDR Naming and Design Rules - TC Admin announced the 60-day public review ending 18 December 2016: https://lists.oasis-open.org/archives/ubl/201610/msg00011.html https://lists.oasis-open.org/archives/ubl/201610/msg00012.html - per TC process 3.4.1 last paragraph, nothing can change in the document at this point until after the public review https://www.oasis-open.org/policies-guidelines/tc-process#cos-Submission-laterChangesDisallowed 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 - in order for the issue to become active work for the committee the new ticket must be changed to OPEN or it will not be seen in the "to do" filter - the other option on a new ticket is to change it to DEFERRED - please remember to look at the open filter to ensure visibility: https://issues.oasis-open.org/issues/?filter=12972 - DEFERRED - the issue is not in consideration for the development distribution - please remember to use this when creating new tickets for backwards-incompatible changes - OPEN - the issue is in consideration for the development distribution - keep the issue OPEN when assigning to Ken for incorporation - please remember to add a comment regarding expectations whenever you assign an OPEN ticket to another person for any action - RESOLVED + Applied - the issue is incorporated in test but not released
← Prev in month
← Prev in thread
Next in thread →
Next in month →