RE: [ebxml-iic] Proposed EAN.UCC Deployment Guide 0.1

[Eric VanLydegraf <ericv@kinzan.com>]

Hello Pete,
I've just completed reviewing the EAN deployment implementation;
Overall it seems to have worked out quite well, the comments I have are
mostly structure proposals and possibly some guidance for the organization
filling it out and a few fixes.

On the overall level I was thinking we may want to insist or HIGHLY
RECOMMEND the use
of RFC http://www.ietf.org/rfc/rfc2119.txt keywords.

The EAN document seems to use it but it's not consistent which makes me
wonder about it.
e.g. 3.1.1.1 and 3.1.4 have the SHOULD keyword
but 
3.1.5 has lowercase must and is in fact the only "MUST" in the entire
document.

Suggestion:
For document structure a potential document organization is to make the
tables nonbreaking
so they don't flow over into the next page. Makes it a little hard to follow
the question
or understand the answer when split.

Some items I've noticed that may need fixing:

3.1.4 Service Element has as an example with a <eb:CPAID ... /> element.

4.1.4.4
The Value is "V" which I don't understand





-----Original Message-----
From: Pete Wenzel [mailto:pete@seebeyond.com]
Sent: Monday, October 21, 2002 9:54 AM
To: ebXML IIC
Subject: [ebxml-iic] Proposed EAN.UCC Deployment Guide 0.1


(Original submission bounced from OASIS listserve.  Resending.)

Cc: Thomas Bikeev <Bikeev@ean-int.org>

Attached is a proposed EAN.UCC Deployment Guide for ebMS 2.0.  It was
created by placing the content provided by Thomas Bikeev into the 0.3
version of the Template.  Please review and comment.

Note that the modifications to the Template suggested during last week's
conference call have not yet been incorporated.  I will post a new
version of the document when that has been done.

--Pete
Pete Wenzel <pete@seebeyond.com>
SeeBeyond
Standards & Product Strategy
+1-626-471-6311 (US-Pacific)