A glossary is a list of terms in a particular domain of knowledge with the definitions for those terms. Traditionally, a glossary appears at the end of a book and includes terms within that book which are either newly introduced or at least uncommon.
This article identifies and explains format rules, style rules, and lexicographic conventions that have been shown to improve clarity and precision in a technical glossary. Rationale for the rules of language, presentation, and style are examined. The need to allow flexibility in following the rules is discussed in terms of strengthening the technical merit and vitality of the glossary. This article also describes the computer-display techniques and file-management system used in committee to develop U.S. Federal Standard 1037C, Glossary of telecommunication terms, and to display the results both in the meeting room and on the Internet between meetings.
Comprehensive list of adaptive technology devices with detailed descriptions and examples of how they are used. Covers Alternative Keyboards, Alternative Mouse Systems, Braille Embosser and Text to Braille Conversion, Refreshable Braille Displays, Screen Magnifiers, Screen Readers and Talking Browsers, Text-to-Speech Systems, Animated Signing Characters (Signing Avatars) to name but a few.
If a ligature falls in a paragraph and no one notices, does it make a sound? Or an impression? When people are no longer aware of old 'standard' typographic conventions and they've lost their meaning, does it make them archaic?
Glossaries are lists of specialized word definitions contained in technical documentation that can assist the nontechnical user to comprehend fully the technical topic at hand. In a joint project with SAS Institute, I sought to discover how glossaries were first developed, what guidelines are available for technical writers in the writing of glossaries, and what rhetorical technique might be of value for glossary writers. I found that glossaries are much more than simple word lists; they are, in fact, an opportunity for the technical writer to outline and protect the parameters of technical discourse between a company and its customers across multiple communications channels, and different languages. In an increasingly global technical environment, an explicit connection between the rhetorical technique of definition and the writing of glossary definitions should be made to aid technical writers in this task.
There is considerable confusion in the marketplace regarding the definition of various information management terms. The scope and role of specific information systems is particularly blurry, in part caused by the lack of consensus between vendors. With the aim of lessening this confusion, this briefing provides an at-a-glance definition of terms for a range of information systems.
The European Association for Terminology (EAFT) was formed in 1996 and the first few years of its existence were largely taken up with organisational issues. Recently, however, the EAFT has become more active setting up a European Terminology Information Server (ETIS) and co-organising conferences. The EAFT has also established a number of special interest groups, including SIGs in terminology training and in minority languages.
In projects like 'Wikipedia', collaborative work also necessitates a common language. This was one of the reasons why a 'Wiktionary' or a 'Wikiwoerterbuch' came into being. Thus, the open source community has already set out to develop ideas for the management of terminology and its implementation.
A glossary is an alphabetically arranged list of terms, with a definition or an explanation of each term. A term can be a single word or many words. Typically, in a printed document, the glossary is at the end of the document. Usually, in online help, each term in a topic, or the first instance of a term, has a popup that explains the term.
This glossary provides an explanation to many of the terms frequently used in connection with translation and interpreting. Whether you need to communicate effectively with translators or translation companies, or just want to know what Unicode or translation memory are all about, you’ll find the answers here.
Glossaries can be quite difficult to write, mainly because some definitions require so much research. While many definitions can be found online, others cannot. For these, you will have to read standards, Requests for Comments (RFCs), and books—a lot of work for a three- or four-line definition!
We wanted to provide a comprehensive references of elements that are new or have been redefined in HTML5, so we've created a glossary. The purpose of the glossary is simple: we’re going to give you a breakdown of all the elements within the spec in clear, bite-sized chunks.
It is important to recognize that because we all differ in our experience and background the learning process is different for each of us. Consequently, in our documentation we should by to put users on an equal footing by, for example, clearly and exactly defining terms we use and including a glossary. We can also put everyone on an equal footing by using 'bridges to understanding,' from analogies, examples, and metaphors to mnemonic strategies. For overall comprehension, we can employ 'frameworks,' from conceptual maps to road maps, that give patterns of meaning to what we say.
This glossary is intended to foster development of a shared vocabulary within the new and rapidly evolving field of information architecture. It should serve as a valuable reference for anyone involved with or interested in the design of information architectures for web sites, intranets and other information systems.
In an attempt to summarize the relationship among various metadata formats and how they relate to building Internet systems I wrote a glossary. I then ordered and tied the terms together with a bit of narrative to explain the relationships among the terms.
The easiest way to gain the respect of programmers is to learn to speak their language. If you can do that, they’ll inevitably recognize the effort you've invested in learning to appreciate their work and will treat you as an equal thereafter. With that goal in mind, I present this glossary of key programming terms you should master.
Here is a summary of a survey that I conducted in April 1999. These results reflect replies received as of 10 June 1999.
Inter-operability is defined as the ability of two or more systems or components to exchange information and to use the information that has been exchanged (source: IEEE Standard Computer Dictionary). Achieving inter-operability of computer-systems and software can consume a significant fraction of the Information Technology budgets of large corporations, so it is an important problem.
The following glossary lists and explains usability terms, which are relevant for the SAP software world. The information was taken from several sources and adapted to the needs of this glossary. Among the sources are: www.whatis.com, the book authored by Larry Constantine and Lucy Lockwood 'Software for use: a practical guide to models and methods of usage-centered design', the book authored by JoAnn Hackos and Janice Reddish 'User and Task Analysis for Interface Design', information contained in articles and guidelines in the SAP Design Guild, own contributions (a.o. photos and graphics).