Glossary of "Glossary of Terms for Device Independence"

Term entries in the "Glossary of Terms for Device Independence" glossary

W3C Glossaries

Showing results 21 - 40 of 57

gateway

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

A gateway is an intermediary which acts as a server on behalf of some other server with the purpose of supplying resources or resource manifestations from that other server. Clients using a gateway know the gateway is present but do not know that it is an intermediary.
This term was taken verbatim from Web Characterization Terminology & Definitions Sheet.
glossary of terms for device independence (version used forDevice

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

Glossary of Terms for Device Independence , Rhys Lewis, 2003. W3C Working Draft available at: http://www.w3.org/TR/2003/WD-di-gloss-20030825/
harmonized adaptation

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

A functional adaptation sufficiently harmonized with the delivery context that it generates a harmonized user experience .
harmonized user experience

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

A functional user experience that is sufficiently harmonized with the delivery context to meet the quality criteria of the author.
HTTP client

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

A program that establishes connections for the purpose of sending HTTP requests.
This term was developed from the definition of client in Hypertext Transfer Protocol -- HTTP/1.1.
HTTP gateway

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

An HTTP server which acts as an intermediary for some other HTTP server. Unlike an HTTP proxy, an HTTP gateway receives requests as if it were the origin server for the requested resource; the requesting HTTP client may not be aware that it is communicating with an HTTP gateway.
This term was developed from the definition of gateway in Hypertext Transfer Protocol -- HTTP/1.1.
HTTP payload entity

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

The information transferred as the payload of an HTTP request or HTTP response.
An HTTP payload entity consists of meta-information in the form of entity-header fields and content in the form of an entity-body.
This term was developed from the definition of entity in Hypertext Transfer Protocol -- HTTP/1.1.
HTTP proxy

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

An intermediary program which acts as both an HTTP server and as an HTTP client for the purpose of making requests on behalf of other HTTP clients.
HTTP requests are serviced internally or by passing them on, with possible translation, to other HTTP servers. An HTTP proxy must implement both the client and server requirements of this specification. A "transparent proxy" is a proxy that does not modify the HTTP request or the HTTP response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is a proxy that modifies the HTTP request or HTTP response in order to provide some added service to the user agent, such as group annotation services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies.
This term was developed from the definition of proxy in Hypertext Transfer Protocol -- HTTP/1.1.
HTTP representation

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

An HTTP payload entity, included in an HTTP response, that is subject to content negotiation. There may exist multiple representations associated with a particular HTTP response status.
This term was developed from the definition for representation in Hypertext Transfer Protocol -- HTTP/1.1.
HTTP request

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

An HTTP message sent by an HTTP client requesting that some operation be performed on some resource. Also, the act of sending such a message is termed making a request.
This term was developed from the definition of request in Hypertext Transfer Protocol -- HTTP/1.1.
HTTP response

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

An HTTP message sent back to an HTTP client in response to a previous HTTP request.
This term was developed from the definition of response in Hypertext Transfer Protocol -- HTTP/1.1.
HTTP server

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

An application program that accepts connections in order to service HTTP requests by sending back HTTP responses.
Any given program may be capable of being both an HTTP client and an HTTP server; our use of these terms refers only to the role being performed by the program for a particular connection, rather than to the program's capabilities in general. Likewise, any HTTP server may act as an origin server, HTTP proxy, HTTP gateway, or tunnel, switching behavior based on the nature of each request.
This term was developed from the definition of server in Hypertext Transfer Protocol -- HTTP/1.1.
interaction

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

An activity by which a user can influence the data and processing of an application by modifying the information associated with an active perceivable unit.
A common form of this kind of activity is the entry of data into an active perceivable unit that contains a form.
modality

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

The type of communication channel used for interaction . This might be, for example, visual, gestural or based on speech. It also covers the way an idea is expressed or perceived, or the manner in which an action is performed. This definition is based on unpublished work of the Multimodal Interaction group.
multiple authoring

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

An authoring style in which a different variant of each resource is created for use in the user experience for each delivery context without adaptation.
Multiple authoring represents one end of a spectrum of authoring styles that include single authoring and flexible authoring. It represents a theoretical extreme that is rarely achieved in practice. Though it offers authors complete control over the user experience on each device, the associated development and maintenance costs are usually considered prohibitive.
navigation

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

An activity, based on a mechanism provided by an active perceivable unit, by which a user can alter their focus of attention. If the new focus of attention is in a different perceivable unit, that unit becomes an active perceivable unit.
One common form of this kind of mechanism is the link, a region within an active perceivable unit which can be activated by a suitable user action.
origin server

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

The server on which a given resource resides or is to be created.
This term was taken verbatim from Hypertext Transfer Protocol -- HTTP/1.1.
perceivable unit

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

A set of material which, when rendered by a user agent, may be perceived by a user and with which interaction may be possible.
User agents may choose to render some or all of the material they receive in a delivery unit as a single perceivable unit or as multiple perceivable units.
Most perceivable units provide both presentation and the means for interaction. However, on some types of device, such as printers, perceivable units might contain only presentation.
physical transducer

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

An entity by which a user interacts physically with a device .
proxy

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

A proxy is an intermediary which acts as both a server and a client for the purpose of retrieving resources or resource manifestations on behalf of other clients. Clients using a proxy know the proxy is present and that it is an intermediary.
This term was taken verbatim from Web Characterization Terminology & Definitions Sheet.

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.