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: Minutes of Atlantic UBL TC call 26 October 2016 14:00UTC


Minutes of Atlantic UBL TC call 26 October 2016 14:00UTC

ATTENDANCE

  Oriol Bausà
  Kenneth Bengtsson
  Erlend Klakegg Bergheim
  G. Ken Holman (convener)

  Regrets received in advance:

   Tim McGrath
   Ole Madsen
   Kees Duvekot


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
    - no new events to add at this time

   Review of Atlantic call minutes
      https://lists.oasis-open.org/archives/ubl/201610/msg00013.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
    - 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 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
      - Kees Duvekot
        - Member OASIS BDXR
      - G. Ken Holman
        - 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
      - Tim McGrath
        - EESPA Observer CEN/TC434, AU Expert UN/CEFACT
    - member losing voting status after this meeting:
      - Tim McGrath
    - active non-voting members
      - Roberto Cisternino
      - Audun Vennesland
   - upcoming committee membership changes:
      https://lists.oasis-open.org/archives/ubl/201610/msg00007.html

  Appreciation for logistics support
   - the committee offers hearty thanks to Tim McGrath for supplying the
     GoToMeeting access up until now and to Kenneth Bengtsson for picking
     up this critically important expense on behalf of our committee


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
 - 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 csd01wd09 spreadsheet is found here:
https://docs.google.com/spreadsheets/d/185sbrn5rodJmu612GGI54_N0eQKNvKZhnoIgksM-MWI/edit
   - the csd01wd08 working draft release of UBL 2.2 artefacts is found at:
     https://www.oasis-open.org/committees/document.php?document_id=59045
     https://lists.oasis-open.org/archives/ubl/201609/msg00067.html

 - documentation requirements
   - a Google text document of the hub document is here:
https://docs.google.com/document/d/11Atj1Knidip35iwt_3hWgJlY7OhNhHh5OYCCx53mAYE/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.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
 - 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
   - 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
     - we aren't going to make this because of vacation schedules
   - 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, leaving the ticket status as "OPEN"
     (Ken will change it from OPEN to RESOLVED when the changes have been
      incorporated into internal draft or external released deliverables)
   - when asking a question in the spreadsheet, or challenging a value such
     as a definition, please include a question mark (?) and that can be used
     to search for outstanding issues ... better still would be to simply
     create a JIRA ticket for the issue and leave the definitions untouched
     until they are addressed

UBL-50 Can we use the DigitalCapability document as TPA ?
https://issues.oasis-open.org/browse/UBL-50
 - are we adding a TPA document to the suite of documents?
 - if so, do we wait for the second public review?

UBL-48 Consignment usage note for hub document re: transport events
https://issues.oasis-open.org/browse/UBL-42
 - does anyone have editorial comment on Tim's submission before I incorporate
   it in the hub document?

UBL-34 Hub document change tracking
https://issues.oasis-open.org/browse/UBL-34
 - note that the Party Roles table has been distilled out (as described above)

UBL-28 Support for Verified Gross Mass
https://issues.oasis-open.org/browse/UBL-28
 - is this ready to sign off and go to the first public review?


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
- RESOLVED + Fixed - the issue is incorporated in a released test version;
                          (record which one)
     - RESOLVED + No Action - considered as no action for distribution
     - 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

   - to find all of the OASIS TC Administration tickets related to UBL, use
     the https://issues.oasis-open.org/issues/?filter=13070 filter


TC CONCALL SCHEDULE

 Next Atlantic call meetings:
  2016-10-26 Atlantic teleconference 14:00UTC/16:00CEST/10:00EDT
 Proposed:
  2016-11-02 Atlantic teleconference 15:00UTC/16:00CET/11:00EDT
  2016-11-09 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2016-11-16 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2016-11-23 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2016-11-30 Atlantic teleconference 15:00UTC/16:00CET/10:00EST

 Next Pacific call meetings:
  CCYY-MM-DD Pacific 02:00UTC/21:00EST - November to March
  CCYY-MM-DD Pacific 01:00UTC/21:00EST - April to October
  - these teleconferences are suspended until warranted by attendance

 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 |



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