ubl-australia] Agenda for ALSC Call 14 NOVEMBER 2018 11:00 AEDT

Agenda for ALSC Call 14 NOVEMBER 2018 11:00 AEDT

https://www.timeanddate.com/worldclock/fixedtime.html?iso=20181114T11&p1=57&ah=1

CONFERENCING INFO

Meeting ID: 547 975 473

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

https://zoom.us/j/547975473

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

Or additional telephone numbers:

https://zoom.us/zoomconference?m=tZYVoCjT6sw0zaoKK3bbfRHUX43prdSf

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

REFERENCING THE SPECIFICATION

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:

        http://docs.oasis-open.org/ubl/os-UBL-2.2/

the working semantic libraries for this subcommittee:

Google sheets are located in the ALSC google drive 

https://drive.google.com/drive/folders/16YIef092Y7xBqeiLqevUglAxKxa5QjKG?usp=sharing

STANDING ITEMS

Review of minutes

minutes were 

 

Review of DBC semantic model (Invoice) approach:

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

TAX  Category Codes

Industry Scenarios

Existing trading networks 

Woolworths - Levine

https://docs.google.com/document/d/1sM_MLgyiku_hHL2bJOt4Y7CIjaWAMo5vXrqFAysMdKs/edit?usp=sharing

Generally the flexibility of UBL can support translation to and from EANCOM.  

The content of each invoice could be translated from one to the other, but due to the differences in how the models are structured there would need to be an implementation specific guide that provides rules on how to translate between them. - there doesnât appear to be a simple and straightforward forward mapping. 

Coles - Andrew

Andrew to compare INVOIC with Core Invoice

Metcash - Andrew

Andrew to compare INVOIC with Core Invoice

Small Business - Matt Vickers,

GS1 XML - Levine

   https://drive.google.com/open?id=1x_oFBQ-GNiv-ZuL1Uv96TMVkhxlCbL5tC6HxEbZsY60

Summary of most significant differences/deficiencies  with current ALSC model

some GS1 elements appear to be in other UBL documents, perhaps its due to a philosophical difference in that GS1 may cover a smaller number of documents due to reusing them across a number of business processes

digital signature should be included from base UBL - to review under extension point

address element should include additional elements from base UBL

delivery element should include additional elements from base UBL

Payment Terms structure (GS1) is different from payment terms and payment means structures in UBL  - ALSC model exludes the vast majority of base UBL elements - this work should be reviewed under the payment scenarios work

Payment Scenarios - Matt Lewis

Payment via Card (Credit or Debit) e.g. Visa Debit

Payment via BPAY

Payment via online payment gateway (UI or API). e.g. PostBillPay, PayPal, AfterPay or other vendors.

Payment via Direct Credit (within AU)

Payment via Direct Credit (international)

Payment via an NPP overlay (using any PayID variant). e.g. OSKO

Payment via transfer of Crypto-currency asset/token.

Payment via other method (as much as I dislike the concept many organisations still support payment over the phone, in person or via cheque.  So our semantic model should support them to provide one or more textual payment instructions.)

Partial or complete pre-payment. eg. a direct debit arrangements, partial deposit etc.

Implementation guidance

Delivery structure

Payment Means

GST Free/ exempt examples

Invoice as Receipt

More test examples

Actions:

Chair of ABSIA to progress in March next year

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:

- spreadsheets

- schemas & html

- schematron

- document (xml via docbook or word document) - DITA being explored

When non-OASIS resources are used it is essential to create a snapshot, eg at publication or on reaching a milestone  create a zip file and store on OASIS Kavi server and reference the location of the zip file in the minutes.

There are 2 types of references, use committee link to add revision and use public link for publication eg 

Archive only:

https://www.oasis-open.org/committees/document.php?document_id=63462

https://www.oasis-open.org/apps/org/workgroup/ubl/document.php?document_id=63462

Distribution:

https://www.oasis-open.org/committees/document.php?document_id=63463

https://www.oasis-open.org/apps/org/workgroup/ubl/document.php?document_id=63463

P2P scope - numbered in priority order

Purchasing (2)

Order, Order Response Simple, Order Response, Order Change, Order Cancellation

Fulfilment (3)

Despatch Advice, Receipt Advice, Fulfilment Cancellation

Accounts Payable

Invoice including elaborate payment means (1), Remittance (1), statement (4), reminder (4), Utility Statement (4)

JIRA tickets

Summary - https://issues.oasis-open.org/issues/?jql=project%20%3D%20UBL%20AND%20component%20%3D%20%22Australia%20SC%22

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:

https://issues.oasis-open.org/browse/UBL/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel

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

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/?jql=project%20%3D%20UBL%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20%22Australia%20SC%22

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:

https://lists.oasis-open.org/archives/ubl/201709/msg00000.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

RECRUITMENT

FACE TO FACE MEETING

Will review on an as needed basis

CONFERENCE CALL SCHEDULE

28 November 11am AEDT

12 December 11am AEDT

31 October 11am AEST

SC Calendar - https://www.oasis-open.org/apps/org/workgroup/ubl-australia/calendar.php

SC Calendar subscription link - webcal://www.oasis-open.org/apps/org/workgroup_feeds/ical/my_vcalendar.ics?token=f352ce7037f9b5ccc709d6085becd4e0&workgroup_id=559

OTHER BUSINESS

Levine Naidoo

+61481471758