On Dec 26, 2007, at 11:13 AM, Peter Saint-Andre wrote:
L.R.N wrote:
OK, you can get some general information from URI. But how about
technical
information, like player name (and version), format (codec/
container),
bitrate, file size, sample rate, channels etc.
Is that of interest to more than 1% of users?
We shouldn't lose track of our extensibility here, either. There's
nothing that says that a XEP-118 publish couldn't have other
information embedded in it, in another namespace:
<iq type='set'
from='[EMAIL PROTECTED]/14793c64-0f94-11dc-9430-000bcd821bfb'
id='tunes123'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<publish node='http://jabber.org/protocol/tune'>
<item>
<tune xmlns='http://jabber.org/protocol/tune'>
...
<technical xmlns='urn:xmpp:tune;technical'>
<codec>BLAH</codec>
<bitrate>192</bitrate>
</technical>
</tune>
</item>
</publish>
</pubsub>
</iq>
So there's no need to redefine the spec every time we come up with
more information we want to be included.
--
Joe Hildebrand
