MINUTES OF EUROPE/ASIA UBL TC MEETING 8 June 2005

[Tim McGrath <tmcgrath@portcomm.com.au>]

MINUTES OF EUROPE/ASIA UBL TC MEETING
08H00 - 10H00 UTC WEDNESDAY 8 JUNE 2005

ATTENDANCE

1. Rollcall
Tim McGrath
Mavis Cournane
Thomas Lee
Peter Borresen
Sue Probert 
Mikkel Brun
Ralph Ho DTTN - invited expert
Lun Cheng DTTN - invited expert

2. Liaison Report
ebXML Asia update
There are about 10 people registered for ebXML Asia including Patrick Chan the OASIS Asia/Pacific representative.
There will be a UBL presentation at that meeting.
Thomas will be doing the presentation and talk about UN/CEFACT negotiations and feasability study.

3. Subcommittees & Team Reports
HISC wants to know as early as possible the type and number of document 
types we will be producing for UBL 2.0. The HISC is also laising with 
UN/eDocs about mapping to the UN layout key.
So there are two streams of discussion going on with UN/eDocs one on 
alignment and one by HISC.

We have representatives from the transport and the EU government groups 
on this call.

4. Extended procurement process
Peter Borresen is about to update the next draft of this document and 
implement comments received. Some work has been done with other Danish 
experts.
The procurement process will look a lot like that suggested by the OGC 
Group. For exmaple , a Rectification Advice is needed to correct a delivery that does not meet 
the order requirements (we cannot just use another DeliveryAdvice).

5. C of Origin from Crimson Logic and the DTTN contributions
At a discussion last week with DTTN who developed the transport models, 
it was suggested we package the DTTN submission such that we are 
looking at 3 additional document types:
The BillofLading, WayBill, and ForwardingInstruction.
These were identified in the APEC paperless trading initiative as the 
three documents essential for international trade.
To develop those 3 documents means incorporating 90% of the reusable 
library (the common reusable components for the international trade and 
transport context of use). 
This is a good reason to split the library into core reusable and common reusable.
DTTN are still looking at the C of Origin from Singapore.

6. UBL 2.0 Issues list
All the requirements from the various submissions need to be put in to 
the issues list.
We are attempting to bring the Crimson Logic and the DTTN, the European 
and Tax XML submissions in to one set of issues.

7. Tax XML Requirements
Tax XML have produced a document showing how they believe that tax 
items should appear. They believe that 13-14 items should be added to 
UBL and a similar number are questioned.
We recognize a difference of purpose between TAX XML and UBL 2.0.  
Theirs is to allow tax reporting, ours is to support business processes for 
procurement (and transportation). So we have a choice of approaches when
dealing with Tax issues.
The first option is to create structures that satisfy every regulatory 
environment for tax. i.e have hardwired in to UBL, the british 
government VAT requirements, the french consumption tax requirements, 
US Sales Tax , etc, etc...
We may be better off to have a generic tax model and 
a set of guidelines how to use the model for British tax etc. The 
people who understand those taxes should be responsible for developing 
those guidelines.
Perhaps we should work with TAX XML to produce guidelines, maybe one 
for direct taxes and one for indirect taxes.  It was noted that some of 
Tax XML's requirements for additional items appear justified as well.

8. Alignment with UNedocs
The current thinking of the feasability study is if we were to develop 
a common core comp library that incorporated the implicit core 
components used in UBL 1.0 and the explicit core components suggested 
by UNedocs, that can provide the basis for developing UBL 2.0 in a way 
that would align with UNedocs and also satisfy requirements for the 
Core Component technical specification.

We may only need to focus on a one way mapping for alignment. UNedocs is 
a printed document format. The idea is you can take UBL document and use 
the logical mapping to UNedocs as a way of producing physical maps to printed 
forms (such as the UN Layout Key).

By the end of July we will be in a position where we understand more 
clearly how to create the three layered/contextualized models. That also 
is an essential requirement for the UBL tools group.

9. NDR Work
DTTN will share their use of NDR with the NDR group.  They will also look at 
the proposed UBL Code List strategy (Mavis to supply - see email addresses above)

Bryan Rasmussen from the Danish Government will look at the UBL 
Customisation document and provide input to it.

10. Work Plan and Schedule

Suggestion to revise as follows:

   20 Jun 2005 Finalize and agree requirements/issues list for 2.0
               - Extended Procurement process
               - Tax requirements
               - Trade and Transport process
   21 Jun 2005 Begin updating spreadsheet models
               - Agree to model changes  
               - Agree changes to the NDR
               - Reconfigure tools as required 
   04 Jul 2005 Begin TC Review Number 1 (data model only)
               - Load spreadsheets into EDIFIX and test/revise until synchronized
   11 Jul 2005 GEFEG gets all the schema changes decided so far
   08 Aug 2005 All-week UBL TC meeting in Ottawa hosted by Adobe:
               - Review of the spreadsheet and EDIFIX models.
               - Comment disposition, Review Number 1; 
               - Begin final schema generation for Review Number 2


-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160

DOCUMENT ENGINEERING: Analyzing and Designing Documents for Business Informatics and Web Services
(coming soon from MIT Press)
http://mitpress.mit.edu/catalog/item/default.asp?sid=632C40AB-4E94-4930-A94E-22FF8CA5641F&ttype=2&tid=10476