-
RDF (Resource description framework)
-
From Requirements
for String Identity Matching and String Indexing (1998-07-10) |
Glossary for this
source
A data model and streaming format for
metadata, with search engines and inference engines as potential
users. Much metadata is textual, and a basic operation is to decide
whether two elements of metadata are the same or not. For
consistent behavior, string identity matching is necessary.
-
RDF (Resource description framework)
-
From Glossary of "Weaving the Web"
(1999-07-23)
| Glossary for
this source
A framework for constructing logical
languages that can work together in the Semantic Web. A way of
using XML for data rather than just documents.
- RDF
resource
-
From
Composite Capability/Preference Profiles (CC/PP): Structure and
Vocabularies 1.0 (2004-01-15)
| Glossary for
this source
An object or element being described by RDF
expressions is a resource. An RDF resource is typically identified
by a URI.
- reader
-
From Hypertext Terms (1995-04-15) | Glossary for this
source
We have used this term for the person who
browses, to distinguish him/her from the program (
browser ) which (s)he
uses.
- reading
-
From Ruby Annotation (2001-05-31) |
Glossary for this
source
For ideographs: Technical term; indication
of possible pronunciation. Different from pronunciation in various
respects: script used may not be fully phonetic; actual
pronunciation is speaker-dependent; pronunciation may not be
realized when reading a text silently. In Chinese or Korean, some
ideographs have several readings. In Japanese, most ideographs have
at least two readings, and some have a lot more. Readings also may
depend on context.
- REC
-
From Glossary of W3C Jargon (2003-03-11) | Glossary for this
source
- receiver
-
From
Composite Capability/Preference Profiles (CC/PP): Structure and
Vocabularies 1.0 (2004-01-15)
| Glossary for
this source
A system component (device or program)
which receives a message.
- recognize
-
From User Agent
Accessibility Guidelines 1.0 (2002-12-17) |
Glossary for this
source
Authors encode information in many ways,
including in markup languages, style sheet languages, scripting
languages, and protocols. When the information is encoded in a
manner that allows the user agent to process it with certainty, the
user agent can "recognize" the information. For instance, HTML
allows authors to specify a heading with the H1 element, so a user
agent that implements HTML can recognize that content as a heading.
If the author creates a heading using a visual effect alone (e.g.,
just by increasing the font size), then the author has encoded the
heading in a manner that does not allow the user agent to recognize
it as a heading. Some requirements of this document depend on
content roles, content relationships, timing relationships, and
other information supplied by the author. These requirements only
apply when the author has encoded that information in a manner that
the user agent can recognize. See the section on conformance for
more information about applicability.In practice, user agents will
rely heavily on information that the author has encoded in a markup
language or style sheet language. On the other hand, behaviors,
style, meaning encoded in a script, and markup in an unfamiliar XML
namespace may not be recognized by the user agent as easily or at
all. The Techniques document [UAAG10-TECHS] lists some markup known
to affect accessibility that user agents can recognize.
- recommendation
-
From Glossary of W3C Jargon (2003-03-11) | Glossary for this
source
A technical specification which has been
endorsed by the W3C. Similar to what other standards organizations
would call a "Standard".
- recoverable
errors
-
From XSL Transformations (XSLT)
2.0 (2007-01-23) |
Glossary for this
source
Some dynamic errors are classed as
recoverable errors. When a recoverable error occurs, this
specification allows the processor either to signal the error (by
reporting the error condition and terminating execution) or to take
a defined recovery action and continue processing.
- reduced
image
-
From Portable
Network Graphics (PNG) Specification (Second Edition) (2003-11-10) |
Glossary for this
source
-
reference architecture
-
From Web Services Glossary (2004-02-11)
| Glossary for
this source
A reference architecture is the generalized architecture of several end systems that
share one or more common domains. The reference architecture
defines the infrastructure common to the end systems and the
interfaces of components that will be included in the end systems.
The reference architecture is then instantiated to create a
software architecture of a specific system. The definition of the
reference architecture facilitates deriving and extending new
software architectures for classes of systems. A reference
architecture, therefore, plays a dual role with regard to specific
target software architectures. First, it generalizes and extracts
common functions and configurations. Second, it provides a base for
instantiating target systems that use that common base more
reliably and cost effectively. [Ref Arch]
- reference
image
-
From Portable
Network Graphics (PNG) Specification (Second Edition) (2003-11-10) |
Glossary for this
source
rectangular array of rectangular
pixels , each having the
same number of
samples , either three
(red, green, blue) or four (red, green, blue,
alpha ). Every reference
image can be represented exactly by a
PNG datastream and every
PNG datastream can be converted into a reference image. Each
channel has a
sample depth in
the range 1 to 16. All samples in the same channel have the same
sample depth. Different channels may have different sample
depths.
-
reference in attribute value
-
From Extensible Markup Language
(XML) 1.1 (2004-02-04) |
Glossary for this
source
as a reference within either the value of
an attribute in a start-tag, or a default value in an attribute
declaration; corresponds to the nonterminal AttValue.
-
reference in attribute value
-
From Extensible Markup
Language (XML) 1.0 (2000-10-06) |
Glossary for this
source
as a reference within either the value of
an attribute in a start-tag, or a default value in an attribute
declaration; corresponds to the nonterminal AttValue.
- reference
in content
-
From Extensible Markup Language
(XML) 1.1 (2004-02-04) |
Glossary for this
source
as a reference anywhere after the start-tag
and before the end-tag of an element; corresponds to the
nonterminal content.
- reference
in content
-
From Extensible Markup
Language (XML) 1.0 (2000-10-06) |
Glossary for this
source
as a reference anywhere after the start-tag
and before the end-tag of an element; corresponds to the
nonterminal content.
- reference
in DTD
-
From Extensible Markup Language
(XML) 1.1 (2004-02-04) |
Glossary for this
source
as a reference within either the internal
or external subsets of the DTD, but outside of an EntityValue,
AttValue, PI, Comment, SystemLiteral, PubidLiteral, or the contents
of an ignored conditional section (see )..
- reference
in DTD
-
From Extensible Markup
Language (XML) 1.0 (2000-10-06) |
Glossary for this
source
[E90]as a reference within either the
internal or external subsets of the DTD, but outside of an
EntityValue, AttValue, PI, Comment, SystemLiteral, PubidLiteral, or
the contents of an ignored conditional section (see )..
-
reference in entity value
-
From Extensible Markup Language
(XML) 1.1 (2004-02-04) |
Glossary for this
source
as a reference within a parameter or
internal entity's literal entity value in the entity's declaration;
corresponds to the nonterminal EntityValue.