Normative Definitions from Gleaning Resource Descriptions from Dialects of Languages (GRDDL)
in section Status of This Document
in section Table of Contents
in section 1. Introduction: Data and Documents
in section Resource Descriptions
in section Faithful Renditions
in section Preface and Companion Documents
in section GRDDL Primer
in section GRDDL Use Cases
in section 2. Adding GRDDL to well-formed XML
Given an XPath[XPATH] root
node N with root element E,
if the expression
/*/@*[local-name()="transformation"
and namespace-uri()=
"http://www.w3.org/2003/g/data-view#"]
matches an attribute of
an element
E, then for each space-separated
token REF in the value of that attribute, the resource
identified[WEBARCH] by the
absolute form (see section 5.2 Relative Resolution in [RFC3986]) of REF with respect to the
base URI of E is a GRDDL transformation of
N.
|
If an information resource([WEBARCH],
section 2.2) IR
is represented by an XML document with
an XPath root node R,
and R has a GRDDL transformation
with a transformation property TP,
and TP applied to R gives an
RDF Graph G, then G
is a GRDDL result of IR.
|
If F and G are GRDDL results of IR,
then the
merge
[RDF-MT]
of F and G is also a GRDDL result of IR.
|
in section 3. Using GRDDL with XML Namespace Documents
If
- an information resource NSDOC, identified by a URI
NS has a GRDDL result that includes a triple
whose
- subject is NSDOC, whose
- predicate is the property
<http://www.w3.org/2003/g/data-view#namespaceTransformation>,
and whose
- object is TX,
- and an information resource
IR has an XML representation with
root node NODE and with a root element
with a namespace name NS,
then TX is a GRDDL
transformation of NODE.
|
If an information resource IR is represented
by a
conforming RDF/XML document[RDFX],
then the RDF graph represented by that document
is a GRDDL result of IR.
|
in section Example: Using GRDDL with an XML Schema namespace document
in section 4. Using GRDDL with valid XHTML
in section An example Dublin Core META transformation
in section Multiple transformations in XHTML
An XHTML document whose metadata profile names
include http://www.w3.org/2003/g/data-view
has a GRDDL transformation for each resource identified by
a link of type transformation.
|
Given an XPath root node N of an XHTML document,
for each space-separated
token REF in the value of the profile
attribute of the head element E,
the absolute form of REF with respect to the
base URI of E is a metadata profile name of
N.
|
In an XHTML family document with XPath root node N,
each a and link descendant
E with a rel attribute is a
typed link of N whose
target is the resource identified by the absolute
form of the href attribute with respect
to the base of E and whose type is
the value of the rel attribute of E.
|
in section 5. GRDDL for HTML Profiles
If
- an information resource PDOC, identified by a URI
PNAME has a GRDDL result that includes a triple
whose
- subject is PDOC, whose
- predicate is the property
<http://www.w3.org/2003/g/data-view#profileTransformation>,
and whose
- object is TX,
- and an information resource
IR has an XML representation with
root node NODE that has a metadata
profile name PNAME,
then TX is a GRDDL
transformation of NODE.
|
in section 6. Transformation Algorithms
If
- RDFXML is the root XPath node of a
conforming RDF/XML document[RDFX]
that represents an RDF Graph G, and
- R is the root node of some XML document
and TXNODE is the root node of
an XSLT transformation[XSLT1], and
- RDFXML is the root node of the
XSLT result tree when TXNODE
is applied to R, and
- TXDOC is an information
resource
with transformation property
TP
represented by an XML document
with root node TXNODE
then TP relates R to G.
|
If TXDOC is
a GRDDL transformation of some node,
then it has a transformation property
that is a functional relationship between
XPath nodes and RDF graphs.
@@This can probably be expressed
in OWL in the schema rather than as a rule.
|
in section 7. Security considerations
in section Example: A GRDDL-aware Agent protocol trace
in section 8. The GRDDL Vocabulary
in section 9. References
in section Normative References
in section Informative references
in section Appendix: Transformations for Styling versus data extraction
in section Appendix: Issues
in section Appendix: Implementation Experience: Test Cases, Software, and Services
in section Acknowledgements and Change History
$Revision: 1.6 $ of $Date: 2007/02/16 23:41:46 $
generated from $Id: spec.html,v 1.215 2007/02/16 23:40:38 connolly Exp $
via normonly.xsl$Id: normonly.xsl,v 1.1 2006/11/10 05:02:50 connolly Exp $