Party Proposal

[Doug Bunting <Doug@ariba.com>]

After too many shots at a moving target, I now present my proposal for updates related to the PartyId element.  The attached proposal is based on version 0.91.  It primarily addresses two primary concerns:

• It's insufficient in a multi-hop situation to identify any party using a single scheme (DUNS, SCAC, EAN, whatever).  Without explicit prior agreement on identification schemes for all parties, it's probably insufficient for ebXML to allow only one identifier per party even in single-hop situations.  This was issue 10 in our list.
• The Sender element didn't contain enough information for a receiver to create a valid response (error or intermediate acknowledgement) directed back.  This came up during a discussion about issue 18 last week and follows the general proposal.

In the process, I corrected a number of typographic errors and improved a few consistency problems.  I addressed the nagging doubts Chris and David mentioned about the name "ErrorURI" (for example).  And, I threw in a few things from the various "PartyId" threads on this list.  Things are pretty well marked out as changes, though (as I mention in the attached document) I turned off change tracking for a while.

 

If anyone requests it, I can forward the PDF version tomorrow.  Let me know.

 

thanx,

    doug

           

Doug Bunting

cXML Standards Manager

Ariba, Inc.

 

Party proposal.doc