Re: Phrase markup (was Re: Aural Cascading Style Sheets)

Ian Graham (ianweb@smaug.java.utoronto.ca)
Fri, 10 Jan 1997 15:37:57 -0500 (EST)


From: ianweb@smaug.java.utoronto.ca (Ian Graham)
Message-Id: <199701102037.PAA09475@smaug.java.utoronto.ca>
Subject: Re: Phrase markup (was Re: Aural Cascading Style Sheets)
To: Chris.Lilley@sophia.inria.fr (Chris Lilley)
Date: Fri, 10 Jan 1997 15:37:57 -0500 (EST)
Cc: www-html@www10.w3.org
In-Reply-To: <9701101907.ZM14920@grommit.inria.fr> from "Chris Lilley" at Jan 10, 97 07:07:42 pm

Is there not a way to do this with LINK and REL/REV -- that is,
define an external document that contains acronym and/or 
abbreviation definitions?  For example:

   <LINK HREF="acronyms_file" REL="acronym">
   <LINK HREF="abbrev_file" REL="abbrev">

A browser could load these file,s and use their content to map 
acronyms or abbreviations to full meanings.  It would not 
eliminate the need for (or advantages of) semantic attribute 
values,  but would perhaps be easier to manage on the authoring 
side, in some cases.  Of course, you need a format for
the acronym file -- this could either be a simple HTML
document, using lines like 

<acronym for="Cascading Style Sheets">CSS</acronym>

to define global acronyms, or a database-style format, such as: 
as:

  <ACRONYM>
     <SHORT>CCS</SHORT>
     <LONG>Cascading Style Sheets</LONG>
  </ACRONYM>

Pretty small DTD, I'd wager ;-)

Ian
--
Ian Graham ........................................ ian.graham@utoronto.ca
Information Commons                                      Tel: 416-978-4548
University of Toronto                                    Fax: 416-978-7705

> 
> On Jan 10, 10:05am, Dave Raggett wrote:
> 
> > For instance, indicate that something is an acronym, abbreviation,
> > a person's name etc. It makes sense in some cases to specify the
> > long form as an attribute, e.g. one could write
> >
> >  <acronym for=3D"Cascading Style Sheets">CSS</acronym>
> >  <abbrev for=3D"etcetera">etc.</abbrev>
> >  <person fullname=3D"David St.John Raggett">Dave</person>
> >
> > Note that GUI browsers could in principle use these attributes for
> > balloon help when the mouse is held over the word in question.
> 
> Yes, good point. I recall lking the ability to add this level of simple
> semantic markup in HTML 3.0draft.
> 
> In general, it seems that CSS is starting to need access
> to the content of attributes, be they alt, for, lang, or whatever.
> >
> > If a name is from a different language then different pronunciation
> > rules will apply, this can be handled via the language attribute, e.g.
> >
> >  <person lang=3Dfr>Jean Fran&ccedil;ois Dupont</person>
> 
> Yes, it is worth stressing that language is a much more important
> tag or attribute when using speech synthesis. It is easy to tell
> que j'ecrire en Fran=E7ais pour un peu, and then switch to back to
> English. A speech synth would get very confused without explicit markup.
> 
> > For really hard to pronounce phrases, perhaps its worth considering
> > an attribute for specifying the pronunciation using the International
> > Phonetic Alphabet. Can anyone give me a lead on how to represent
> > IPC characters conveniently using ASCII?  Is there an agreed set
> > of SGML entities?
> 
> No. I checked the full set of  8879:1986 defined entities. There is
> however a block of characters for IPA in Unicode, from 0250 to 02AF,
> so (assuming the attributes are declared CDATA and not NAME or
> something) they could be used in an attribute by any Coagar-like or
> i18N-aware DTD that allows characters with code-points above 255.
> 
> -- =
> 
> Chris Lilley, W3C                          [ http://www.w3.org/ ]
> Graphics and Fonts Guy            The World Wide Web Consortium
> http://www.w3.org/people/chris/              INRIA,  Projet W3C
> chris@w3.org                       2004 Rt des Lucioles / BP 93
> +33 (0)4 93 65 79 87       06902 Sophia Antipolis Cedex, France
> 
> --PART-BOUNDARY=.19701101907.ZM14920.inria.fr--
>