Minutes for ALSC Face to Face meeting 6 March 10:00 AEDT
ATTENDANCE Martijn van den Boogaard Matt Lewis Andrew Mitchell Levine Naidoo (convenor) Steve Ryan Ken Holman
APOLOGIES
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:
- the working semantic libraries for this subcommittee:
Google sheets are located in the ALSC google drive
STANDING ITEMS
- Review of minutes
- Review of ALSC Semantic Model semantic model:
- 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 - ALSC Artefacts should be: - spreadsheets - schemas & html - schematron - document (xml via docbook or word document)
- 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
- Ken to explore use of an online service for publishing, to provide user id
- 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
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
- 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 + Incomplete - the issue has been decided but not incorporated for test
- 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
RECRUITMENT
- Possible membership increase with state government agencies
FACE TO FACE MEETING
CONFERENCE CALL SCHEDULE
OTHER BUSINESS
Thanks Levine |