[ebxmlms-develop] Hermes bug report

[Tripathi, A. (GXS) <Aji...@gx...>]

Bob, Patrick,

I traced hermes a little bit more. 

This is what I am getting in the messages ... does it make sense?  I think
type and value of partyID elements are interchanged!!!!! Please confirm.

<eb:From><eb:PartyId
eb:type="Sample">fromPartyId</eb:PartyId></eb:From><eb:To><eb:PartyId
eb:type="Sampola">toPartyId</eb:PartyId></eb:To>

regards,

Ajit    

---------------

The spec:

It is further recommended that these 783

values be taken from the EDIRA (ISO 6523), EDIFACT ISO 9735 or ANSI ASC X12
I05 registries. 784

If the PartyId type attribute is not present, the content of the PartyId
element MUST be a URI 785

[RFC2396], otherwise the Receiving MSH SHOULD report an error (see section
4.1.5) with errorCode 786

 

3.1.1 From and To Elements 762

The REQUIRED From element identifies the Party that originated the message.
The REQUIRED To 763

element identifies the Party that is the intended recipient of the message.
Both To and From can contain 764

logical identifiers, such as a DUNS number, or identifiers that also imply a
physical location such as an 765

eMail address. 766

The From and the To elements each contains: 767

* PartyId elements - occurs one or more times 768

* Role element - occurs zero or one times. 769

If either the From or To elements contains multiple PartyId elements, all
members of the list MUST 770

identify the same organization. Unless a single type value refers to
multiple identification systems, the 771

value of any given type attribute MUST be unique within the list of PartyId
elements contained within 772

either the From or To element. 773

Note: This mechanism is particularly useful when transport of a message
between the parties may involve multiple 774

intermediaries. More generally, the From Party should provide identification
in all domains it knows in support of 775

intermediaries and destinations that may give preference to particular
identification systems. 776

The From and To elements contain zero or one Role child element that, if
present, SHALL immediately 777

follow the last PartyId child element. 778

3.1.1.1 PartyId Element 779

The PartyId element has a single attribute, type and the content is a string
value. The type attribute 780

indicates the domain of names to which the string in the content of the
PartyId element belongs. The 781

value of the type attribute MUST be mutually agreed and understood by each
of the Parties. It is 782

RECOMMENDED that the value of the type attribute be a URI. It is further
recommended that these 783

values be taken from the EDIRA (ISO 6523), EDIFACT ISO 9735 or ANSI ASC X12
I05 registries. 784

If the PartyId type attribute is not present, the content of the PartyId
element MUST be a URI 785

[RFC2396], otherwise the Receiving MSH SHOULD report an error (see section
4.1.5) with errorCode 786

set to Inconsistent and severity set to Error. It is strongly RECOMMENDED
that the content of the 787

PartyId element be a URI. 788

3.1.1.2 Role Element 789

The Role element identifies the authorized role (fromAuthorizedRole or
toAuthorizedRole)