- conditional content
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
Conditional content is content that, by format specification, should be made available to users through the user interface, generally under certain conditions (e.g., based on user preferences or operating environment limitations). Some examples of conditional content mechanisms include: The alt attribute of the IMG element in HTML 4. According to section 13.2 of the HTML 4 specification ([HTML4]): "User agents must render alternate text when they cannot support images, they cannot support a certain image type or when they are configured not to display images."OBJECT elements in HTML 4. Section 13.3.1 of the HTML 4 specification ([HTML4]) explains the conditional rendering rules of (nested) OBJECT elements. The rules select among ordered alternatives according to user preferences or error conditions.The switch element and test attributes in SMIL 1.0. Sections 4.3 and 4.4, respectively, of SMIL 1.0 [SMIL] explain the conditional rendering rules of these features.SVG 1.0 [SVG] also includes a switch element and several attributes for conditional processing.The NOSCRIPT and NOFRAMES elements in HTML 4 [HTML4] allow the author to provide content under conditions when the user agent does not support scripts or frames, or the user has turned off support for scripts or frames.Specifications vary in how completely they define how and when to render conditional content. For instance, the HTML 4 specification includes the rendering conditions for the alt attribute, but not for the title attribute. The HTML 4 specification does indicate that the title attribute should be available to users through the user interface ("Values of the title attribute may be rendered by user agents in a variety of ways...").Note: The Web Content Accessibility Guidelines 1.0 requires that authors provide text equivalents for non-text content. This is generally done by using the conditional content mechanisms of a markup language. Since conditional content may not be rendered by default, the current document requires the user agent to provide access to unrendered conditional content (checkpoints 2.3 and 2.9) as it may have been provided to promote accessibility.
- conditional sections
-
From Extensible Markup Language (XML) 1.1 (2004-02-04) | Glossary for this source
Conditional sections are portions of the document type declaration external subsetor of external parameter entities which are included in, or excluded from, the logical structure of the DTD based on the keyword which governs them.
- conditional sections
-
From Extensible Markup Language (XML) 1.0 (2000-10-06) | Glossary for this source
Conditional sections are portions of the document type declaration external subset which are included in, or excluded from, the logical structure of the DTD based on the keyword which governs them.
- confidentiality
-
From Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0 (2004-01-15) | Glossary for this source
Protecting the content of a message from unauthorized
disclosure.
- confidentiality
-
From Web Services Glossary (2004-02-11) | Glossary for this source
Assuring information will be kept secret, with access
limited to appropriate persons. [NSA Glossary]
- configuration
-
From Web Services Glossary (2004-02-11) | Glossary for this source
A collection of properties which may be changed. A
property may influence the behavior of an entity.
- configure, control
-
From User Agent Accessibility Guidelines 1.0 (2002-12-17) | Glossary for this source
In the context of this document, the verbs "to control" and "to configure" share in common the idea of governance such as a user may exercise over interface layout, user agent behavior, rendering style, and other parameters required by this document. Generally, the difference in the terms centers on the idea of persistence. When a user makes a change by "controlling" a setting, that change usually does not persist beyond that user session. On the other hand, when a user "configures" a setting, that setting typically persists into later user sessions. Furthermore, the term "control" typically means that the change can be made easily (such as through a keyboard shortcut) and that the results of the change occur immediately. The term "configure" typically means that making the change requires more time and effort (such as making the change via a series of menus leading to a dialog box, or via style sheets or scripts). The results of "configuration" might not take effect immediately (e.g., due to time spent reinitializing the system, initiating a new session, or rebooting the system). In order to be able to configure and control the user agent, the user needs to be able to "write" as well as "read" values for these parameters. Configuration settings may be stored in a profile. The range and granularity of the changes that can be controlled or configured by the user may depend on limitations of the operating environment or hardware.Both configuration and control can apply at different "levels": across Web resources (i.e., at the user agent level, or inherited from the operating environment), to the entirety of a Web resource, or to components of a Web resource (e.g., on a per-element basis).A global configuration is one that applies across elements of the same Web resource, as well as across Web resources.User agents may allow users to choose configurations based on various parameters, such as hardware capabilities or natural language preferences.Note: In this document, the noun "control" refers to a user interface control.
- conformance
-
From QA Framework: Specification Guidelines (2005-08-17) | Glossary for this source
Fulfillment by a product, process, systems, or service of a specified
set of requirements.
- conformance
-
From W3C QA - Quality Assurance glossary (2003-09-06) | Glossary for this source
The ability of a product to meet all the requirements claimed to be supportedPart of a specification which defines the requirements that must be satisfied to claim conformance to part of the specification.Testing the level of fullfilment with regard to the claim done on features implementation
- conformance clause
-
From QA Framework: Specification Guidelines (2005-08-17) | Glossary for this source
A section of the specification that defines the requirements,
criteria, or conditions to be satisfied by an implementation in order to
claim conformance.
- conformance clause
-
From W3C QA - Quality Assurance glossary (2003-09-06) | Glossary for this source
Part of a specification which defines the requirements that must be satisfied to claim conformance to part of the specification.
- conformance testing
-
From W3C QA - Quality Assurance glossary (2003-09-06) | Glossary for this source
Testing the level of fullfilment with regard to the claim done on features implementation
- conforming document
-
From W3C QA - Quality Assurance glossary (2003-09-06) | Glossary for this source
Document that obeys the rules defined in the recommendation it was written for.
- connection
-
From Web Services Glossary (2004-02-11) | Glossary for this source
A transport layer virtual circuit established between
two programs for the purpose of communication.
[RFC 2616]
- connection
-
From Hypertext Transfer Protocol -- HTTP/1.1 (1999-06-15) | Glossary for this source
A transport layer virtual circuit established between two programs for the purpose of communication.
- consequent
-
From RDF Semantics (2004-02-10) | Glossary for this source
(n.) In an inference,
the expression constructed from the
antecedent
. In an entailment relation, the
entailee. Also
conclusion
.
- consistent
-
From RDF Semantics (2004-02-10) | Glossary for this source
(adj., of an expression) Having
a satisfying
interpretation
; not internally contradictory. (Also used
of an inference system as synonym for
Correct
.)
- constraint
-
From Architecture of the World Wide Web, Volume One (2004-12-15) | Glossary for this source
In the design of the Web, some choices, like the names of the
p
and
li
elements in HTML, the choice of
the colon (:) character in URIs, or grouping bits into eight-bit
units (octets), are somewhat arbitrary; if
paragraph
had been chosen instead of
p
or asterisk (*) instead
of colon, the large-scale result would, most likely, have been the
same. This document focuses on more fundamental design choices:
design choices that lead to constraints, i.e., restrictions in
behavior or interaction within the system. Constraints may be
imposed for technical, policy, or other reasons to achieve
desirable properties in the system, such as accessibility, global
scope, relative ease of evolution, efficiency, and dynamic
extensibility.
- constraint
-
From OWL Web Ontology Language Guide (2004-02-10) | Glossary for this source
informal term for discussing the effect of a restriction
- constraint onstraint
-
From XML Schema Part 2: Datatypes (2001-05-02) | Glossary for this source
Constraints on the schema components themselves, i.e. conditions components satisfy to be components at all. Largely to be found in .