[standards-jig] JEP0038 (the emoticon spec) Some suggestions

Sebastiaan 'CBAS' Deckers cbas at screaming3d.com
Wed Sep 25 00:24:54 UTC 2002


Mattias Campe wrote:

> - I've used <text xml:lang="en" alt="cat"> instead of just
>   <text lang="en" alt="cat"> because xml:lang seems to be a standard
>   within xml. This xml:lang is constrained of using a two-letter
>   ISO 639 language code or a two-letter ISO 639 language followed by a
>   three-letter ISO 3166 country code or ... (If people would like this
>   idea I'll add a clear explanation on the Wiki site of Theo)

What advantage does this offer compared to the lang attribute we have 
been using the last three months?  It seems like the "right" thing to 
do, but I can't think of a more practical reason.  Is there a conflict 
between the lang attribute and something else?

> - <object> is a html tag which can be used for multimedia purposes and
>   could be used to replace <img>. Because this <object> is more
>   straightforwarded, I would like to use it in this JEP as well.

I think the <graphic/>, <sound/> and <format/> tags were perfectly clear 
in the way they represent the options a client has.  This <object/> tag 
and the format attribute will IMO add ambiguity.  This <object/> tag 
could be confused with the tag defined in HTML (which is in no way similar).

> - the other suggestions can be found at the end of
>   http://www.theoretic.com/?IM_Icons/Styles

Amongst the changes you propose are categories.  This seems like a nice 
idea, allthough I can't imagine people would need *that many* emoticons. 
 It's an implementation choice I guess.
Another thing is the <head/> tag.  What is the reason for this?  It 
doesn't seem to have any functionality.
In the example you've added an <url/> tag.  What is this supposed to 
hold?  (The address of the JEP?)
Why is the name of the author now in a name attribute instead of as the 
element's data?
Please not that the <text/> tags in your example all have the xml:lang 
attribute set.  This leads to problems.  There _must_ be atleast one 
default string.  Adam Theo just didn't find a way to specify this in the 
schema.
What is the point of a language x-ascii?  I don't think it's wise to 
replace one text string with another.  Seems like a nop to me.

--
Sebastiaan Deckers




More information about the Standards mailing list