Re: [egov] Groups - ebxml.pdf uploaded

[Duane Nickull <duane@yellowdragonsoft.com>]

Graham:

In response to the questions regarding Unique Identifiers (section 3.6 
of this docuemnt) - this issue has been address by allowing multiple ID 
types within the message header.

Line 780 of the specification v 2.0 describes this:

"The PartyId element has a single attribute, type and the content is a 
string value. The type attribute indicates the domain of names to which 
the string in the content of the PartyId element belongs. The value of 
the type attribute MUST be mutually agreed and understood by each of the 
Parties. It is RECOMMENDED that the value of the type attribute be a 
URI. It is further recommended that these values be taken from the EDIRA 
(ISO 6523), EDIFACT ISO 9735 or ANSI ASC X12 I05 registries.
If the PartyId type attribute is not present, the content of the PartyId 
element MUST be a URI [RFC2396], otherwise the Receiving MSH SHOULD 
report an error (see section 4.1.5) with errorCode set to Inconsistent 
and severity set to Error. It is strongly RECOMMENDED that the content 
of the PartyId element be a URI."

Duane Nickull

-- 
***************************************************
Yellow Dragon Software - http://www.yellowdragonsoft.com
Web Services & ebXML Messaging / Registry Downloads
Project Team Lead - UN/CEFACT eBusiness Architecture
Phone:   +1 (604) 738-1051 - Canada: Pacific Standard Time
Direct:  +1 (604) 726-3329