OASIS ebXML Messaging Services TC

 View Only

  • 1.  Case sensitivity of AS4 headers

    Posted 03-27-2025 04:35
    Hello,

    In ebMS3 and AS4 there is no discussion on case-sensitivity of text
    values of headers.    One AS4 product treats them as case-insensitive
    and processes

    <eb:action>NewPurchaseOrder</eb:action>

    and

    <eb:action>newpurchaseorder</eb:action>

    in the same way.

    In theory the business logic for NewPurchaseOrder could be different
    from newpurchaseorder.  So the case to use should be as specified in the
    P-Mode. This is how other products implement it.    If they have only
    the NewPurchaseOrder configured,  a message with newpurchaseorder is an
    error.

    There can be discussion on party identifiers as some schemes are
    existing code lists that may specify that the values are case
    insensitive whereas others are sensitive.  So value and VALUE may or may
    not be the same party dependent on the scheme.

     <eb:partyid type="urn:sometype">value</eb:partyid>

     <eb:partyid type="urn:sometype">VALUE</eb:partyid>

    IMO for the Pmode and in AS4 messages,  a specific agreed/configured
    case-sensitive value must be used. Generic AS4 products cannot be
    expected to know about such differences between code schemes.   Any
    opinions?

    Thanks,

    Pim


  • 2.  RE: Case sensitivity of AS4 headers

    Posted 03-27-2025 04:39


    Resending because somehow this email gateway strips my inline XML

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


    Hello,

    In ebMS3 and AS4 there is no discussion on case-sensitivity of text values of headers.    One AS4 product treats them as case-insensitive and processes

    <eb:Action>NewPurchaseOrder</eb:Action>

    eb:Action: NewPurchaseOrder


    and

    <eb:Action>newpurchaseorder</eb:Action>

    eb:Action: newpurchaseorder


    in the same way.

    In theory the business logic for NewPurchaseOrder could be different from newpurchaseorder.  So the case to use should be as specified in the P-Mode. This is how other products implement it.    If they have only the NewPurchaseOrder configured,  a message with newpurchaseorder is an error.

    There can be discussion on party identifiers as some schemes are existing code lists that may specify that the values are case insensitive whereas others are sensitive.  So value and VALUE may or may not be the same party dependent on the scheme.

     <eb:PartyId type="urn:sometype">value</eb:PartyId>

    eb:PartyId type="urn:sometype">value

     <eb:PartyId type="urn:sometype">VALUE</eb:PartyId>

    eb:PartyId type="urn:sometype">VALUE</eb:PartyId>


    IMO for the Pmode and in AS4 messages,  a specific agreed/configured case-sensitive value must be used. Generic AS4 products cannot be expected to know about such differences between code schemes.   Any opinions?

    Thanks,

    Pim


    On 27-03-2025 09:34, Pim van der Eijk via OASIS wrote:
    01000195d6bd32c7-4af8dc5d-4aec-463a-ad69-3dc0a1b17ecc-000000@email.amazonses.com">
    Hello, In ebMS3 and AS4 there is no discussion on case-sensitivity of text values of headers. One AS4 product treats them as case-insensitive... -posted to the "OASIS ebXML Messaging Services TC" community



    Original Message


Related Content