Comments to 3 January build of UBL 2.0 review package by JPLSC

["Yukinori Saito" <saito-yukinori@fujielectric.co.jp>]

Dear Jon Bosak,

We (UBL JPLSC) have held F2F meeting in Tokyo on January 6. The participants
were five members including me.
We discussed about UBL 2.0 review package.
The followings are our comments.

1. Universal Business Language 2.0 (index.html)
(1) This V2.0 (index.html) is great progress to V1.0. There were much
technical descriptions at V1.0.
However, there are much descriptions of business process and business
documents in V2.0.
V2.0 (index.html) is much understandable and acceptable for UBL users (e.g.
Business Experts).
(2) The section 1.1, 1.2, 1.3 are describing change from V1.0 to V2.0.
We think that these sections should be moved to Appendix.
(3) There are descriptions about changed Elements and Attributes at section
1.3.3 and 1.3.4. There is no information of the reason why these Elements
and Attributes are changed. Especially, removed items should need to
describe the reasons. For example: The item is removed because the function
became unnecessary. The item is removed because the item is achieved by
another means.
(4) Business Process Classification
The classification of Business Process is not appropriately arranged.
The classification of Business Process should be described at the top of
section 5.2 (Business process).
For example: Sourcing, Ordering, Fulfillment, Billing, Payment,
Transportation, Certificate of Origin.
(5) Business Process Description
There are Business Process descriptions at section from 5.3 to 5.9. The
contents are not united.
The contents should contain general description, business rules, and
corresponding business documents.
For example: The description of the business rule and the business documents
have come off at Section 5.7 (Payment Collaboration).
(6) Section 5.10 Document Types
This table is very important.
We want you to describe to which business process each business document
belongs clearly. It seems that it only has to review "Use cases involved".
(7) Section 6.3 Imported Code List Schema
There are only 4 Code Lists at V2.0
There were 13 Code Lists at V1.0.
Why did the number decreased?
(8) B.1 Library Assembly Model
There are 3 Libraries (Common Library, Procurement Library, and
Transportation Library).
We would like you to explain the relation between these libraries and
business process classification.
For example: The Procurement Library has the common ABIEs regarding business
process "Sourcing, Ordering, Fulfillment, Billing, Payment". The
Transportation Library has the common ABIEs regarding business process
"Transportation, Certificate of Origin".

2. Business Documents and Common Libraries
We are anxious whether these business documents (especially new business
documents) are usable in Japanese marketplace.
We (JPLSC members) would like to evaluate these business documents for about
2 or 3 month.

3. Others
(1) .ods
There are many documents named "---.ods" in UBL 2.0 review package.
We don't know what are these files. We cannot open these document by our
Personal Computers.
Please tell us what these are and how to open.

Best Regards
Yukinori Saito
(Vice chair of UBL JPLSC)
-------------------------------------------
Yukinori Saito
Fuji Electric Information Service Co., Ltd. (FIS)
e-mail: saito-yukinori@fujielectric.co.jp
Tel: +81-3-5435-7333     Fax: +81-3-5435-7513
------------------------------------------- 

----- Original Message ----- 
From: <jon.bosak@sun.com>
To: <ubl@lists.oasis-open.org>
Sent: Wednesday, January 04, 2006 6:04 AM
Subject: [ubl] 3 January build of UBL 2.0 review package


Hello UBL TC,

A second build of the UBL 2.0 review package can temporarily be
found at

   http://ibiblio.org/bosak/ubl/wd-UBL-2.0/

with the whole thing temporarily downloadable from

   http://ibiblio.org/bosak/ubl/wd-UBL-2.0.zip

This draft bears a publication date of 3 January 2006.  This is
important because I'll be recycling the temporary URLs above as we
revise the package, so be careful to note the dates when you
download from these locations.  The 3 January draft differs from
the one dated 1 January that I posted yesterday chiefly in the
inclusion of Tables 1-3, which list the changes to 1.0 elements
and attributes in 2.0.

We will be discussing this in tomorrow's Atlantic TC call.  Please
send comments and corrections to the list.  Barring the discovery
of some new major problem, this is what I'll be asking our
stakeholders and ubl-dev to look at starting Wednesday afternoon
my time.

PLEASE NOTE that the purpose of this draft is to begin the OASIS
public review process and gather input.  It's not meant to be
perfect at this point.  So minor issues should simply be noted for
the issues list to be dealt with after the initial review.  The
kind of problems we're looking for today are the kind that would
prevent the specification from being used at all (for example,
invalid schemas or a missing document type).

I will be proposing in tomorrow's call that we begin a vote to
approve this build (modulo necessary editorial changes) as a
committee draft on Friday and submit it to OASIS to begin public
review the week of 16 January.

Jon

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php