Capabilities Document enhancements for SLD-WMS

From SLD Spec:
6.7. Enhancements to WMS GetCapabilities The GetCapabilities request supported by a WMS must return enough information for a client to construct further, valid requests. For example, the capabilities of a WMS includes what named layers are known to a WMS. A GetMap request is not valid if it references a named layer not known to the WMS. To ensure valid interaction with a range of WMSes, including the integrated and component WMS described above, the capabilities response has been enhanced. Specifically it can describe the following information: 1. Does the WMS provide SLD support? 2. Can a client use HTTP POST (with an embedded SLD) and/or HTTP GET (with an SLD or SLD_BODY parameter) to issue a request? 3. Does the WMS support user-defined layers? 4. Does the WMS support user-defined styles? 5. Can the WMS be 'directed' to remote OWS services (i.e., does the WMS support the REMOTE_OWS_SERVICE and REMOTE_OWS_URL parameters in HTTP-GET requests and the RemoteOWS attribute within an SLD)? 6. Does the WMS support the DescribeLayer request? The fact that a WMS may not support named layers and named styles is indicated by not returning any Layer elements when describing its capabilities. This approach makes it possible to support user-defined styles without supporting user-defined layers. This situation is likely to be most prevalent with component WMSes that are used solely to render remote features. However, it should be noted that this description of the capabilities of a WMS makes no explicit mention of 'integrated' and 'component' types.