OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-australia message

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

Subject: [ubl-australia] Agenda for ALSC Call 22 August 2018 10:00 AEST

Agenda for ALSC Call 22 August 2018 10:00 AEST


Meeting ID: 547 975 473

Join from PC, Mac, Linux, iOS or Android:

Or iPhone one-tap (Australia): +61280152088,,547975473#

Or additional telephone numbers:

Many thanks to http://eFact.pe for sponsoring our teleconferences.

  • the following should be used as a specific citation:
        OASIS Universal Business Language (UBL) v2.2
  • the canonical 2.2 documents are available in the OASIS repository:
  • the working semantic libraries for this subcommittee:
Google sheets are located in the ALSC google drive 


  1. Review of minutes
  1. Review of DBC semantic model (Invoice)
    • Review model issues
      • Optionality in single child elements
      • Cardinality one Accounting Supplier and Customer Party
      • Invoice line documentation (PO, Despatch and Receipt)
      • Party Contact
      • Use of CompanyID in PartyTaxScheme - is it ABN or Branch ID and Cardinality
    • Review application of Invoice policy requirements
    • Review business rules
    • Produce Schematron, including empty elements check
    • GST Category Codes
    • Industry Scenarios
      • Existing trading networks
    • Implementation guidance
      • Delivery structure
      • Payment Means
      • GST Free/ exempt examples
      • Invoice as Receipt
      • More test examples
    • Actions:
      • Levine to capture above issues in the ASLC model spreadsheets with comments
      • Levine to reach out to ABSIA to socialise the ALSC work
  1. Documentation Approach
    • Proposed approach for review and creation of ALSC artefacts with coaching from Ken
- cnd01dw01 as working draft for artefacts
- cnd01dw01 be reviewed under public consultation
- Templates are available from OASIS
- ALSC Artefacts should be:
- document (xml via docbook or word document)
- spreadsheets
- schemas
- schematron
  1. P2P scope
For Discussion:
    • Purchasing
      • Order, Order Response Simple, Order Response, Order Change, Order Cancellation
    • Fulfilment
      • Despatch Advice, Receipt Advice, (Fulfilment Cancellation?)
    • Accounts Payable
      • Invoice including elaborate payment means, Remittance, statement, reminder, (Utility Statement?)
  1. JIRA tickets

When creating tickets for the SC, remember to use âAustralia SCâ to distinguish between the following components by how they are described to be used as categories:
if you leave the "Component/s" field empty, the ticket will not show up in the SC summary filter.

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
    • 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:
    • 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 working draft version
    • RESOLVED + Later - the issue is still up for discussion for a future minor revision but not the current development
    • RESOLVED + No Action - considered as no action for any distribution
    • RESOLVED + Cannot Reproduce - considered as no action for distribution
    • APPLIED + Fixed - the issue is included in a public review (record the availability of the disposition once review opened)
    • DEFERRED - the issue is not in consideration for any minor revision
      • please remember to use this when creating new tickets for backwards-incompatible changes

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

Should we plan a face to face

  • 22 August 10am AEST
  • 5 September 10am AEST
  • 19 September 10am AEST
  • 3 October 11am AEST
  • 17 October 11am AEST
  • 31 October 11am AEST

  • As comes forward

Many thanks

Levine Naidoo
Managing Director â LXNDigital 

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