MHonArc v2.5.0b2 -->
ubl-tsc message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ubl-tsc] Issue with Certificate of Origin Document
Jern Kuan, Leong wrote:
Hi Tim
Great, i was suspecting
that, so it should be validationDateTime?
I meant that
SignatureDateTime is no longer found in endorsement. But explained by
you, it has been placed in <signature><validationDateTime>
Correct
Lastly, where can i
locate the price of the items? It used to be under
<Item><BasePrice><PriceAmount>
BasePrice is not associated with LineItem not Item. This is becasue
the price of an item can vary depending on the order (quantity,place,
time, etc)
Sometime we would need
the items in COO to have some monetary values in there.
Any samples from Peter
on the dsig?
Not as far as I know. But he is working on sample instances for all UBL
2.0 documents so I expect it is a part of that. Perhaps you should
make a reuqets to the entire UBL TC just to remind them.
I think that under the proposed model the signatures are just another
type of attachment so it should be easy to create an example.
Rgds
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
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
Hi TSC
After some quick review,
Issues are as logged in here
| 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/
--
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/
|
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]