ID Cyber Identity Ltd bannermap
dot
dot
news
up
dot dot
E-Health
Since 2012:

PKI-Consulting in eHealth

>> Read more
border
up
dot dot
Swiss UIDB ISO6523 listed
May 2013:

Swiss Unique Business Identification Number is now ISO6523 registered.

>> Read more
border
up
dot dot
Giesecke & Devrient
November 2012:

We have presented at the G+D Security Forum.

>> Read more
border
dot
bord
dot dot
border
dot
envelope

Message examples

Below we have listed some examples about the usage of unique business identifiers in messages ("envelopes"):
  • ebMS

    ebXML Messaging Services (ebMS) is a standard under the E-Business XML umbrella which provides a secure and reliable SOAP / Web Services based messaging protocol developed by OASIS and UN/CEFACT.
    A specific example, taken from the OASIS ebCore Party Id Type Technical Specification Version 1.0 is the following:

    <eb3:PartyInfo>
      <eb3:From>
       <eb3:PartyId type="urn:oasis:names:tc:ebcore:partyid-type:iso6523:0088" >
       4035811991021
       </eb3:PartyId>
       <eb3:Role>Buyer</eb3:Role>
      </eb3:From>
      <eb3:To>
      <!-- details omitted -->
      </eb3:To>
    </eb3:PartyInfo>

    Explanation:
    The above excerpt from an ebMS message shows the information about the party sending the ebXML message. The PartyId-tag has a type-attribute. The Uniform Resource Name (URN) dedicating the identifier scheme in the type-attribute ends with "0088". This designates the usage of a GS1 GLN in the body of the PartyId-tag.

  • SBDH

    The Standard Business Document Header (SBDH) is based upon XML and is developed by UN/CEFACT. It provides a standardized envelope (for any kind of business document or other payload) and specifies the header information.
    A specific example, taken from the OASIS ebCore Party Id Type Technical Specification Version 1.0 is the following:

    <sh:StandardBusinessDocument xmlns:sh="http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader" >
      <sh:StandardBusinessDocumentHeader>
       <sh:HeaderVersion>2.2</sh:HeaderVersion>
       <sh:Sender>
        <sh:Identifier Authority="urn:oasis:names:tc:ebcore:partyid-type:iso6523:0088" >
        2203148000002
        </sh:Identifier>
       </sh:Sender>
       <sh:Receiver>
        <sh:Identifier Authority="urn:oasis:names:tc:ebcore:partyid-type:iso6523:0088" >
        6903148000007
        </sh:Identifier>
       </sh:Receiver>
       <!-- Remainder of sample omitted -->

    Explanation:
    The above excerpt from an SBDH envelope contains the unique identifiers of the Sender and the Receiver of the message. The Uniform Resource Name (URN) dedicating the identifier scheme in the Identifier-tag ends with "0088". This designates the usage of a GS1 GLN in the body of the Identifier-tag.

  • AS2

    The EDIINT AS2 (EDI over the Internet Applicability Statement 2) is a protocol for the secure and reliable transport of business data over the Internet by using the HTTP protocol and the S/MIME standard.

    HTTP/1.0 200 OK
    AS2-From: urn:oasis:names:tc:ebcore:partyid-type:iso6523:0060:012345678
    AS2-To: urn:oasis:names:tc:ebcore:partyid-type:iso6523:0060:001368083
    AS2-Version: 1.1
    Message-ID: <709700825.1028122454671.JavaMail@ediXchange>
    Content-Type: multipart/signed; micalg=sha1;
    protocol="application/pkcs7-signature";
    boundary="----=_Part_57_648441049.1028122454671"
    Connection: Close

    Explanation:
    The example shows a so called Message Disposition Notification (MDN) which is sent to confirm the receipt of an AS2-message. The HTTP-headers "AS2-From" and "AS2-To" contain the unique business identifiers of the sender and the recipient of the MDN. These identifiers contain Uniform Resource Names (URNs) which hold the D-U-N-S numbers of the sender and the recipient at the end. The fact that these are D-U-N-S numbers is indicated by the four digits "0060" before them.


dot

dot
treelogix media SA - CH 6934 Bioggio