Notes from 07 March 2003 Glossary meeting

Present

We gathered for an hour Friday morning to discuss user needs, processes, and data requirements for glossaries.

mutli-lingual
- translations, comments on translations.
- one concept can have several translations
- EN-US as basis
searchable
- by subsets (e.g., WAI, QA, etc.)
versioning (+history)
context
UTF-8
audience
- Editors
- Readers
- Translators
acronyms and abbreviations
authority --CMN: There may be a many-many mapping between terms and glossary explanations or translations. It would be useful to know not just the original context of an entry, but also who "approves" (i.e. agrees with) a given term-concept pair, or in what circumstances. For example, Sidar is likely to recommend the use or Résumen to translate the term Abstract (a section in each W3C spec). Another group may propose Abstracto. (Currently the two are used). A third group may provide a particular recommendation for one or the other.

Comparison - compare how a term is used in different contexts.
Discovery - discover either a term to use in a context or the definition for a context. Editors often need to find a word to represent an idea that a Working Group is trying to express. Thus, editors may go looking to other specs to find similar terms. Othertimes editors, readers, or translators may wish to find the definition of a term.
Derivation - find a term used in another context and extend it for the purposes of a new context.
Policy making - refering to glossaries to set policy (i.e., these are the terms we are using and how they are defined). Examples of policy - web accessibility or translation services (i.e., for W3C translations our translators in language X should use entries from glossary Y).
Illustration?
Speech Synthesis - if pronunciation information was attached to terms (as in a standard dictionary), a reader could use the data to inform their speech synthesizer.
Cross-referencing

Reader - reads multiple W3C specifications. May wish to compare definitions of terms between specs.
- may be looking for pronunciation information for a term
- may need to convince someone "this is the term to use" (related to policy-making)
Translator - translates one or more W3C specifications from EN-US to another language.
- translates terms, may need to create a new term
- look for recommended term for a concept
- compare with other terms being defined
Editor - is participating in a working group, trying to synthesize the variety of ideas from the group into a set of statements that achieves consensus. will likely need to:
- search for a term to find uses in other specs
- compare definitions of terms
- link to other definitions (and show derivation if want to extend another group's definition)

$Date: 2003/03/18 12:54:23 $ Wendy Chisholm