XSD
IBM and Microsoft (W3C Note) · 1.1
WSDL 1.1
Web service descriptions for SOAP services: types, messages, port types, bindings and services.
About
Most SOAP services publish a WSDL 1.1 document that client generators (wsimport, svcutil, zeep) read. The schema checks its structure.
Good to know
- The embedded XML Schema in types and the SOAP binding extensions are accepted as is; references between messages, port types and bindings are not resolved.
- The example is by xmlvalid.com.
Example document
stock.wsdl · 1.8 KB · valid against this schema
In CI and from code
The same schema by its name, wsdl-1.1, through the API.
npx @xmlvalid/cli validate "**/*.xml" --schema wsdl-1.1
- uses: xmlvalid/validate-action@v1
with:
files: "**/*.xml"
schema: wsdl-1.1
api-key: ${{ secrets.XMLVALID_API_KEY }}
curl https://xmlvalid.com/api/v1/validations \
-H "Authorization: Bearer $XMLVALID_API_KEY" \
-F document={{ $schema->example ?? 'document.xml' }} -F schema=wsdl-1.1
Free accounts get 100 API validations a month. On Pro, a URL monitor can check a published document against this schema every hour and email you when it breaks. More CI setups