[JDEV] Emoticons: guidelines

Tue Apr 23 12:42:50 CDT 2002

Uh, yeah ... I guess we can reimplement the functionality provided
by HTML with our own invention.  Because we're not constrained by
two companies trying to outdo each other with the industry voting on
standards, we may even be able to beat HTML at its own game.  Hmm. . .
I dunno ... maybe. . .

 - Dave

David Waite wrote:
> 
> Dave wrote:
> 
> >As you all saw, my initial proposal was purely receiver-based (i.e.,
> >the receiving program converted anything "interesting"-looking into
> >an icon), but it looks to me like you're all trying to figure out some
> >standard way of integrating non-text elements into messages :-(
> >
> >In that case, my proposal is simple - use an embedded element:
> ><message to="dave at dave.tj">This is a <x xmlns="html"><img src="http://dave.tj:8080/icons/envelope.png" alt="message"/></x> containing <x xmlns="html"><img src="http://dave.tj:8080/icons/2emoticons.png" alt="two emoticons"/></x>.</message>
> >
> >Any new client (text-only or non-text-only) will be able to support
> >this quite easily, and any existing client won't be too difficult to
> >modify to accomodate this convention.  In other words, it has all the
> >advantages of HTML ... because ... ahem ... it ... well ... _is_ HTML ;-)
> >
> Another option would be to use namespaces to embed another type of data 
> within the message, i.e.
> 
> <message to="dave at dave.tj"><html xmlns="http://www.w3.org/TR/rec-xhtml" xmlns:ex='emoticon-namespace'>This is a <ex:message/> containing <ex:two-emoticons/>.</html></message>
> 
> But this has the disadvantage of not being visible on non-emoticized 
> clients <ex:smiley/>.
> 
> -David Waite
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 