This flag causes a DMS to exclude all DLNA-defined attributes and parameters in the DIDL-Lite responses given by the Browse or Search UPnP actions, as specified by [UPnP].

Value: %x4

This flag affects the response of UPnP Actions: ContentDirectory:Browse, ContentDirectory:Search, and ConnectionManager:GetProtocolInfo.

Note The dlna:profileID and xmlns:dlna attributes MUST NOT be included in the upnp:albumArtURI nodes.

 <upnp:albumArtURI dlna:profileID="JPEG_SM" xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/"></upnp:albumArtURI>

The following content feature flags MUST also be removed from the protocolInfo attribute, as defined in [UPNPCDS1] section 6, of res elements:







     <res duration="0:03:20.000" bitrate="24000" protocolInfo="http-get:*:audio/mpeg:DLNA.ORG_PN=MP3;DLNA.ORG_OP=01;DLNA.ORG_FLAGS=01500000000000000000000000000000" sampleFrequency="44100" bitsPerSample="16" nrAudioChannels="2" microsoft:codec="{00000055-0000-0010-8000-00AA00389B71}" xmlns:microsoft="urn:schemas-microsoft-com:WMPNSS-1-0/"></res>

Because some devices fall down if the string DLNA exists in the protocol response, the WMC_COMPAT_EXCLUDE_DLNA_1_5 compatibility flag MUST be set to indicate that the specified attributes have not been included in the upnp:albumArtURI and res nodes. Setting this compatibility flag causes the server to not include the DLNA string as specified in the XML response.

Moreover, because DLNA support is non-existent if the WMC_COMPAT_INCLUDE_RTSP_FOR_VIDEO flag has been set, it MUST be ignored. By setting this flag, RTSP-based URLs will be excluded from res nodes in the case of video content.

Note In order to preserve backwards compatibility, when the WMC_COMPAT_EXCLUDE_RTSP flag is included within the descriptor <desc> tag, it can be escaped as described in [MS-DLNHND] section

In the case of the UPnP action ConnectionManager:GetProtocolInfo, all format support information MUST NOT contain protocol information that announces DLNA profiles, as specified in [DLNA].


Note The XML tags can be escaped, as described in section 3.1 of this document, when this compatibility flag is used.