| Standards for Technology in Automotive Retail |
| Home - News Feed

2.5. The payload Manifest SOAP Header
Prev | Chapter 2. Common Components | Next

## 2.5. The payload Manifest SOAP Header

STAR defines a custom SOAP header to serve as a table of contents for the message. The payload manifest contains one manifest element for each content element in the SOAP body. The manifest provides an easy and fast way to identify the types of data in the message payload without parsing the whole message. This is useful for implementations that make routing decisions based on the contents of the message. And, it is especially useful if the body of the message is encrypted.

Figure 2.9. Payload Manifest

The manifest has the following attributes:

- namespaceURI: (Required) -This attribute contains the namespace URI of the XML element in the corresponding content in the SOAP body.

- element: (Required) - This attribute contains the local name of the XML element in the corresponding content in the SOAP body.

- contentID: (Required)This attribute should be populated with the ID of the corresponding content element. This attribute, along with the id attribute of the content element is used to match the manifest to its corresponding content element.

- version (Optional) - When the payload content is a BOD, this attribute contains the version number of the noun's schema used to validate the BOD, for example, 3.01. DTS files use the interfaceVersion of the file. For BOD content and DTS attachments this attribute is required.

| STAR Level 1 Requirement
STAR1018: A SOAP Header MUST contain one manifest element for each content element in the SOAP body. STAR1019: A manifest is REQUIRED to have namespaceURI, element, contentID, and version attributes. Even though version is listed as optional it is REQUIRED for STAR BOD and DTS transports.

Prev | Up | Next
2.4. Web Methods | Home | Chapter 3. Communication Patterns