Search results

Term entries in the full glossary matching "component"

W3C Glossaries

Showing results 1 - 6 of 6

component

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

1. A component is a software object, meant to interact with other components, encapsulating certain functionality or a set of functionalities. A component has a clearly defined interface and conforms to a prescribed behavior common to all components within an architecture. [CCA T&D]

2. A component is an abstract unit of software instructions and internal state that provides a transformation of data via its interface. [Fielding]

3. A component is a unit of architecture with defined boundaries.

component

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

for parts of a definition e.g. the arguments to intersection-of in a class definition

in-scope schema components

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

The schema components that may be referenced by name in a stylesheet are referred to as the in-scope schema components. This set is the same throughout all the modules of a stylesheet.

schema components

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

Type definitions and element and attribute declarations are referred to collectively as schema components.

sort key component

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

Within a sort key specification, each xsl:sort element defines one sort key component.

user control of every user interface component

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

This document distinguishes user interface features that are part of the user agent user interface and those that are part of content. Some checkpoints (e.g., those in guideline 5) require user control over rendering and behavior that is driven by content only. This document does not always explicitly require the same control over features of the user agent user interface. Nevertheless, this document (see checkpoint 7.3) does require user agents to follow software usability guidelines. The UAWG expects such usability guidelines to include requirements for user control over user interface behavior.Note: It is more difficult for users to distinguish content from user interface when both are rendered as sound in one temporal dimension, than it is when both are rendered visually in two spatial dimensions. Thus, the UAWG encourages developers of user agents that include audio output or synthesized speech output to apply the requirements of this document to both content and user agent components.

Run another query