Movatterモバイル変換
[0]ホーム
This document is a glossary of terms used in other documents produced bythe Device Independence Working Group (DIWG). Details of the entire series ofdocuments can be found on theW3C DeviceIndependence Activity home page.
This section describes the status of this document at the time of itspublication. Other documents may supersede this document. A list of currentW3C publications and the latest revision of this technical report can befound in theW3C technical reports indexat http://www.w3.org/TR/.
This glossary is published and maintained by DIWG, part of theW3C Device Independence Activity. TheDIWG activity statement can be seen athttp://www.w3.org/2001/di/ActivityThe glossary is maintained as a Working Draft of a future W3C Note. Thisallows it to be revised at appropriate intervals. Updates take place insupport of new work being carried out by the DIWG. In general, it isinappropriate to use W3C Working Drafts as formal reference material or tocite them as other than "work in progress". Because this document is subjectto change, other authors wishing to cite definitions in this glossary shouldexercise caution. Updates to the glossary are made in such a way as to avoidinvalidating references, as long as those references conform to themechanisms described in the sectionUsing and Maintaining the Glossary.However, in support of its work, DIWG may need to modify definitions in newerversions of this document.
A list of current public W3C Working Drafts can be found athttp://www.w3.org/TR.
Publication as a Working Draft does not imply endorsement by the W3CMembership. This is a draft document and may be updated, replaced orobsoleted by other documents at any time. It is inappropriate to cite thisdocument as other than work in progress.
Comments on this document can be sent towww-di@w3.org, the public forum fordiscussion of the W3C's work on Device Independence. To subscribe, send anemail towww-di-request@w3.orgwith the word subscribe in the subject line (include the word unsubscribe ifyou want to unsubscribe). Thearchive for the listis accessible online.
Information on how to use this document and how it is maintained can befound inUsing and Maintaining theGlossary.
Patent disclosures relevant to this document may be found on theWG patent disclosure page.
Terms whose definitions are taken directly from other sources are markedas follows:
- Term taken verbatim from another source
- Definition taken from another source
- Access Mechanism
- A combination of hardware (including one or moredevices and network connections) and software (including one or moreuser agents) that allows auser to perceive andinteract with the Web using one or moremodalities. (sight, sound, keyboard, voice etc.)
- Active Perceivable Unit
- Aperceivable unit that is currently being rendered by theuser agent and with whichinteraction may be possible.
- Adaptation
- a process of selection, generation or modification that produces one or moreperceivable units in response to a requesteduniform resource identifier in a given delivery context.
- Adaptation Preferences
- A set of preferences, specified by auser, that may affect theadaptation for a given delivery context, and so change the resultantuser experience.
- Application Personalization
- A set of factors, specified by auser or other aspects of thedelivery context, that may affect the functionality of an application, independently of itsadaptation and delivery, and so change the resultantuser experience."
- Authored Unit
- Some set of material created as a single entity by an author. Examples include a collection of markup, a style sheet, and a mediaresource, such as an image or audio clip.
- Browser
- Auser agent that allows auser to perceive andinteract with information on the Web.
- This definition was developed from that inWeaving the Web: Glossary.
- Client
- The role adopted by an application when it is retrieving and/or renderingresources orresource manifestations.
- This term was taken verbatim fromWeb Characterization Terminology & Definitions Sheet.
- Content Negotiation
- The mechanism for selecting the appropriateHTTP representation when servicing arequest. TheHTTP representation of entities in any response can be negotiated (including error responses).
- This term was developed from that inHypertext Transfer Protocol -- HTTP/1.1.
- Decomposition
- The act of dividing up one or moreauthored units during creation of a set ofperceivable units appropriate for a particular delivery context.
- Delivery Context
- A set of attributes that characterizes the capabilities of theaccess mechanism and the preferences of theuser
- Delivery Unit
- A set of material transfered between two cooperating web programs as the response to a singleHTTP request. The transfer might, for example, be between anorigin server and auser agent.
- Users are not normally aware of individual delivery units.
- Device
- An apparatus through which auser can perceive andinteract with the Web
- Focus of Attention
- The point in anactive perceivable unit on which the user's attention is currently focused.
- For example, this might be a paragraph of text or an image on which the user is concentrating.
- Functional Adaptation
- Anadaptation that generates afunctional user experience from a particularresource.
- Functional User Experience
- A set of one or moreperceivable units that enables auser to complete the function intended by the author for a givenresource via a givenaccess mechanism.
- Gateway
- A gateway is an intermediary which acts as aserver on behalf of some otherserver with the purpose of supplyingresources orresource manifestations from that otherserver.Clients using a gateway know the gateway is present but do not know that it is an intermediary.
- This term was taken verbatim fromWeb Characterization Terminology & Definitions Sheet.
- Harmonized Adaptation
- Afunctional adaptation sufficiently harmonized with thedelivery context that it generates aharmonized user experience.
- Harmonized User Experience
- Afunctional user experience that is sufficiently harmonized with thedelivery context to meet the quality criteria of the author.
- HTTP Client
- A program that establishes connections for the purpose of sendingHTTP requests.
- This term was developed from the definition ofclient inHypertext Transfer Protocol -- HTTP/1.1.
- HTTP Gateway
- AnHTTP server which acts as an intermediary for some otherHTTP server. Unlike anHTTP proxy, an HTTP gateway receives requests as if it were theorigin server for the requestedresource; the requestingHTTP client may not be aware that it is communicating with an HTTP gateway.
- This term was developed from the definition ofgateway inHypertext Transfer Protocol -- HTTP/1.1.
- HTTP Payload Entity
- The information transferred as the payload of anHTTP request orHTTP 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 ofentity inHypertext Transfer Protocol -- HTTP/1.1.
- HTTP Proxy
- An intermediary program which acts as both anHTTP server and as anHTTP client for the purpose of making requests on behalf of otherHTTP clients.
- HTTP requests are serviced internally or by passing them on, with possible translation, to otherHTTP 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 theHTTP request or theHTTP response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is a proxy that modifies theHTTP request orHTTP response in order to provide some added service to theuser 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 ofproxy inHypertext Transfer Protocol -- HTTP/1.1.
- HTTP Representation
- AnHTTP payload entity, included in anHTTP response, that is subject tocontent negotiation. There may exist multiple representations associated with a particularHTTP response status.
- This term was developed from the definition forrepresentation inHypertext Transfer Protocol -- HTTP/1.1.
- HTTP Request
- An HTTP message sent by anHTTP client requesting that some operation be performed on someresource. Also, the act of sending such a message is termedmaking a request.
- This term was developed from the definition ofrequest inHypertext Transfer Protocol -- HTTP/1.1.
- HTTP Response
- An HTTP message sent back to anHTTP client in response to a previousHTTP request.
- This term was developed from the definition ofresponse inHypertext Transfer Protocol -- HTTP/1.1.
- HTTP Server
- An application program that accepts connections in order to serviceHTTP requests by sending backHTTP responses.
- Any given program may be capable of being both anHTTP 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, anyHTTP server may act as anorigin server,HTTP proxy,HTTP gateway, or tunnel, switching behavior based on the nature of each request.
- This term was developed from the definition ofserver inHypertext Transfer Protocol -- HTTP/1.1.
- Interaction
- An activity by which a user can influence the data and processing of an application by modifying the information associated with anactive perceivable unit.
- A common form of this kind of activity is the entry of data into anactive perceivable unit that contains a form.
- Modality
- The type of communication channel used forinteraction . 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.
- Navigation
- An activity, based on a mechanism provided by anactive perceivable unit, by which a user can alter theirfocus of attention. If the newfocus of attention is in a differentperceivable unit, that unit becomes anactive perceivable unit.
- One common form of this kind of mechanism is the link, a region within anactive perceivable unit which can be activated by a suitable user action.
- Origin Server
- Theserver on which a given resource resides or is to be created.
- This term was taken verbatim fromHypertext Transfer Protocol -- HTTP/1.1.
- Perceivable Unit
- A set of material which, whenrendered by auser agent, may be perceived by auser and with whichinteraction may be possible.
- User agents may choose to render some or all of the material they receive in adelivery unit unit as a single perceivable unit or as multiple perceivable units.
- Most perceivable units provide both presentation and the means forinteraction. However, on some types of device, such as printers, perceivable units might contain only presentation.
- Proxy
- A proxy is an intermediary which acts as both aserver and aclient for the purpose of retrievingresources orresource manifestations on behalf of otherclients.Clients using a proxy know the proxy is present and that it is an intermediary.
- This term was taken verbatim fromWeb Characterization Terminology & Definitions Sheet.
- Rendering
- The act of convertingperceivable units into physical effects that can be perceivable by auser and with which auser may be able tointeract.
- Rendering Preferences
- A set of preferences, specified by auser, that may affect the way the user agent renders a perceivable unit, and so change the resultant user experience.
- Request
- A message describing an atomic operation to be carried out in the context of a specifiedresource.
- This term was taken verbatim fromWeb Characterization Terminology & Definitions Sheet.
- Resource
- A network data object or service that can be identified by aURI. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, resolutions) or vary in other ways.
- This term was taken verbatim fromHypertext Transfer Protocol -- HTTP/1.1
- Resource Manifestation
- One specific rendition of aresource at a specific point in time and space.
- A conceptual mapping exists between aresource and a resource manifestation (or set of manifestations), in the sense that the resource has certain properties - e.g., itsURI, its intended purpose, etc. - which are inherited by each manifestation, although the specific structure, form, and content of the manifestation may vary according to factors such as the environment in which it is displayed, the time it is accessed, etc. Regardless of the form the manifestation's rendering ultimately takes, the conceptual mapping to theresource is preserved.
- This term was taken verbatim fromWeb Characterization Terminology & Definitions Sheet
- Response
- A message containing the result of an executedrequest.
- This term was taken verbatim fromWeb Characterization Terminology & Definitions Sheet.
- Server
- The role adopted by an application when it is supplyingresources orresource manifestations.
- This term was taken verbatim fromWeb Characterization Terminology & Definitions Sheet.
- Uniform Resource Identifier
- A short string that uniquely identifies aresource such as an HTML document, an image, a down-loadable file, a service, or an electronic mailbox.
- User
- A human who perceives andinteracts with the web
- User Agent
- Aclient within adevice that performsrendering.
- Browsers are examples ofuser agents, as are web robots that automatically traverse the web collecting information.
- User Experience
- A set of materialrendered by auser agent which may be perceived by auser and with whichinteraction may be possible.
- Variant
- Aresource 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 tocontent negotiation.
- This term is taken verbatim fromHypertext Transfer Protocol -- HTTP/1.1.
- Web Page
- A collection of information, consisting of one or moreresources, intended to be rendered simultaneously, and identified by a singleUniform Resource Identifier.
- More specifically, a web page consists of aresource with zero, one, or more embeddedresources intended to be rendered as a single unit, and referred to by theURI of the oneresource which is not embedded.
- This term was developed from the definition ofweb page inWeb Characterization Terminology & Definitions Sheet.
- Web Page Identifier
- AUniform Resource Identifier intended to be recognized by a user as representing the identity of a specific Web Page (resource).
- It may need to be entered explicitly by a user.
This section documents the way in which the glossary should be used fromother DIWG documents. It also documents how changes are to be made to theglossary itself in a way that will not invalidate links to thedefinitions.
Every definition in the glossary has an associated anchor. As aconsequence every definition can be directly referenced externally from otherdocuments. Such references should use the public URL associated with the DIWGglossary. For the latest version of the glossary, this has been establishedas
http://www.w3.org/TR/di-gloss/
Dated versions of the glossary will appear at URLs in the form of thefollowing
http://www.w3.org/TR/2003/WD-di-gloss-20030825/
To refer to a particular definition, a document should create a URL basedon the appropriately dated, public URL and the fragment identifier for thedefinition. Fragment identifiers consist of the definition name, inlowercase, with words separated by dashes and prefixed bydef. For example, the fragment identifier for the definitionofUser Agent isdef-user-agent, and forNavigation isdef-navigation. The URL touse for the definition of Navigation for the dated version mentioned abovewould be:
http://www.w3.org/TR/2003/WD-di-gloss-20030825/#def-navigation
One important guarantee for documents that reference the glossary is thatthe fragment identifier for a given definition never changes. If, forexample, a new version of a particular definition is needed, the olderversion will be retained within the glossary with its fragment identifier.The new version will be given a new identifier. The process used to maintainthe glossary and to retain this uniqueness of definition identifiers isdescribed in the following section.
In addition to referring directly to individual definitions in theglossary, documents that use it should include a reference to the datedversion in use in their References section. The following is an example ofsuch a reference:
- Glossary of Terms for Device Independence (version used for definitions)
- Glossary of Terms for Device Independence, Rhys Lewis, 2003. W3C Working Draft available at: http://www.w3.org/TR/2003/WD-di-gloss-20030825/
The DIWG glossary will remain a public working draft. This reflects theneed to update it as new work is carried out in DIWG. The need to revise theglossary, and in particular the potential requirement to revise definitions,leads to a need for a mechanism that can allow older documents to referunambiguously to older revisions of particular definitions.
Once a version of the glossary has been published, the definitions itcontains have fragment identifiers that must not be changed. As newdefinitions are added they are given new identifiers. This poses no issuesfor documents authored before the new definitions were published. However,when a definition is revised, it is vital that older documents that used theold version are still valid. They are protected by versionning the fragmentidentifiers and by keeping the old versions of definitions inAppendix B of the glossary.
To revise a glossary definition, the following steps must be carriedout:
- The existing definition, complete with fragment identifier, must be copied toAppendix B.
- The definition must be updated within the main part of the glossary.
- The revised definition must be given an updated fragment identifier constructed by adding a version number where none exists, or incrementing it if one already exists. For example, if the fragment identifier before revision were#def-navigation it would become#def-navigation-v2. Alternatively, if the fragment identifier before revision were#def-navigation-v7 it would become#def-navigation-v8.
- All references to the definition within the glossary itself must be updated to refer to this new fragment identifier. In addition, all definitions that refer to the revised definition must be reviewed to see whether they need modification because of the change. If so, this same procedure must be applied those definitions and new versions must be created.
- The old definition that has been moved toAppendix B must have a reference added that refers to the newer definition in the body of the glossary. As an example, the reference for an old version of the definition of Navigation might include the reference:
"This definition has been superseded. There is a newer definition ofNavigation".
Notice thatthese links shouldnot be updated when a new version of a definition is added. By not changing them, they form a chain through the versions of the definition from the one referenced by the external document up to the latest version.
This section contains definitions that have been superseded within theexisting glossary. The first section holds definitions that have beenupdated. The second section holds definitions that have been removed.
No definitions have yet been updated.
- User Experience Preferences
- A set of preferences, specified by auser, that affect theuser experience that results fromadaptation for a givendelivery context
- Fragmentation
- The act of dividing up one or moreauthored units to create a set ofperceivable units appropriate for a particular delivery context.
- This term has been replaced by the new termdecomposition
No definitions have yet been deprecated.
- Hypertext Transfer Protocol -- HTTP/1.1.1
- Hypertext Transfer Protocol -- HTTP/1.1, June 1999. IETF RFC-2616 available at http://www.w3.org/Protocols/rfc2616/rfc2616.html
- Uniform Resource Identifiers (URI): Generic Syntax
- Uniform Resource Identifiers (URI): Generic Syntax, June 1998. IETF RFC-2396 available at http://www.ietf.org/rfc/rfc2396.txt
- Naming and Addressing: URIs, URLs, ...
- Naming and Addressing: URIs, URLs, ... available at http://www.w3.org/Addressing/
- Web Characterization Terminology & Definitions Sheet
- Web Characterization Terminology & Definitions Sheet, May 1999. W3C Working Draft available at http://www.w3.org/1999/05/WCA-terms/
- Weaving the Web: Glossary
- Weaving the Web: Glossary, 1999, Tim Berners-Lee. Available at http://www.w3.org/People/Berners-Lee/Weaving/glossary.html
Members of the W3C Device Independence Working Group have helped developthis Working Group Note through their comments, proposals and discussions atteleconferences, face-to-face meetings and via the group discussion list.
At the time of publication, the principal and active members of the groupwere as follows:
- Stephane Boyera (W3C)
- Steve Farowich (Boeing)
- Roger Gimson (HP)
- Yoshihisa Gonno (Sony Corp)
- Guido Grassel (Nokia)
- Rotan Hanrahan (MobileAware Ltd)
- Kazuhiro Kitagawa (W3C)
- Markus Lauff (SAP AG)
- Tayeb Lemlouma (INRIA)
- Rhys Lewis (Volantis Systems Ltd)
- Roland Merrick (IBM)
- Franklin Reynolds (Nokia)
- Andreas Schade (IBM)
- Ryuji Tamagawa (Sky Think System)
- Luu Tran (Sun Microsystems)
- Michael Wasmund (IBM)
- Stan Wiechers (Merkwelt)
- Jason White (University of Melbourne)
- Candy Wong (NTT DoCoMo)
- Amy Yu (SAP AG)
The following were members of the group at earlier stages of itsdrafting:
- Yasser AlSafadi (Philips Research)
- Abbie Barbir (Nortel Networks)
- Einar Breen (Adaptive Media)
- Shlomit Ritz Finkelstein (invited expert)
- Vidhya Golkar (Argogroup)
- Luo Haiping (Comverse)
- Eric Hsi (Philips Research)
- Lynda Jones (SHARE)
- William Loughborough (Smith-Kettlewell Institute)
- Stephane Maes (IBM)
- Kaori Nakai (NTT DoCoMo)
- Hidetaka Ohto (W3C/Panasonic)
- Garland Phillips (Motorola)
- Lalitha Suryanarayana (SBC Technology Resources)
- Yoshifumi Yonemoto (NTT DoCoMo)
[8]ページ先頭