All,
As a follow up to discussions last meeting
regarding candidate text supporting a graphic Use Case Diagram, I attach an
early draft of some material. The group needs to decide on the number of levels
of UC diagrams and descriptions; I show a second and a third level from the
overall Use Case diagram of UBL2.0. I also look to the true transport experts
to help refine the details; however, I think its important to keep the
terminology independent of transport mode so that it may be applicable to any
mode and then further refined as necessary.
Regards,
Andy
From: Kama, Kamarudin
Bin Tambi [mailto:]
Sent: Sunday, February 05, 2006
10:18 PM
To: ubl-tsc@lists.oasis-open.org
Cc: Eric Tesoro; Peter Larsen
Borresen
Subject: [ubl-tsc] Minutes of
Transport Subcommittee Teleconference Call 12 December 2005
Hi all,
Pls find below minutes for last Thursday’s
concall.
MINUTES OF UBL-TRANSPORT SUBCOMMITTEE
1000 – 1120 (SGT) Thursday Feb 02,2006
Teleconference:
PARTICIPANT:
Tim McGrath (UBL Vice Chair)
(UBL TSC Chair)
Andy Schoka (Information Systems Engineer)
Jern Kuan (CrimsonLogic)
Eric Tesoro (CrimsonLogic)
1. Public Review update of the UBL 2.0
OASIS Committee Draft
- Some of the comments are as
follows ;
a. UBL TC has an issue
on the party information not being on the root document . However in COO, there
would be redundant information in the application and in the root document.
b. Three different
category of code list can be seen.
- International standard codes, like
ISO currency, etc
- Codes used by a specific company
like a financial institute.
- Codes used between trading
partners
c. Code list for transportation
mode has not been finalized. Some of the possible code list include transport
means which fall into category 1.
d. There are still
discussions on all of the code list to be used on UBL
e. One of the UBL TC
member, Ken Holman had worked on a paper on code list and TSC is keen to
consider contributing on the different ways of validation and
implementation of code list
f. Code list for 2.0
would be lesser than version 1.0
g. Tim to post on
the website on the issues and comments gathered from the review so
far.
2. Work on supporting materials
a. Process worksheet to
support UML use case.
b. Narrative
description would be added to the use case. BL will be the first document to have
the narrative description. Tim would put forth this to other subcommittee for
adoption for the additional documentation.
c. Andy to work on this
3. UN/CEFACT - UBL Meeting
a. Tim mentioned that
he will be attending the next UN/CEFACT Forum meeting in .
b. Kama mentioned that
he is waiting for approval from the relevant authority in .
c.
mentioned that perhaps UBL members could have a side-meeting during the
UN/CEFACT Forum.
4. AOB
a. Tim mentioned that
UBL TC can hold the plenary meeting in tentatively in late July
or early August after second public review.
(Post-meeting note: In
the recent Manhattan UBL TC meeting, it was decided to move the
meeting to November 06)
5. Digital signature
a. Suggested
implementation would be to use digital signature as an attachment instead
of being embedded
b. Peter to deliver
sample XMLs in February 06 for the proposed implementation of the digital
signature afterwhich TSC will produce sample XML files for the documents under
its care
Action Items:
- Andy to work on BL UML use case
and present in the next meeting
- Tim to post on the
issues/comments on UBL website
- to
inform the local standards organization, ITSC about the Singapore UBL TC
meeting
- Peter to work out sample
documents with digital signature
Best Regards
Kamarudin Bin Tambi
UBL TSC Chair
DID: 65 – 6887 7516
Fax: 65 – 6778 5277
CrimsonLogic Pte Ltd
(Regn No: 198800784N)
formerly
known as
Network Services
,
The Crimson,
117611
Main Tel: 65 - 6887 7888
Main Fax: 65 - 6778 5277
Visit us at www.crimsonlogic.com
Makes better sense
NOTICE
This eMail and any attachments are intended solely
for the named addressee(s) only. It contains confidential and/or privileged
information which should not be copied or disclosed without the consent of the
CrimsonLogic group. If you are not the
intended recipient or if you have received this eMail in error, you must not
copy, distribute, disclose or take any action in reliance on it (or any part of
its contents). In such case, you should inform the CrimsonLogic
group immediately by eMail or telephone +65
68877888 (reverse charges if necessary) and delete this eMail and any
attachments from your system.
The integrity and security
of Internet communications and in particular this eMail and any attachments
cannot be guaranteed. The CrimsonLogic
group accepts no liability whatsoever in
connection therewith. You are strongly advised to carry out all necessary
virus checks and that you open this eMail and any attachments at your own risk.