Alphabetical Links | Abbreviations / Acronyms | References | Contents | Printable Version

WAI Glossary Home

Internal Working Draft, 1 November 2002

Latest version:

http://www.w3.org/WAI/GL/Glossary/printable

Last Updated: $Date: 2002/10/28 18:32:41 $

Editors:

Katie Haritos-Shea , Charles McCathieNevile

This WAI Glossary is dedicated to the Memory of Len Kasday

1. Status Of This Document

This document is an internal working draft published for review and comment, specifically for several WAI working groups. It was created by Harvey Bingham and is currently being worked on as a proposed glossary for use in future versions of the Authoring Tool Accessibility Guidelines [ATAG10], Techniques for Authoring Tool Accessibility [ATAG-TECHS], User Agent Accessibility Guidelines [UAAG10], Techniques for User Agent Accessibility Guidelines [UAAG-TECHS], as well as being a proposed glossary for Web Content Accessibility Guidelines 2.0 [WCAG20] which is a W3C working draft.

The purpose of this combined glossary is to allow comparison of definitions, and potentially to provide a single glossary for all the accessibility guidelines. The Evaluation and Repair group and readers of more than one guideline will benefit from consistent uses of terms.

Comments on this document are welcomed and should be sent to wai-xtech@w3.org - list archives are available at http://lists.w3.org/Archives/Public/wai-xtech for review.

This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". A list of current W3C Recommendations and other technical documents is available.

Publication of this document does not imply endorsement by the W3C, any of its member organisations or working groups.

Translations of this document or of drafts may be available. Further translations are welcome, but prospective translators should ensure that they are familiar with W3C copyright and translation policy.

2. Contents

1. Status Of This Document
2. Contents
3. Introduction
4. How This Glossary Is Organised
5. Alphabetical Links (A to Z)
6. Glossary
7. Abbreviations/Acronyms
8. References

3. Introduction

4. How This Glossary Is Organised

• WCAG10: Web Content Accessibility Guidelines 1.0, 1999-5-5 WCAG 1.0
• WCAG20-Draft: Web Content Accessibility Guidelines 2.0, 2001-0-0 WCAG 2.0
• ATAG10: Authoring Tools Accessibility Guidelines 1.0, 2000-02-03 ATAG 1.0
• UAAG10: Working Draft User Agent Accessibility Guidelines, 2000-07-28 UAAG 1.0

In the glossary terms that follow, the suffix to each term -- one of [WCAG10], [WCAG20], [ATAG10], [UAAG10], [SVG], [SMIL10], [CC/PP], [CSS1], [CSS2], [XHTML10], [HTML40], [HTML401], [XML], [XSL], [XSLT], [PWD-Use-Web1], [P3P10] or [PDF-Tech] -- indicates the source guideline for the following definition. Text of the definition may indicate that that definition applies for the purpose of the document from which it was extracted.

5. Alphabetical Links

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

6. Glossary

Accessibility GENERIC a la Tim's book-glossary

The art of ensuring that, to as large an extent as possible, facilities (such as, for example, Web access) are available to people whether or not they have impairments of one sort or another.

Accessibility [ATAG10] (Also: Accessible [ATAG10])

Within these guidelines, "accessible Web content" and "accessible authoring tool" mean that the content and tool can be used by people regardless of disability.

To understand the accessibility issues relevant to authoring tool design, consider that many authors may be creating content in contexts very different from your own:

• They may not be able to see, hear, move, or may not be able to process some types of information easily or at all;
• They may have difficulty reading or comprehending text;
• They may not have or be able to use a keyboard or mouse;
• They may have a text-only display, or a small screen.

Accessible design will benefit people in these different authoring scenarios and also many people who do not have a physical disability but who have similar needs. For example, someone may be working in a noisy environment and thus require an alternative re of audio information. Similarly, someone may be working in an eyes-busy environment and thus require an audio equivalent to information they cannot view. Users of small mobile devices (with small screens, no keyboard, and no mouse) have similar functional needs as some users with disabilities.

Accessibility Awareness [ATAG10] NEW 01-01-12

An "accessibility-aware" application is one that has been designed to account for authors' differing needs, abilities, and technologies. In the case of authoring tools, this means that (1) care has been taken to ensure that the content produced by user-authors is accessible and (2) that the user interface has been designed to be usable with a variety of display and control technologies.

Accessibility Information [ATAG10] NEW LINKS 01-01-12

"Accessibility information" is content, including information and markup, that is used to improve the accessibility of a document. Accessibility information includes, but is not limited to, equivalent alternative information.

Accessibility Permission [WCAG10] [WCAG20] (PDF-Tech) NEW 01-01-08

A PDF file can be encrypted (PDF 1.1) to protect its contents from unauthorized access. PDF's standard security handler defines a set of access privileges for a document, including privileges such as modifying the document's contents, copying text and graphics from the document, and printing the document. In PDF 1.4, this set includes accessibility permission, which controls whether the contents of the document are available via standard accessibility APIs to screen readers and other assistive technology.

Accessibility Problem [ATAG10] (Also: Inaccessible Markup [ATAG10]) NEW LINKS 01-01-12

Inaccessible Web content or authoring tools cannot be used by some people with disabilities. The Web Content Accessibility Guidelines 1.0 WCAG 1.0 describes how to create accessible Web content.

Accessible [WCAG10] [WCAG20]

Content is accessible when it may be used by someone with a disability.

Accessible [ATAG10] NEW LINKS 01-01-23

See Accessibility [ATAG10].

Accessible Authoring Practice [ATAG10]

"Accessible authoring practices" improve the accessibility of Web content. Both authors and tools engage in accessible authoring practices. For example, authors write clearly, structure their content, and provide navigation aids. Tools automatically generate valid markup and assist authors in providing and managing appropriate equivalent alternatives.

Acronym [WCAG10] [WCAG20] NEW 00-12-13

An identifier formed from some of the letters (often the initials) of a phrase and used as an abbreviation.

Activate [WD-UAAG10-20010409] NEW 01-05-05

In this document, the verb "to activate" means (depending on context) either:

• To execute or carry out one or more behaviors associated with an enabled element.
• To execute or carry out one or more behaviors associated with a component of the user agent user interface.

The effect of activation depends on the type of enabled element or user interface control. For instance, when a link is activated, the user agent generally retrieves the linked Web resource. When a form control is activated, it may change state (e.g., check boxes) or may take user input (e.g., a text entry field).

Active Element [SVG10] NEW 01-01-12

An active element is an element with behaviors that may be activated (or "triggered") either through the user interface or through scripts. Which elements are active depends on the document language and whether the features are supported by the user agent. In SVG documents, for example, active elements include links and element instances with scripts (event handlers) explicitly associated with them (for example, through the various "on" attributes: onactivate etc). Most systems use the content focus to navigate active elements and identify which is to be activated. An active element's behavior may be triggered through any number of mechanisms, including the mouse, keyboard, an Application Programming Interface (API), etc. The effect of activation depends on the element. For instance, when a link is activated, the user agent generally retrieves the linked resource.

Active Element [UAAG10] NEW LINKS 01-01-12

An active element is an element with behaviors that may be activated (or "triggered") either through the user interface or through an API (e.g., by using scripts). Some element instances may be active at times but not at others (e.g., they may be "deactivated" through scripts, or they are only active for a period of time determined by the author). Which elements are active depends on the document language and whether the features are supported by the user agent. In HTML 4.01 HTML4.01 documents, for example, active elements include links, image maps, form controls, element instances with a value for the "longdesc" attribute, and element instances with scripts (event handlers) explicitly associated with them (e.g., through the various "on" attributes). Most systems use the content focus to navigate active elements and identify which is to be activated. An active element's behavior may be triggered through any number of mechanisms, including the mouse, keyboard, an API, etc. The effect of activation depends on the element. For instance, when a link is activated, the user agent generally retrieves the linked web resources. When a form control is activated, it may change state (e.g., check boxes) or may take user input (e.g., a text field). Refer also to the definition of event handler

Accessible design will benefit people in these different authoring scenarios and also many people who do not have a physical disability but who have similar needs. For example, someone may be working in a noisy environment and thus require an alternative re of audio information. Similarly, someone may be working in an eyes-busy environment and thus require an audio equivalent to information they cannot view. Users of small mobile devices (with small screens, no keyboard, and no mouse) have similar functional needs as some users with disabilities.

Active Element [UA Draft] NEWER 01-02-03

An active element is a piece of content with behaviors that may be activated (or "triggered") either through the user interface or through an API (e.g., by using scripts).

What constitutes an active element depends on the content. In HTML 4 [HTML4] documents, for example, active elements include links, image maps, form controls, element instances with a value for the "longdesc" attribute, and element instances with scripts (event handlers) explicitly associated with them (e.g., through the various "on" attributes). The requirements of this document refer only to active elements that may be recognized through markup (and not, for example, through scripts or style sheets). Some element instances may be active at times but not at others (e.g., they may be "deactivated" through scripts, or they may only be active for a period of time determined by the author).

Potential user interaction with a piece of content does not imply that the content constitutes an active element. For example, the user may select text an copy it to the clipboard, but the selected text is not (necessarily) an active element, because the selection is a functionality provided by the user agent. For the purposes of this document, markup languages determine which elements are potentially active elements.

The effect of activation depends on the element. For instance, when a link is activated, the user agent generally retrieves the linked Web resource. When a form control is activated, it may change state (e.g., check boxes) or may take user input (e.g., a text entry field). See also the definition of event handler.

Most systems use the content focus to indicate which active element will be activated on user demand.

ActualText Value [WCAG10] [WCAG20] (PDF-Tech) NEW 01-01-08

Sometimes characters are rendered by graphics commands other than showstring. For instance, an illuminated character may be rendered by an image or a series of graphics commands. In this situations, the Actual Text property is used to identify the character being rendered. This character may be concantentated with adjoining text to form a word.

Adobe Glyph Name [WCAG10] [WCAG20] (PDF-Tech) NEW 01-01-11

The name of a character in the Adobe standard character encodings, in Appendix D of the PDF 1.3 Reference Manual. The encodings list characters, character names, and character codes used in platform standard encodings.

Afford, Affordance NEW 01-04-13 Human Factors & HCI, Al Gilman

An affordance is an effective service delivery; one that makes it into user space where the user can actually use it. Or the effect of the service delivery as observed within user space.

Aging-Related Conditions [PWD-Use-Web1] NEW 01-03-18 Judy's new "How People w/dis Use the Web"

Changes in people's functional ability due to aging can include subtle and/or gradual changes in abilities or a combination of abilities including vision, hearing, dexterity and memory. Any one of these limitations can affect an individual's ability to access Web content.

Alert [ATAG10] NEW 01-01-12

An "alert" draws the author's attention to an event or situation. It may require a response from the author. An alert warns the author that there are problems that need to be addressed. Attracting the author's attention artfully can be challenging, since author perceptions of alerts, prompts, and warnings can influence opinions of the tool and even of accessible authoring.
An Unintrusive Alert is an alert such as an icon, underlining, or gentle sound that can be presented to the author without necessitating immediate action. For example, in some word processors misspelled text is highlighted without forcing the author to make immediate corrections. These alerts allow authors to continue editing with the knowledge that problems will be easy to identify at a later time. However, authors may become annoyed at the extra formatting or may choose to ignore the alerts altogether.
An Interruptive Alert is an informative message that interrupts the editing process for the author. For example, interruptive alerts are often presented when an author's action could cause a loss of data. Interruptive alerts allow problems to be brought to the author's attention immediately. However, authors may resent the constant delays and forced actions. Many people prefer to finish expressing an idea before returning to edit its format.

Alert [UAAG10] NEW 01-01-12

To "alert" means to make the user aware of some event, without requiring acknowledgement. For example, the user agent may alert the user that new content is available on the server by displaying a text message in the user agent's status bar.

Alternative Equivalents for Content [UAAG10] NEW 01-02-03

Since rendered content in some forms is not always accessible to users with disabilities, authors must supply alternative equivalents for content. In the context of this document, the equivalent must fulfill essentially the same function for the person with a disability (at least insofar as is feasible, given the nature of the disability and the state of technology), as the "primary" content does for the person without any disability. For example, the text "The Full Moon" might convey the same information as an image of a full moon when presented to users. Note that equivalent information focuses on fulfilling the same function. If the image is part of a link and understanding the image is crucial to guessing the link target, an equivalent must also give users an idea of the link target. User agents must make the alternative equivalent content available to users or software that require it (in place of and/or in addition to the "primary" content). Alternative representations include text equivalents (long and short, synchronized and unsynchronized) and non-text equivalents (e.g., captions, auditory descriptions, a visual track that shows sign language translation of a written text, etc.).

Alternative Information [ATAG10] NEW LINKS 01-01-13

(Also: Equivalent Alternative [ATAG10] & Text equivalent WC)

Content is "equivalent" to other content when both fulfill essentially the same function or purpose upon presentation to the user. Equivalent alternatives play an important role in accessible authoring practices since certain types of content may not be accessible to all users (e.g., video, images, audio, etc.). Authors are encouraged to provide text equivalents for non-text content since text may be rendered as synthesized speech for individuals who have visual or learning disabilities, as braille for individuals who are blind, or as graphical text for individuals who are deaf or do not have a disability. For more information about equivalent alternatives, please refer to the Web Content Accessibility Guidelines WCAG 1.0 WCAG 1.0.

Alternative Keyboards or Switches [PWD-Use-Web1] NEW 01-03-18 Judy's new "How People w/dis Use the Web"

Alternate keyboards or switches are hardware or software devices used by people with physical disabilities, that provide an alternate way of creating keystrokes that appear to come from the standard keyboard. Examples include keyboard with extra-small or extra-large key spacing, keyguards that only allow pressing one key at a time, on-screen keyboards, eyegaze keyboards, and sip-and-puff switches. Web-based applications that can be operated entirely from the keyboard, with no mouse required, support a wide range of alternative modes of input.

Animation [WCAG10 Tech] NEW 01-03-10

In this document, the term "animation" refers to any visual movement effect created automatically (i.e., without manual user interaction). This definition of animation includes video and animated images. Animation techniques include:

• graphically displaying a sequence of snapshots within the same region (e.g., as is done for video and animated images). The series of snapshots may be provided by a single resource (e.g., an animated GIF image) or from distinct resources (e.g., a series of images downloaded continuously by the user agent).
• scrolling text (e.g., achieved through markup or style sheets).
• displacing graphical objects around the viewport (e.g., a picture of a ball that is moved around the viewport giving the impression that it is bouncing off of the viewport edges). For instance, the SMIL 2.0 [SMIL20] animation modules explain how to create such animation effects in a declarative manner (i.e., not by composition of successive snapshots).

Anonymization [CC/PP] NEW 01-04-23

Hiding the identity of the User as a security precaution.

Applet [WCAG10] [WCAG20] NEW 01-01-11

A Beginning...01-01-25 A Java program inserted into a Web page that relies on a browser to provide the environment in which it can run. Applets are essentially guests of the browser. The browser takes care of their welfare and provides and manages access to the platform specific services.

API's [WCAG10] [WCAG20] NEW 01-01-11

A Beginning...01-01-25 An application programming interface (API) defines how communication may take place between applications.

A device API defines how communication may take place with an input or output device such as a keyboard, mouse, video card, etc.

A standard device API is one that is considered standard for that particular device on a given operating or windowing system.

Application Programming Interface (API) [UAAG10] NEW 01-01-25

An application programming interface (API) defines how communication may take place between applications.

A device API defines how communication may take place with an input or output device such as a keyboard, mouse, video card, etc.

A standard device API is one that is considered standard for that particular device on a given operating or windowing system.

Application Programming Interface, standard input/output/device (API) [UAAG10] Draft NEWER 01-01-25

An application programming interface (API) defines how communication may take place between applications.

As part of encouraging interoperability, this document recommends using standard APIs where possible, although this document does not define in all cases how those APIs are standardized (i.e., whether they are defined by specifications such as W3C Recommendations, defined by an operating system vendor, de facto standards, etc.). Implementing APIs that are independent of a particular operating system (e.g., the W3C DOM Level 2 specifications) may reduce implementation costs for multi-platform user agents and promote the development of multi-platform assistive technologies. Implementing standard APIs defined for a particular operating system may reduce implementation costs for assistive technology developers who wish to interoperate with more than one piece of software running on that operating system.

A "device API" defines how communication may take place with an input or output device such as a keyboard, mouse, video card, etc. A "standard device API" is one that is considered standard for that particular device on a given operating or windowing system.

In this document, an "input/output API" defines how applications or devices communicate with a user agent. As used in this document, input and output APIs include, but are not limited to, device APIs. Input and output APIs also include more abstract communication interfaces than those specified by device APIs. A "standard input/output API" is one that is expected to be implemented by software running on a particular operating system. Standard input/output APIs may vary from system to system. For example, on desktop computers today, the standard input APIs are for the mouse and keyboard. For touch screen devices or mobile devices, standard input APIs may include stylus, buttons, voice, etc. The graphical display and sound card are considered standard ouput devices for a graphical desktop computer environment, and each has a standard API.

Array [WCAG10] [WCAG20] NEW

A Beginning...01-01-25 A set of elements of some type that can be identified by an index, starting in JavaScript at 0, and increasing by 1 for each subsequent member of the array.

7. Abbreviations

8. References

For the latest version of any W3C specification please consult the list of W3C Technical Reports at http://www.w3.org/TR.

[ATAG10] Updated LINKS 01-02-16

"Authoring Tool Accessibility Guidelines 1.0" , J. Treviranus, C. McCathieNevile, I. Jacobs,
and J. Richards, eds., 3 February 2000.
This W3C Recommendation is at: http://www.w3.org/TR/2000/REC-ATAG10-20000203.
Latest version:www.w3.org/TR/ATAG10/

[ATAG10-TECHS] Updated LINKS 01-02-16

" Techniques for Authoring Tool Accessibility", J. Treviranus, C. McCathieNevile, I. Jacobs,
and J. Richards, eds., 4 May 2000.
This W3C Note is at: http://www.w3.org/TR/2000/ATAG10-TECHS.
Latest version: www.w3.org/TR/ATAG10-TECHS/

[CSS1] Updated LINKS 01-02-16

"CSS, level 1 Recommendation", B. Bos, Håkon Wium Lie, eds.,
17 December 1996, revised 11 January 1999.
This CSS1 Level 1 Recommendation is at: http://www.w3.org/TR/REC-CSS1.
Latest version: www.w3.org/TR/REC-CSS1

[CSS2] Updated LINKS 01-02-16

"CSS, level 2 Recommendation", B. Bos, Håkon Wium Lie, C. Lilley, and I. Jacobs, eds., 12 May 1998.
This CSS2 Level 2 Recommendation is at: http://www.w3.org/TR/1998/REC-CSS2-19980512/.
Latest version: www.w3.org/TR/REC-CSS2

[DOM1] Updated LINKS 01-02-16

"Document Object Model (DOM) Level 1 Recommendation", V. Apparao, S. Byrne, M. Champion,
S. Isaacs, I. Jacobs, A. Le Hors, G. Nicol, J. Robie, R. Sutor, C. Wilson, and L. Wood, eds., 1 October 1998.
This DOM Level 1 Recommendation is: http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/
Latest version: www.w3.org/TR/REC-DOM-Level-1

[HTML4] Updated LINKS 01-02-16

"HTML 4.0 Recommendation", D. Raggett, A. Le Hors, and I. Jacobs, eds.,
17 December 1997, revised 24 April 1998.
This HTML 4.0 Recommendation is at: http://www.w3.org/TR/1998/REC-html40-19980424.
Latest version: http://www.w3.org/TR/html40/.

[HTML401] Updated LINKS 01-02-16

"HTML 4.01 Recommendation", D. Raggett, A. Le Hors, and I. Jacobs, eds., 24 December 1999.
This HTML 4.01 Recommendation is at: http://www.w3.org/TR/html401/.
Latest version: www.w3.org/TR/html401/

[MathML10] Updated LINKS 01-02-16

"Mathematical Markup Language" P. Ion and R. Miner, eds., 7 April 1998.
This W3C Recommendation is at: http://www.w3.org/TR/P3P/
Latest version: www.w3.org/TR/P3P/

[P3P10] NEW 01-03-10

"Platform for Privacy Preferences 1.0 (P3P1.0) Specification ", L. Cranor, M. Langheinrich, M. Marchiori, M. Presler-Marshall, and Joseph Reagle, eds., 15 December 2000.
This W3C Candidate Recommendation is at: http://www.w3.org/TR/P3P/.
Latest version: www.w3.org/TR/P3P/

[RDFMS] Updated LINKS 01-02-16

"Resource Description Framework (RDF) Model and Syntax Specification",
O. Lassila, R. Swick, eds., 22 February 1999.
This RDF Recommendation is at: http://www.w3.org/TR/1999/REC-rdf-syntax-19990222.
Latest version: www.w3.org/TR/1999/REC-rdf-syntax/

[RFC2616] Updated LINKS 01-02-16

"Hypertext Transfer Protocol -- HTTP/1.1,
J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee, June 1999.

[SMIL10] Updated LINKS 01-02-16

"Synchronized Multimedia Integration Language (SMIL) 1.0 Recommendation",
P. Hoschka, ed., 15 June 1998.
This SMIL 1.0 Recommendation is at: http://www.w3.org/TR/REC-smil.
Latest version: www.w3.org/TR/REC-smil

[SVG10] Updated LINKS 01-02-16

Scalable Vector Graphics (SVG) 1.0 Specification (Working Draft)," J. Ferraiolo, ed.
This SVG is at: http://www.w3.org/TR/SVG
Latest version: www.w3.org/TR/SVG

[UAAG10] Updated LINKS 01-02-16

"User Agent Accessibility Guidelines 1.0", J. Gunderson, I. Jacobs, eds.
Latest version: www.w3.org/WAI/UA/UAAG10/

[UAAG10-TECHS] Updated LINKS 01-02-16

"Techniques for User Agent Accessibility Guidelines 1.0," J. Gunderson, I. Jacobs, eds.
This Draft is at: http://www.w3.org/WAI/UA/UAAG10-TECHS.
Latest version: www.w3.org/WAI/UA/UAAG10-TECHS

[VOICEBROWSER] Updated LINKS 01-02-16

"VOICEBROWSER.",
This VOICEBROWSER 1.0 Recommendation is at: http://www.w3.org/Voice
A Draft of Speech Synthesis Markup Language Specification for the Speech Interface Framework is at: www.w3.org/TR/speech-synthesis
A Draft of Speech Recognition Grammar Specification for the W3C Speech Interface Framework is at: www.w3.org/TR/speech-grammar
A Draft of Stochastic Language Models (N-Gram) Specification is at: www.w3.org/TR/ngram-spec
Latest versions: www.w3.org/Voice

[WCAG10] Updated LINKS 01-02-16

"Web Content Accessibility Guidelines 1.0", W. Chisholm, G. Vanderheiden, and I. Jacobs, eds., 5 May 1999.
This WCAG 1.0 Recommendation is at: http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505.
Latest version: www.w3.org/TR/WAI-WEBCONTENT

[WCAG10-TECHS] Updated LINKS 01-02-16

"Techniques for Web Content Accessibility Guidelines 1.0", W. Chisholm, G. Vanderheiden, and I. Jacobs, eds.
The latest version of this WC document is available at http://www.w3.org/TR/WCAG10-TECHS.
Latest version: www.w3.org/TR/WCAG10-TECHS

[WCAG20] NEW 01-01-12Updated LINKS 01-02-16

"Web Content Accessibility Guidelines 2.0", W. Chisholm, G. Vanderheiden, and I. Jacobs, eds.
This WCAG 2.0 Recommendation is http://www.w3.org/WAI/GL/WCAG20.
Latest version: www.w3.org/WAI/GL/WCAG20/

[WCAG20-TECHS] NEW 01-01-12Updated LINKS 01-02-16

"Techniques for Web Content Accessibility Guidelines 2.0", W. Chisholm, G. Vanderheiden, and I. Jacobs, eds.
Latest version: www.w3.org/TR/WCAG20-TECHS

[WEBCHAR]

"Web Characterization Terminology and Definitions Sheet", B. Lavoie, H. F. Nielsen, eds., 24 May 1999. This is a W3C Working Draft that defines some terms to establish a common understanding about key Web concepts.

[XHTML10]

"XHTML[tm] 1.0: The Extensible HyperText Markup Language", S. Pemberton, et al. The 26 January 2000 XHTML 1.0 Recommendation is http://www.w3.org/TR/2000/REC-xhtml1-20000126.

[XHTMLbasic] NEW 01-02-15

"XHTML[tm] Basic: The Extensible HyperText Markup Language", S. Pemberton, et al. The 19 December 2000 XHTML Basic Recommendation is http://www.w3.org/TR/2000/REC-xhtml-basic-20001219/.

[XLINK10] NEW 01-02-15

"XML Linking Language (XLink) Version 1.0", T. Bray, J. Paoli, C.M. Sperberg-McQueen, eds., 10 February 1998. This XML 1.0 Recommendation is http://www.w3.org/TR/xlink/.

[XML10] NEW 01-02-15

"Extensible Markup Language (XML) 1.0.", T. Bray, J. Paoli, C.M. Sperberg-McQueen, eds., 10 February 1998. This XML 1.0 Recommendation is http://www.w3.org/TR/1998/REC-xml-19980210.

[XML Schema] NEW 01-04-24NEEDS LINK

"Extensible Markup Schema Language", @@ This XML Schema Recommendation is @@

[XSL10] NEW 01-02-15

"Extensible Stylesheet Language (XSL) 1.0.", This XSL 1.0 Recommendation is http://www.w3.org/TR/xsl/.

[XSLT10] NEW 01-02-15

" XSL Transformations (XSLT) Version 1.0", This XSLT 1.0 Recommendation is http://www.w3.org/TR/xslt.html.

[XSLT11] NEW 01-02-15

" XSL Transformations (XSLT) Version 1.1.", This XSLT 1.1 Draft is http://www.w3.org/TR/xslt11/.

[XPATH10] NEW 01-02-15

" XML Path Language (XPath) Version 1.0", This XPath 1.0 Recommendation is http://www.w3.org/TR/xpath.html.

Editors:

Katie Haritos-Shea , Charles McCathieNevile

For corrections and updates, please contact Katie Haritos-Shea

Comments about this WAI Glossary may be viewed at wai-xtech@w3.org

Last Updated:

$Date: 2002/10/28 18:32:41 $

by: Katie Haritos-Shea or Charles McCathieNevile

Copyright ©1999-2002 W3C ( MIT, INRIA,Keio), All Rights Reserved. W3C liability, trademark,document use and software licensing rules apply.