Tweet
UPnP compliance bug
Hi,
Thanks for making Asset such a good product.
Not certain this forum is the right place to file such bugs, but it looks like there's an XML compliance issue in Asset's current version.
The UPnP spec clearly states the <dc:title> element should be the first child element of <container> or <item> elements in content directory service DIDL-Lite responses.
Using Asset UPnP 4.1, I may get the following XML answer...
... where the first child element is <upnp:searchClass> rather than <dc:title> :-(
This, for sure, may break some controller implementations. Let me know if there's a better place for raising that kind of issue.
Thanks,
Denis
Thanks for making Asset such a good product.
Not certain this forum is the right place to file such bugs, but it looks like there's an XML compliance issue in Asset's current version.
The UPnP spec clearly states the <dc:title> element should be the first child element of <container> or <item> elements in content directory service DIDL-Lite responses.
Using Asset UPnP 4.1, I may get the following XML answer...
Code:
<DIDL-Lite xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/">
<container id="0" parentID="-1" childCount="3" restricted="0" searchable="0">
<upnp:searchClass includeDerived="1">object</upnp:searchClass>
<dc:title>root</dc:title>
<upnp:artist>Unknown</upnp:artist>
<upnp:genre>Unknown</upnp:genre>
<upnp:album>Unknown</upnp:album>
<dc:creator>Unknown</dc:creator>
<upnp:class>object.container</upnp:class>
</container>
</DIDL-Lite>
This, for sure, may break some controller implementations. Let me know if there's a better place for raising that kind of issue.
Thanks,
Denis
Comment