SBDH Technical Implementation Guide - GS1
SBDH Technical Implementation Guide - GS1
SBDH Technical Implementation Guide - GS1
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Standard Business Document Header (<strong>SBDH</strong>) Version 1.3 <strong>Technical</strong> <strong>Implementation</strong> <strong>Guide</strong><br />
XSD Element / Attribute XSD Type Occ <strong>GS1</strong> Usage <strong>Guide</strong>lines<br />
------| Contact string 0..1 Name of contact person or department<br />
[R8] The element ‘Contact’, although optional, SHOULD be used, if possible.<br />
Example: Delysha Burnet<br />
------| EmailAddress string 0..1 [R9] The element ‘EmailAddress, although optional, SHOULD be used, if<br />
possible.<br />
Example: Delysha.Burnet@CompanyXYZ987.com<br />
------| FaxNumber string 0..1 [R10] A number format agreed upon between the ‘Sender’ and ‘Receiver’<br />
SHOULD be used. Number format expressed using [RFC3966] ‘The tel URI for<br />
Telephone Numbers’ MAY be used. See section 5.1 ‘International telephone<br />
number format’ for recommended options on formatting telephone/fax numbers.<br />
Example: tel:+31.235.3311.87<br />
------| TelephoneNumber string 0..1 [R10] A number format agreed upon between the ‘Sender’ and ‘Receiver’<br />
SHOULD be used. Number format expressed using [RFC3966] ‘The tel URI for<br />
Telephone Numbers’ MAY be used. See section 5.1 ‘International telephone<br />
number format’ for recommended options on formatting telephone/fax numbers.<br />
Example: tel:+31.235.3311.69<br />
------| ContactTypeIdentifier string 0..1 Role of the identifier.<br />
[Example: SELLER<br />
--| Receiver Partner 1..* Receiver of the message, party representing the organization which receives<br />
the standard business document.<br />
[R11] The ‘Receiver’ tag MUST be used exactly only once with <strong>GS1</strong> XML<br />
messages, even though it can occur multiple times<br />
----| Identifier PartnerIdentification 1..1 A unique identification key for the receiving party<br />
[R5] The value of the ‘Identifier’ element of ‘PartnerIdentification’ type MUST be<br />
a GLN. The use of GLN as the identifier is mandatory with <strong>GS1</strong> standards.<br />
Example: 8712345000005<br />
----| Authority string 0..1 Authority agency of the identification key<br />
[R6] The ‘Authority’ attribute, although optional, MUST be used and its value<br />
must be set to ‘EAN.UCC’. For legacy reasons and to support existing<br />
implementations of <strong>GS1</strong> XML standards, the token ‘EAN.UCC’ has been used.<br />
At a future date when a new major version of <strong>GS1</strong> XML standards will be<br />
created (version 3.0) all references to the token ‘EAN.UCC’ associated with<br />
<strong>GS1</strong> XML standards and document shall be replaced with the token ‘<strong>GS1</strong>’<br />
----| ContactInformation ContactInformation 0..* Name of the contact person or department for the Sender Party<br />
[R7] The element ‘ContactInformation’, although optional, SHOULD be used, if<br />
possible.<br />
July-2007, Issue 1 All contents copyright © <strong>GS1</strong> 2007 Page 9 of 21
Change language