WS-I Basic Profile Version 1.1 - instructional media + magic

More documents

Recommendations

Info

... CORRECT: ... 4.2.3 WSDL Import location Attribute Structure WSDL 1.1 is not clear about whether the location attribute of the wsdl:import statement is required, or what its content is required to be. R2007 A DESCRIPTION MUST specify a non-empty location attribute on the wsdl:import element. Although the wsdl:import statement is modeled after the xsd:import statement, the location attribute is required by wsdl:import while the corresponding attribute on xsd:import, schemaLocation is optional. Consistent with location being required, its content is not intended to be empty. 4.2.4 WSDL Import location Attribute Semantics WSDL 1.1 is unclear about whether WSDL processors must actually retrieve and process the WSDL document from the URI specified in the location attribute on the wsdl:import statements it encounters. R2008 A CONSUMER MAY, but need not, retrieve a WSDL description from the URI specified in the location attribute on a wsdl:import element. C The value of the location attribute of a wsdl:import element is a hint. A WSDL processor may have other ways of locating a WSDL description for a given namespace. 4.2.5 Placement of WSDL import Elements From www.ws-i.org/Profiles/BasicProfile-1.1.html 28 8 February 2008
Example 3 in WSDL 1.1 Section 3.1 causes confusion regarding the placement of wsdl:import. R2022 When they appear in a DESCRIPTION, wsdl:import elements MUST precede all other elements from the WSDL namespace except wsdl:documentation. R2023 When they appear in a DESCRIPTION, wsdl:types elements MUST precede all other elements from the WSDL namespace except wsdl:documentation and wsdl:import. For example, INCORRECT: ... .... ....... CORRECT: ... From www.ws-i.org/Profiles/BasicProfile-1.1.html 29 8 February 2008
Page 1 and 2: Basic Profile Version 1.1 Final Mat
Page 3 and 4: of contributors to the work. If the
Page 5 and 6: 4.7.9. One-Way Operations 4.7.10. N
Page 7 and 8: When possible, the Profile makes st
Page 9 and 10: • xsi - "http://www.w3.org/2001/X
Page 11 and 12: • MESSAGE - protocol elements tha
Page 13 and 14: o E0011 - Transfer-Encoding - The s
Page 15 and 16: CORRECT: Here is some data with
Page 17 and 18: Both SOAP and this Profile use the
Page 19 and 20: soap:Client Invalid message format
Page 21 and 22: 3.4 Use of SOAP in HTTP The followi
Page 23 and 24: R1111 An INSTANCE SHOULD use a "200
Page 25 and 26: conformant. While Cookies thus may
Page 27: R2803 In a DESCRIPTION, the namespa
Page 31 and 32: 4.2.9 Acceptable WSDL Character Enc
Page 33 and 34: Requiring a targetNamespace on all
Page 35 and 36: An "rpc-literal binding" is a wsdl:
Page 37 and 38: The equivalent implicit qualificati
Page 39 and 40: WSDL 1.1 does not clearly state how
Page 41 and 42: R2709 A wsdl:portType in a DESCRIPT
Page 43 and 44: In a document-literal SOAP binding,
Page 45 and 46: There is inconsistency between the
Page 47 and 48: However, it does not explicitly sta
Page 49 and 50: There is no correlation between the
Page 51 and 52: The following specifications (or se
Page 53 and 54: mechanisms used to describe Web ser
Page 55 and 56: R5001 If an INSTANCE requires the u
Page 57 and 58: • E0014 - Validation mode - wheth
Page 59: (IBM), Daniel Foody (Actional Corpo

WS-I Basic Profile Version 1.1 - instructional media + magic

Create successful ePaper yourself

Delete template?

Save as template?