Standards for Technology in Automotive Retail
| Standards for Technology in Automotive Retail | |
STAR BOD Specific and Generic Transports must be message level interoperable.
All web services must be compliant to the rules and specifications outlined by the WS-I Basic Profile.
Appropriate compliance markers are required as specified by the WS-I Conformance Claim Attachment Mechanisms document.
Application level error messages MUST NOT be returned with a SOAP Fault, and MUST be returned using the appropriate BOD.
The service provider must keep track of contents that are deemed to have been received by the client to avoid resending.
The client must be able to handle duplicate messages from a service provider.
A SOAP Header MUST contain one manifest element for each content element in the SOAP body.
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.
All STAR Web Services are REQUIRED to understand and handle the STAR Specific SOAP Faults.
All STAR soap fault error codes are REQUIRED to be be prefixed with STAR: and the appropriate STAR error code. i.e. STAR:Invalid Structure
All STAR soap fault error codes are REQUIRED to appear in the standard SOAP:Fault block.
SOAP Faults are for Critical Processing errors only. Informational or warning errors should not be sent as a SOAP Fault.
WS-Security errors must send the appropriate WS-Security SOAP Fault for the authorization being used.
ConfirmBOD reason codes that are sent at the Warning or Informational status, SHOULD NOT trigger a resending of the BOD.
All implementations are REQUIRED to send information over HTTPS.
All services and clients must be compliant to the general Security requirements outlined by the WS-I Basic Security Profile 1.0.
All implementations are required to support Username/Password for authentication.
