Search results

Term entries in the full glossary starting with the letter "V"

W3C Glossaries

Showing results 21 - 40 of 47

variable values

From XQuery 1.0: An XML Query Language (2007-01-23) | Glossary for this source

Variable values. This is a set of (expanded QName, value) pairs. It contains the same expanded QNames as the in-scope variables in the static context for the expression. The expanded QName is the name of the variable and the value is the dynamic value of the variable, which includes its dynamic type.
variable values

From XML Path Language (XPath) 2.0 (2007-01-23) | Glossary for this source

Variable values. This is a set of (expanded QName, value) pairs. It contains the same expanded QNames as the in-scope variables in the static context for the expression. The expanded QName is the name of the variable and the value is the dynamic value of the variable, which includes its dynamic type.
variable-binding elements

From XSL Transformations (XSLT) 2.0 (2007-01-23) | Glossary for this source

The two elements xsl:variable and xsl:param are referred to as variable-binding elements
variant

From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source

One of several possible representations of a data resource.
variant

From Glossary of Terms for Device Independence (2005-01-18) | Glossary for this source

A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations is termed a `variant.' Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
This term is taken verbatim from Hypertext Transfer Protocol -- HTTP/1.1.
variant

From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15) | Glossary for this source

A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations is termed a `varriant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
variant content

From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source

When the form/format of the content being sent depends on receiver's capabilities and/or preferences
version declaration

From XQuery 1.0: An XML Query Language (2007-01-23) | Glossary for this source

Any module may contain a version declaration. If present, the version declaration occurs at the beginning of the module and identifies the applicable XQuery syntax and semantics for the module.
versioning

From Hypertext Terms (1995-04-15) | Glossary for this source

The storage and management of previous versions of a piece of information, for security, diagnostics, and interest. This is important when many users are allowed to edit the same material. (More...)
video

From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source

This content type label refers to all of the requirements related to video for the following checkpoints: 2.5, 2.6, and 3.2. When this label is part of a conformance profile, the user agent must implement at least one video format. Furthermore, when this label is part of a profile, the user agent must satisfy the requirements of checkpoint 3.2 for all implemented video formats, not just those identified in a conformance profile. The video requirements apply to video content that is recognized as distinct and that, according to the encoding format, may be rendered as a coherent unit.
view

From Authoring Tool Accessibility Guidelines 1.0 (2000-02-03) | Glossary for this source

Authoring tools may render the same content in a variety of ways; each rendering is called a "view." Some authoring tools will have several different types of view, and some allow views of several documents at once. For instance, one view may show raw markup, a second may show a structured tree, a third may show markup with rendered objects while a final view shows an example of how the document may appear if it were to be rendered by a particular browser. A typical way to distinguish views in a graphic environment is to place each in a separate window.
view, viewport

From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source

The user agent renders content through one or more viewports. Viewports include windows, frames, pieces of paper, loudspeakers, and virtual magnifying glasses. A viewport may contain another viewport (e.g., nested frames). User agent user interface controls such as prompts, menus, and alerts are not viewports. Graphical and tactile viewports have two spatial dimensions. A viewport may also have temporal dimensions, for instance when audio, speech, animations, and movies are rendered. When the dimensions (spatial or temporal) of rendered content exceed the dimensions of the viewport, the user agent provides mechanisms such as scroll bars and advance and rewind controls so that the user can access the rendered content "outside" the viewport. Examples include: when the user can only view a portion of a large document through a small graphical viewport, or when audio content has already been played.When several viewports coexist, only one has the current focus at a given moment. This viewport is highlighted to make it stand out.User agents may render the same content in a variety of ways; each rendering is called a view. For instance, a user agent may allow users to view an entire document or just a list of the document's headers. These are two different views of the document.
viola

From Glossary of "Weaving the Web" (1999-07-23) | Glossary for this source

An interpreted computer language (like Java) developed by Pei Wei at the University of Berkeley. Also, a Web browser built using Viola.
  • An early review I wrote of Viola
virtual hypertext

From Glossary of "Weaving the Web" (1999-07-23) | Glossary for this source

Hypertext that is generated from its URI by a program, rather than by recourse to a stored file. This was my name for the idea. The CERN phone book was the first example, in 1991. It is sometimes difficult to tell, and impossible to define formally, what is virtual hypertext and what is not.
visual track

From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source

A visual object is content rendered through a graphical viewport. Visual objects include graphics, text, and visual portions of movies and other animations. A visual track is a visual object that is intended as a whole or partial presentation. A visual track does not necessarily correspond to a single physical object or software object.
visual-only presentation

From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source

A visual-only presentation is content consisting exclusively of one or more visual tracks presented concurrently or in series. A silent movie is an example of a visual-only presentation.
visualText

From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source

This content type label refers to all of the requirements related to visually rendered text for the following checkpoints: 3.3, 4.1, 4.2, and 4.3. If a user agent renders text visually, it must satisfy these requirements in order to conform, and this label must appear in a conformance profile. Furthermore, the user agent must satisfy these requirements for all implemented formats that produce visually rendered text, not just those identified in a conformance profile. An audio-only or tactile-only user agent is not required to satisfy the requirements associated with this label.
vocabulary

From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source

A collection of attributes that adequately describe the CC/PP. A vocabulary is associated with a schema.
vocabulary

From OWL Web Ontology Language Guide (2004-02-10) | Glossary for this source

a set of URI references
voice

From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source

This input modality label refers to all of the generic input device requirements of this document as well as those specific to the keyboard, except for the requirements of checkpoint 11.4. This label is an indication that these requirements have been satisfied for voice input.

The Glossary System has been built by Pierre Candela during an internship in W3C; it's now maintained by Dominique Hazael-Massieux

Copyright © 2000-2003W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.