Standards for Technology in Automotive Retail

 Home -  News Feed 

Appendix A. STAR Level One Check List

As specified by the STAR Transport Guidelines, each transport is to have a interoperability check list that is voluntarily filled out by the implementor. This check list should be sent back to STAR either via electronic format or via email submission. The check lists are a way for the STAR to guage the level of adoption as well as what portions of the specification are being implemented. This information is then used as input back to the Architecture Workgroup for further review and action on updates to the transport specification.

A.1. Check List

This is the STAR Level 1 interoperability check list. Please fill this information out in a spreadsheet, and send back to If the implementation has implemented the rule specified please mark with a Y. If the implementation has not implemented mark with a N. If the rule doesn't apply to your implementation please mark as NA.

Table A.1. STAR Level 1 Check List

RuleDescriptionImplemented (Y, N, NA)
STAR1001All web services must be compliant to the rules and specifications outlined by the WS-I Basic Profile 
STAR1002Appropriate compliance markers are required as specified by the WS-I Conformance Claim Attachment Mechanisms document. 
STAR1003All implementations are required to support Username/Password for authentication 
STAR1004All implementations are REQUIRED to send information over HTTPS 
STAR1005All passwords are required to be sent as plain text 
STAR1008All services and clients must be compliant to the general Security requirements Outlined by the WS-I Basic Security Profile 1.0 .The optional attributes defined in the Profile is also to be relaxed in the STAR Implementation. 
STAR1009All STAR Web Services are REQUIRED to understand and handle the STAR Specific SOAP Faults. 
STAR1010All STAR soap fault error codes are REQUIRED to be be prefixed with STAR: and the appropriate STAR error code. i.e. STAR:Invalid Structure 
STAR1011All STAR soap fault error codes are REQUIRED to appear in the standard SOAP:Fault block. 
STAR1012SOAP Faults are for Critical Processing errors only. Informational or warning errors should not be sent as a SOAP Fault. 
STAR1013ConfirmBOD reason codes that are sent at the Warning or Informational status, SHOULD NOT trigger a resending of the BOD. 
STAR1014WS-Security errors must send the appropriate WS-Security SOAP Fault for the authorization being used. 
STAR1015STAR BOD Specific and Generic Transports must be message level interoperable. 
STAR1016Application level error messages MUST NOT be returned with a SOAP Fault, and MUST be returned using the appropriate BOD. 
STAR1017The service provider must keep track of contents that are deemed to have been received by the client to avoid resending. 
STAR1018A SOAP Header MUST contain one manifest element for each content element in the SOAP body. 
STAR1019A 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. 
STAR1020The client must be able to handle duplicate messages from a service provider.