
<!-- Processed by Id: cwm.py,v 1.109 2002/10/08 20:59:07 timbl Exp -->
<!--     using base file:/devel/WWW/2002/11/rddl/ex1.n3-->


<rdf:RDF xmlns="file:/devel/WWW/2002/11/rddl/whatever#"
    xmlns:log="http://www.w3.org/2000/10/swap/log#"
    xmlns:rddl="file:/devel/WWW/2002/11/rddl/whatever#"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:xmls="file:/devel/WWW/2002/11/rddl/whgatever2#">

    <rdf:Description rdf:about="#0_work">
        <log:forAll rdf:resource="#c"/>
        <log:forAll rdf:resource="#p"/>
        <log:forAll rdf:resource="#x"/>
        <log:forAll rdf:resource="#y"/>
    </rdf:Description>

    <Namespace rdf:about="">
        <comment>This is a rather stilted example,
from RDF point of view, designed to look like the sort of thing
which Tim Bray thought the RDDL community was used to.
It introduces an abstract object which is a multiway relation
(like a database record) between the namespace, the supporting document,
and the nature of the document, and the purpose of the relation.
It looks flat, which may appeal.

rddl:resource is, here, the relationship between a namespace and one
of these things.  
</comment>
        <resource rdf:parseType="Resource">
            <rdf:type rdf:resource="whatever#validation"/>
            <nature rdf:resource="whgatever2#Schema"/>
            <prose>Use this to validate this document</prose>
            <related rdf:resource="http://example.org/L.xsd"/>
            <title>Validate</title>
        </resource>
        <resource rdf:parseType="Resource">
            <rdf:type rdf:resource="whatever#presentation"/>
            <nature rdf:resource="whgatever2#CSSStyleSheet"/>
            <related rdf:resource="http://garish.example.com/L.css"/>
            <title>Color me pink</title>
        </resource>
    </Namespace>
</rdf:RDF>
