More complete service definition for WS / SOAP exchange required

The current WS exchange specification is only a rudimentary fragment of what would be needed to properly set up DATEX II exchange connections via WS. Just some examples:
- the client should be able to query configuration information (e.g. which publications are provided, are extension used, etc.)
- there should be support for catalogues and filtered / partial subscription
- a detailed specification plus WSDL of the subscription interface is missing
- apllication level push/pull should be decoupled from low level SOAP connection establishment, i.e. a DATEX push supplier should be able to work as a SOAP client as well as a SOAP server (helper functions like polling or blocking-pull should be tarnspartent to the application and encapsualted in the exchange layer)
- lifecycle magament requires much more refined specification, especially in conjunction with filters
- more precise heartbeat & link monitoring specs required plus better modelling of error handling
- clearer spec how to operate in security restricted environments (HTTPS/SSL/TLS, IPsec, WS -Securirty, etc.)
- a lot more needs to be considered, theser were just a few obvious examples!