- test
case
-
From W3C QA - Quality
Assurance glossary (2003-09-06) | Glossary for this
source
An individual test that corresponds to a
test purpose, which in turn maps back to the assertion(s), and
finally the spec.
- test
purpose
-
From W3C QA - Quality
Assurance glossary (2003-09-06) | Glossary for this
source
An explanation of why the test was written,
and must map directly to one or more test assertions.
- test
requirement
-
From W3C QA - Quality
Assurance glossary (2003-09-06) | Glossary for this
source
Same as test assertion
- test
suite
-
From W3C QA - Quality
Assurance glossary (2003-09-06) | Glossary for this
source
A set of documents and tools providing tool
developers with an objective methodology to verify the level of
conformance of an implementation for a given standard
- testability
-
From QA Framework:
Specification Guidelines (2005-08-17)
| Glossary
for this source
A proposition is testable if there is such
a procedure that assesses the truth-value of a proposition with a
high confidence level.
- TEX
-
From Mathematical
Markup Language (MathML) Version 2.0 (2001-02-21) |
Glossary for this
source
A software system developed by Professor
Donald Knuth for typesetting documents.
- text
-
From Extensible Markup Language
(XML) 1.1 (2004-02-04) |
Glossary for this
source
A parsed entity contains text, a sequence
of characters, which may represent markup or character data.
- text
-
From User Agent
Accessibility Guidelines 1.0 (2002-12-17) |
Glossary for this
source
In this document, the term "text" used by
itself refers to a sequence of characters from a markup language's
document character set. Refer to the "Character Model for the World
Wide Web " [CHARMOD] for more information about text and
characters. Note: This document makes use of other terms that
include the word "text" that have highly specialized meanings:
collated text transcript, non-text content, text content, non-text
element, text element, text equivalent, and text transcript.As used
in this document a "text element" adds text characters to either
content or the user interface. Both in the Web Content
Accessibility Guidelines 1.0 [WCAG10] and in this document, text
elements are presumed to produce text that can be understood when
rendered visually, as synthesized speech, or as Braille. Such text
elements benefit at least these three groups of users:
visually-displayed text benefits users who are deaf and adept in
reading visually-displayed text;synthesized speech benefits users
who are blind and adept in use of synthesized speech;braille
benefits users who are blind, and possibly deaf-blind, and adept at
reading braille.A text element may consist of both text and
non-text data. For instance, a text element may contain markup for
style (e.g., font size or color), structure (e.g., heading levels),
and other semantics. The essential function of the text element
should be retained even if style information happens to be lost in
rendering.A user agent may have to process a text element in order
to have access to the text characters. For instance, a text element
may consist of markup, it may be encrypted or compressed, or it may
include embedded text in a binary format (e.g., JPEG)."Text
content" is content that is composed of one or more text elements.
A "text equivalent" (whether in content or the user interface) is
an equivalent composed of one or more text elements. Authors
generally provide text equivalents for content by using the
conditional content mechanisms of a specification.A "non-text
element" is an element (in content or the user interface) that does
not have the qualities of a text element. "Non-text content" is
composed of one or more non-text elements. A "non-text equivalent"
(whether in content or the user interface) is an equivalent
composed of one or more non-text elements.In this document, a "text
decoration" is any stylistic effect that the user agent may apply
to visually rendered text that does not affect the layout of the
document (i.e., does not require reformatting when applied or
removed). Text decoration mechanisms include underline, overline,
and strike-through.A text transcript is a text equivalent of audio
information (e.g., an audio-only presentation or the audio track of
a movie or other animation). It provides text for both spoken words
and non-spoken sounds such as sound effects. Text transcripts make
audio information accessible to people who have hearing
disabilities and to people who cannot play the audio. Text
transcripts are usually created by hand but may be generated on the
fly (e.g., by voice-to-text converters). See also the definitions
of captions and collated text transcripts.
- text
-
From Extensible Markup
Language (XML) 1.0 (2000-10-06) |
Glossary for this
source
A parsed entity contains text, a sequence
of characters, which may represent markup or character data.
-
text content, non-text content,non-text
-
From User Agent
Accessibility Guidelines 1.0 (2002-12-17) |
Glossary for this
source
As used in this document a "text element"
adds text characters to either content or the user interface. Both
in the Web Content Accessibility Guidelines 1.0 [WCAG10] and in
this document, text elements are presumed to produce text that can
be understood when rendered visually, as synthesized speech, or as
Braille. Such text elements benefit at least these three groups of
users: visually-displayed text benefits users who are deaf and
adept in reading visually-displayed text;synthesized speech
benefits users who are blind and adept in use of synthesized
speech;braille benefits users who are blind, and possibly
deaf-blind, and adept at reading braille.A text element may consist
of both text and non-text data. For instance, a text element may
contain markup for style (e.g., font size or color), structure
(e.g., heading levels), and other semantics. The essential function
of the text element should be retained even if style information
happens to be lost in rendering.A user agent may have to process a
text element in order to have access to the text characters. For
instance, a text element may consist of markup, it may be encrypted
or compressed, or it may include embedded text in a binary format
(e.g., JPEG)."Text content" is content that is composed of one or
more text elements. A "text equivalent" (whether in content or the
user interface) is an equivalent composed of one or more text
elements. Authors generally provide text equivalents for content by
using the conditional content mechanisms of a specification.A
"non-text element" is an element (in content or the user interface)
that does not have the qualities of a text element. "Non-text
content" is composed of one or more non-text elements. A "non-text
equivalent" (whether in content or the user interface) is an
equivalent composed of one or more non-text elements.
- text
decoration
-
From User Agent
Accessibility Guidelines 1.0 (2002-12-17) |
Glossary for this
source
In this document, a "text decoration" is
any stylistic effect that the user agent may apply to visually
rendered text that does not affect the layout of the document
(i.e., does not require reformatting when applied or removed). Text
decoration mechanisms include underline, overline, and
strike-through.
- text
transcript
-
From User Agent
Accessibility Guidelines 1.0 (2002-12-17) |
Glossary for this
source
A text transcript is a text equivalent of
audio information (e.g., an audio-only presentation or the audio
track of a movie or other animation). It provides text for both
spoken words and non-spoken sounds such as sound effects. Text
transcripts make audio information accessible to people who have
hearing disabilities and to people who cannot play the audio. Text
transcripts are usually created by hand but may be generated on the
fly (e.g., by voice-to-text converters). See also the definitions
of captions and collated text transcripts.
- text-To-Speech
-
From Speech
Synthesis Markup Language (SSML) Version 1.0 (2004-09-07)
| Glossary for
this source
The process of automatic generation of
speech output from text or annotated text input.
- the
empty string
-
From XML Schema Part 2:
Datatypes (2001-05-02)
| Glossary
for this source
the empty set;
- third-party
-
From XML Linking Language
(XLink) (2001-06-27) |
Glossary for this
source
If neither the starting resource nor the
ending resource is local, then the arc is a third-party arc.
- throw
-
From Voice
Extensible Markup Language (VoiceXML) Version 2.0 (2004-03-16)
| Glossary for
this source
An element that fires an event
.
- time
parameters
-
From User Agent
Accessibility Guidelines 1.0 (2002-12-17) |
Glossary for this
source
This document includes requirements (see
checkpoints 2.4, 4.4, 4.5, and 4.9) for control of some time
parameters. The requirements are for time parameters that the user
agent recognizes and controls. This document does not include
requirements for control of time parameters managed on the
server.
- TLS
-
From XML Key
Management (XKMS 2.0) Requirements (2003-05-05)
| Glossary for this
source
Transport Layer Security, a protocol layer
designed to provide message integrity and confidentiality for a
message during transit between two endpoints. An earlier version is
known as SSL, the Secure Socket Layer [TLS].
- tobin
-
From Glossary of W3C Jargon (2003-03-11) | Glossary for this
source
(1) Maurice J. Tobin (1901-1953), Boston
politician, after whom a
highway
bridge between Chelsea and Charlestown (MA) was named. (2) A
W3C teleconference bridge with 18 line capacity.
- token
-
From RDF Semantics (2004-02-10) |
Glossary for this
source
(n.) A particular physical inscription of a symbol or
expression in a document. Usually contrasted with
type ,
the abstract grammatical form of an expression.