UBL Australian Localisation SC

Minutes for ALSC Call 5 September 2018 10:00 AEST ATTENDANCE Martijn van den Boogaard Ken Holman Matt Lewis Andrew Mitchell Levine Naidoo (convenor) APOLOGIES Matt Vickers received in advance Steve Ryan received in advance 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 accepted 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 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: ABSIA is progressing discussion with Board. Andrew is also progressing discussion with ABSIA Chair 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) 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 FACE TO FACE MEETING Will review on an as needed basis CONFERENCE CALL SCHEDULE 3 October 11am AEST 17 October 11am AEST 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 None Thank you Levine

Hi Levine, I notice the 19 September is missing from the Conference Call Schedule in the minutes - has this been cancelled? Kind regards, Matt On Tue, 4 Sep 2018 at 20:29 Levine Naidoo < levine@lxndigital.com > wrote: Minutes for ALSC Call 5 September 2018 10:00 AEST ATTENDANCE Martijn van den Boogaard Ken Holman Matt Lewis Andrew Mitchell Levine Naidoo (convenor) APOLOGIES Matt Vickers received in advance Steve Ryan received in advance 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 accepted 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 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: ABSIA is progressing discussion with Board. Andrew is also progressing discussion with ABSIA Chair 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) 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 FACE TO FACE MEETING Will review on an as needed basis CONFERENCE CALL SCHEDULE 3 October 11am AEST 17 October 11am AEST 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 None Thank you Levine -- Matt Vickers Product - New Markets Work (US) +1 (201) 685-0145 Work (NZ) +64 ( 4) 887-9055 Mobile (US) +1 (415) 579-7628 Twitter mattvarchar Skype mattvarchar LinkedIn mattvickers Xero Inc, WeWork, 79 Madison Ave, L5, New York, NY 10016, USA Xero - Beautiful accounting software We're hiring! www.xero.com/careers www.xero.com