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: Agenda for Atlantic UBL TC call 23 November 2016 15:00UTC

Agenda for Atlantic UBL TC call 23 November 2016 15:00UTC



   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


    - 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:
    - the ISO/IEC catalogue entry is found at:
    - the ISO/IEC document and attachments are found at:


   Additions to events calendar: http://ubl.xml.org/events
    - Seminar: UBL E-invoicing, a daily practice
      ? 7 December 2016 ? The Netherlands
      - proposal to designate Kees as a representative of the UBL TC
        to be recognized at the event as a TC representative
        - there are no formal tasks to perform, just to be present and be
          seen by others that the TC takes an interest in the subject matter
    - any other new events to add at this time?

   Review of Atlantic call minutes

  Membership status review

    - 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 gaining voting status:
      - Kees Duvekot
        - Member OASIS BDXR
      - Enric Staromiejski Torregrosa
        - Member OASIS ebXML, European Commission liaison (DG GROWTH)
    - active non-voting members
      - Roberto Cisternino
        - IT Expert UN/CEFACT
      - 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 csd01wd12 spreadsheet is found here:
   - the csd01wd11 working draft release of UBL 2.2 artefacts and hub document
     is found at:

 - documentation requirements
   - a Google text document of the csd01wd12 hub document is here:
   - committee members have been given permissions to edit the document
     - please colour additions in red and indicate in the hub document ticket
       that a change has been made
   - 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
     - business objects - sections 2.x
   - section 2.20 party roles is now managed separately using the XML document
     "UBL-2.2-Party-summary-information.xml" in this directory:
   - section 3.2.x is now managed separately using the XML document
     "UBL-2.2-Schema-summary-information.xml" in this directory:
     - 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:

UBL-55  Pre-award issues for the hub document and document type names
 - how does figure 17 change?
 - do we make the following changes to document names?  do we leave the
   response documents to be "...Confirmation" because they aren't used for a
   negative response?
   - Expression of Interest -> Expression of Interest Request
   - Expression of Interest Confirmation -> Expression of Interest Response
   - Unsubscribe from Procedure -> Unsubscribe from Procedure Request
- Unsubscribe from Procedure Confirmation -> Unsubscribe from Procedure Response
 - do any other new documents need to have their name changed?

UBL-54  Incorrect use of Text representation term for Name primary noun
 - Ken will do this for the next release

UBL-53  Add any new process flow swim lane diagrams
 - Ken will do this for the next release
 - we probably have enough now, though if anyone thinks of other additions
   please let Ken know ASAP

UBL-52  Example XML instances must be created by all members
 - only a few have been added to UBL 2.2 ... we could use more

UBL-51  Party role documentation must be completed by all members
 - no work has been done on this yet, this is probably on the critical path
 - entries needed for all new document types
 - remember to edit the XML and Ken will generate the table from the XML

UBL-34  Hub document change tracking
 - 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
 - Ken has reviewed everything except the Party Role table and made changes to
   accommodate UBL 2.2 based on input from others and a review of the UBL 2.1
   - please review all of the content other than the Party Role table and
     suggest changes; if no changes are suggested, the current text will be
     used in the first public review; all changes are welcome (spelling,
     grammar, turn of phrase, incorrect information, etc.)

JSON Task Group
 - intermediate work being tracked in this document:
 - 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:
 - per TC process 3.4.1 last paragraph, nothing can change in the document
   at this point until after the public review

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:

   - 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:
     - DEFERRED - the issue is not in consideration for the development
                - 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:

   - 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


 Next Atlantic call meetings:
  2016-11-23 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2016-11-30 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2016-12-07 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2016-12-14 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2016-12-21 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2016-12-28 No UBL teleconferences
  2017-01-04 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2017-01-11 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2017-01-18 Atlantic teleconference 15:00UTC/16:00CET/10:00EST
  2017-01-25 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:

 TC calendar iCal subscription link:


 - as comes forward

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]