feature request

[simoncn]

(09-02-2012 09:07)psme Wrote:  Thanks! That's exactly what I wanted! Use the <desc> in <item> to provide detail song tag pair to a smart Controller.

For example, I add a user tag name "Audio Format" and set the value to "Super Audio CD" for SACD ripped track, set it to "Vinyl ripped" for song ripped from LP, etc.

In that case, the smart UPnP server can return all tag values in a song include this user tag "Audio Format", within song's <item> section...

For example, for a song "Rolling In the Deep", the <desc> section in the song <item> section may look like:

<desc id="Artist Name" nameSpace="minimServer:UserTag">Adele</desc>
<desc id="Track Title" nameSpace="minimServer:UserTag">Rolling In The Deep</desc>
<desc id="Album Title" nameSpace="minimServer:UserTag">Adele Best Collection</desc>
<desc id="Date" nameSpace="minimServer:UserTag">2014 06 32</desc>
<desc id="Track Number" nameSpace="minimServer:UserTag">12</desc>
<desc id="Disc Number" nameSpace="minimServer:UserTag">2</desc>
<desc id="Genre" nameSpace="minimServer:UserTag">R&B</desc>
<desc id="Audio Format" nameSpace="minimServer:UserTag">Super Audio CD</desc>

This is exactly what I don't want to do: invent a non-standard proprietary namespace and XML schema. The way this information is sent should be defined formally as part of an industry standard. The definition would be similar to what Microsoft has done in the "Microsoft Extensions to UPnP Metadata" section of this document. By making this a standard, all servers can provide this information in the same format, and all "smart" controllers can work correctly with all servers.