Search results

Term entries in the full glossary matching "application"

W3C Glossaries

Showing results 1 - 9 of 9

application

From Extensible Markup Language (XML) 1.1 (2004-02-04) | Glossary for this source

It is assumed that an XML processor is doing its work on behalf of another module, called the application.
application

From Voice Extensible Markup Language (VoiceXML) Version 2.0 (2004-03-16) | Glossary for this source

A collection of VoiceXML documents that are tagged with the same application name attribute.
application

From XPointer Framework (2003-03-25) | Glossary for this source

A software component that incorporates or uses an XPointer processor because it needs to access XML subresources. The occurrence and usage of XPointers, and the behavior to be applied to resources and subresources obtained by processing those XPointers, are governed by the definition of each application's corresponding data format (which could be XML-based or non-XML-based). For example, HTML Web browsers and XInclude processors are applications that might use XPointer processors.
application

From Extensible Markup Language (XML) 1.0 (2000-10-06) | Glossary for this source

It is assumed that an XML processor is doing its work on behalf of another module, called the application.
application personalization

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

A set of factors, specified by a user or other aspects of the delivery context , that may affect the functionality of an application, independently of its adaptation and delivery, and so change the resultant user experience ."
application programming interface (API), conventional input/output/device API),

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

An application programming interface (API) defines how communication may take place between applications. Implementing APIs that are independent of a particular operating environment (as are 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 conventional APIs for a particular operating environment may reduce implementation costs for assistive technology developers who wish to interoperate with more than one piece of software running on that operating environment.A "device API" defines how communication may take place with an input or output device such as a keyboard, mouse, or video card.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 "conventional input/output API" is one that is expected to be implemented by software running on a particular operating environment. For example, the conventional input APIs of the target user agent are for the mouse and keyboard. For touch screen devices or mobile devices, conventional input APIs may include stylus, buttons, and voice. The graphical display and sound card are considered conventional output devices for a graphical desktop computer environment, and each has an associated API.
NCSA (National center for supercomputing applications)

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

A center at the University of Illinois at Urbana-Champaign whose software development group created Mosaic .
SOAP application

From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24) | Glossary for this source

An entity, typically software, that produces, consumes or otherwise acts upon SOAP messages in a manner conforming to the SOAP processing model (see 2. SOAP Processing Model).
SOAP application

From Web Services Glossary (2004-02-11) | Glossary for this source

A software entity that produces, consumes or otherwise acts upon SOAP messages in a manner conforming to the SOAP processing model.


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.