Re: [ubl] Re: Restracturing UBL spreadsheet V1.0 to V1.1

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

One thing we need to accommodate in this idea is how it relates to the ebXML
Core Component Technical Specification.  I suspect this is behind Michael's
question.

I now realize that we may cause some confusion by calling them "Core BIEs".
 Because the ebXML Core Component Technical Specification also uses the word
"core" but not in the same sense we mean.

In ebXML it means "from which everything is derived". So all BIEs must be
derived from a "core" component. 

I think we meant "core" as in "the central or most important part of something".
  So not all BIEs are derived from our "core" BIEs.  It is just our "core"
BIEs are used across all contexts.

Whilst struggling for a better term I realized we have a precedent to follow.
 We could follow the principles used for Core Component Types libraries.
 But instead of Data Types being derived from Core Component Types, we have
BIEs derived from Core Components.

Core Component Types would be equivalent to the "core components" of UBL
(which we will need to explicitly identify).
Unspecialized (or Unqualified) Types would be equivalent to our "core" BIEs.
Specialized (or Qualified) Types would be equivalent to the document and
common-in-context BIEs.
 
So I thought maybe instead of "core" BIEs , we could call them "unspecialized"
BIEs and the common-in-context could be called "specialized".

This means that we have:

one "unspecialized" library of re-usable BIEs that are used in any document
types (the same as Saito-san's "core BIEs").  

one "specialized procurement" library of re-usable procurement BIEs that
are used in any procurement document types (the same as Saito-san's "common
procurment BIEs").  At a schema level this could be called the Procurement
Aggregate Components.

one "specialized transportation" library of re-usable procurement BIEs that 
are used in any transportation document types (the same as Saito-san's "common 
transportation BIEs")

Each document type definition would include the "unspecialized" library and
also the "specialized" library for its context of use. The main reason for
separating them into "unspecialized" and "specialized" is to make the library
more manageable and useable for specific contexts.

We have not activiely discussed this yet, but all of these should be derived
from a library of UBL "core components".  This Core Component library will
not be used directly in any document models - just like the core component
types aren't used in the documents either.  Its purpose is to provide the
building blocks and it contains only the information pieces necessary to
describe a specific concept. 
 
 Yukinori Saito wrote:

Dear Michel Dill,
Yes, in case this proposal is approved, the current Reusable spreadsheet
(V1.0) will be divided to two spreadsheets instead of one.
But the name of the Reusable will be changed to the following name according
to the discussion at UBL TC Hangzhou meeting.
- Common Procurement BIEs: Reusables to be used for only the procurement
process.
- Core BIES: Reusables to be used for all documents types across processes.

In the near future, the adding document types will be developed. For
example: Transportation process.
The contents for the new documents will be classified to the following two
layers.
- Document BIEs (Transportation)
- Common Transportation BIEs
In case there will be appeared some new common BIEs that will be used for
all documents types across processes, they will be added to Core BIEs.

Finally, UBL spreadsheets will have the following structures.
(1) Document BIEs layer
- Procurement Document BIEs (e.g. Order, Order Response, Order Change,
Despatch Advice, Receipt Advice, Invoice)
- Transportation Document BIEs (e.g. COO, Shipping Order, Airway Bill,
others)
(2) Common Components layer
- Common Procurement BIEs
- Common Transportation BIEs
(3) UBL Core layer
- Core BIEs

If you would like to understand this architecture more, please see Mr.
Thomas Lee's report. I have attached his document in this e-mail.

Best Regards,
Yukinori Saito
-------------------------------------------
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: "Michael Dill" <dill@gefeg.com>
To: "Yukinori Saito" <saito-yukinori@fujielectric.co.jp>
Sent: Thursday, June 23, 2005 11:41 PM
Subject: AW: Restracturing UBL spreadsheet V1.0 to V1.1


Dear Yukinori,
do I understand right, that the reuslt of this, in case it is approved, is
to have two reusable spreadsheets instead of one?
regards
Michel Dill

-----Ursprungliche Nachricht-----
Von: Yukinori Saito [mailto:saito-yukinori@fujielectric.co.jp]
Gesendet: Samstag, 21. Mai 2005 09:05
An: UBL TC
Betreff: Restracturing UBL spreadsheet V1.0 to V1.1


Dear UBL TC members,

According to the decision at UBL TC Hangzhou meeting, I did the following
working regarding restructuring of UBL spreadsheet V1.0.

1. Analysis of the current UBL Reusable V1.0 and restructuring
classification
I have researched and analyzed the current UBL Reusable V1.0.
Then, I have classified ABIEs in the Reusable V1.0 to the restructured
spreadsheet V1.1
I have made the following documents.
(1) Analysis of UBL Reusable Spreadsheet V1.0 and Restructuring of the
Spreadsheet
- This document explains both Analysis method and restructuring method.
(2) Analysis Table of UBL Reusable V1.0 and Classification to V1.1
- This document explains analysis and classifications regarding each ABIE in
Reusable V1.0.

2. Development new spreadsheet V1.1
According to the analysis and classification of Reusable V1.0 described
above, I have made the following spreadsheet V1.1.
These spreadsheets were developed using the recent UBL specifications
'cd-UBL-1.0' at UBL page in OASIS web site.
- UBL-Invoice-1.1.xls
- UBL-CommonProcurementBIEs-1.1.xls
- UBL-CoreBIEs-1.1.xls

According to the analysis, there is no necessity of restructuring the
remaining business documents. e.g.: Order, OrderResponse,
OrderResponseSimple, OrderChange, OrderCancellation, DespatchAdvice,
ReceiptAdvice.

Best Regards,
Yukinori Saito
-------------------------------------------
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
-------------------------------------------

  

---------------------------------------------------------------------
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 

-- 
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