[HTML 4.0 draft] (further) comments on ACRONYM

Aymeric Poulain Maubant (Aymeric.PoulainMaubant@enst-bretagne.fr)
Thu, 10 Jul 1997 16:35:11 +0200

Message-Id: <199707101435.QAA18931@melimelo.enst-bretagne.fr>
From: Aymeric Poulain Maubant <Aymeric.PoulainMaubant@enst-bretagne.fr>
To: www-html@w3.org
Subject: [HTML 4.0 draft] (further) comments on ACRONYM
Date: Thu, 10 Jul 1997 16:35:11 +0200

Numerous comments have already been done here on the ACRONYM element.
It still seems to me that this element misses an attribute... But
first of all, the relevant extract from the draft :


  The ACRONYM element allows authors to clearly indicate a sequence 
  of characters that compose an acronym [...] 

  Here are some sample acronym definitions: 

  <ACRONYM title="World Wide Web">WWW</ACRONYM>
     title="Soci&eacute;t&eacute; Nationale de Chemins de Fer">


The missing attribute should be something like 'acr' (short
for acronym, but a better choice may exist). The following
sequence of HTML code wouldn't then be interpreted as such 
by the user agent (because of the presence of the 'acr' attribute) :

     title="Soci&eacute;t&eacute; Nationale de Chemins de Fer">
     title="Syst&egrave;me Naturel de Cryptologie F&eacute;roce">

and then, the following sequences of HTML code would be interpreted
as expected :

  The <ACRONYM acr="sncf"></ACRONYM> is a Society dealing with
  trains, railways, cows and trainspotting, while the <ACRONYM
  acr="sncf2"></ACRONYM> is a method for crypting documents in
  such a manner that even 1000 DEC Alphas working together during
  1000 years wouldn't been enough to decrypt the document. We will
  now deal with the <ACRONYM acr="sncf"></ACRONYM>. blah blah blah
  and oer use of the "sncf" acronym blah blah blah

Two considerations are in the previous paragraph : 1/ saving of
bandwidth when using an acronym many times througout a (bunch of)
document(s) ; 2/ distinguishing between identical acronyms referring
to diferrent objects.

The above solution is not elegant. But despite of this, I think
we still should consider the above two points.

An more elegant solution may be an acronym dictionnary obtainable via
a LINK instance, and an other tag for referencing entries in the
dictionnary. Something like :

  acr CDATA #IMPLIED;    -- reference to an acronym dictionnary --
  %attrs;                -- %coreattrs, %i18n, %events --

  The <ACROSHORT acr="sncf"> owns <ACROSHORT acr="tgv"> which are
  widely used within the <ACROSHORT acr="eec">.