RE: [ubl-tsc] Issue with Certificate of Origin Document

Sorry, forgot to attch rec 19.

Andy

From: Andrew Schoka [mailto:AMSchoka@comcast.net]
Sent: Thursday, January 19, 2006 7:43 AM
To: 'Tim McGrath'; 'Jern Kuan, Leong'
Cc: 'ubl-tsc@lists.oasis-open.org'
Subject: RE: [ubl-tsc] Issue with Certificate of Origin Document

Tim, etal,

I attach a copy of rec 19 which I pulled of the website:

http://www.unece.org/cefact/recommendations/rec_index.htm

You can get all the other recommendations there as well. I am still unclear how codelists are managed in UBL 2.0. Any clarification would be welcome.

Andy

From: Tim McGrath [mailto:tmcgrath@portcomm.com.au]
Sent: Thursday, January 19, 2006 2:55 AM
To: Jern Kuan, Leong
Cc: ubl-tsc@lists.oasis-open.org
Subject: Re: [ubl-tsc] Issue with Certificate of Origin Document

SignatureDateTime is now part of the Signature.

We agreed to removde Endorsement from the CertificateOfOriginApplication back in November and transferred them to the COO itself.

We have not specified a code set that must be used but I would suggest we recommend UN/ECE Recommendation No 19.
- which i cannot find on the UN/ECE site but it conatins things like "Sea","Air",'Rail", etc..

Similarly for Transport Means I would suggest we recommend UN/ECE Recommendation No 28, as given in....
http://www.unece.org/trade/untdid/d05a/tred/tred8179.htm

Jern Kuan, Leong wrote:

Hi Tim,

Thanxs for the reply.

I also noticed that the SignatureDateTime has been removed from CertificateOfOriginApplication and Endorsement has been removed.

This information is required to indicate when was the document been submitted and signed.

Next.

Is there any place i can get the code list? e.g. TransportModeCode etc.

Rgds and thanxs

Jernkuan

From: Tim McGrath [mailto:tmcgrath@portcomm.com.au]
Sent: Thursday, January 19, 2006 2:20 PM
To: Jern Kuan, Leong
Cc: ubl-tsc@lists.oasis-open.org
Subject: Re: [ubl-tsc] Issue with Certificate of Origin Document

I confess that these were added becasue the TC felt all document roots needed to contain the "from" and "to" parties. I disagree but they wanted them in for the public review.

I suggest you raise it as an issue.

Jern Kuan, Leong wrote:

Hi TC

My mistake, information for importer and exporter can already be found in <COA><Shipment><Consignment><Exporter or Importer>

However any reasons why are these information duplicated at the root CO document?

Rgds and thanxs

Jernkuan

From: Jern Kuan, Leong [mailto:jernkuan@crimsonlogic.com]
Sent: Thursday, January 19, 2006 9:41 AM
To: ubl-tsc@lists.oasis-open.org
Subject: [ubl-tsc] Issue with Certificate of Origin Document

Hi TSC

After some quick review,

Issues are as logged in here

http://www.eccnet.com/UniversalBusinessLanguage/IssuesList.xml

Submitted by:

Leong Jern-Kuan on January 18, 2006, 8:25 pm

Critical : Transport Library. Certificate of Origin Document type. 1. ExporterParty and ImporterParty are at the wrong ABIE namly Certificate of Origin. 2. EndorserParty is already at Certificate of Origin Application ASBIE

Recommendation:1. ExporterParty and ImporterParty should be at the Certificate of Origin Application ASBIE. 2. Removal of EndorserParty at Certificate of Origin.

Rgds

Jernkuan

--

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

http://www.docengineering.com/

--

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

http://www.docengineering.com/

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 1/16/2006

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 1/16/2006

ubl-tsc message