[standards-jig] Jabber Icons (JEP-0038)
theo at theoretic.com
Fri Jul 19 16:59:23 UTC 2002
Ben Schumacher wrote:
> On Fri, 19 Jul 2002, Sebastiaan 'CBAS' Deckers wrote:
>>I'm also in favour of leaving it up to the developer to choose a
>>dataformat for icons. The multiple <graphics> tags are a great idea.
> If we were to do this, I would push to add an attribute to the <graphic>
> of type, where the MIME type could be specified. This would save
> developers from having to read the CDATA from every graphic tag, and
> compare the extension on the file to see if they are able to display that
> specific graphic.
Yep, if it ends up that multiple graphic formats will be allowed, then I
will have a 'type' attribute for the MIME type of the file.
>>For those interested, I created a few sample packages, available at:
>>Adam Theo helped with some changes to the icondef.xml: no more <alt>
>>tags but multiple <text> tags, file begins with <?xml...>
>>I'm not an XML expert so if someone could check those files and tell me
>>if they're ok, I'd appreciate it!
Thanks, CBas, for doing this, BTW!
> If the spec is revised to remove the <alt> tags, then we do need another
> way to specify in the XML document what should be the "default" text
> version of the icon, and what will be sent out by the client.
Yes, you are correct. I'm trying to decide upon either having the client
use the first <text> tag it comes accross (if order of XML nodes is
preserved in Jabber and XML Processors in general), or having a simple
'default' attribute that the intended default <text> tag will have set
/\ Adam Theo, Age 23, Tallahassee FL USA
//\\ Email & Jabber: theo at theoretic.com
// \\ (Boycotting AOL, therefore no AIM or ICQ)
// || \\ Theoretic Solutions: http://www.theoretic.com
|| "Building Ideas by Bringing them Together"
|| Jabber Protocol: http://www.jabber.org
|| "The Next Generation Communications Protocol"
|| "A Free-Market Socialist Patriotic American Buddhist"
More information about the Standards