<?xml version="1.0"?>
<!DOCTYPE rdf:RDF [
  <!ENTITY rdfs 'http://www.w3.org/2000/01/rdf-schema#'>
  <!ENTITY xsd 'http://www.w3.org/2001/XMLSchema#'>
  <!ENTITY data 'http://sswapmeet.sswap.info/data/'>
  <!ENTITY owl 'http://www.w3.org/2002/07/owl#'>
  <!ENTITY rdf 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>]>
<rdf:RDF
    xmlns:rdf="&rdf;"
    xmlns:owl="&owl;"
    xmlns:data="&data;"
    xmlns:xsd="&xsd;"
    xmlns:rdfs="&rdfs;">
    <owl:Ontology rdf:about="&data;owlOntology">
        <owl:imports rdf:resource="&data;owlOntology"/>
    </owl:Ontology>
    <owl:Class rdf:about="&data;Accessor"/>
    <owl:ObjectProperty rdf:about="&data;hasAccessor">
        <rdfs:comment rdf:datatype="&xsd;string">A predicate for associating an accessor with a data object; for example, a link to user authentican and authorization.   One model is where the subject of data:hasAccessor--a node of rdf:type data:DataFormat--is a blank node, and access to the data is via the object (the value) of the data:hasAccessor property.  In this manner data:hasAccessor can be used to model data indirection.</rdfs:comment>
        <rdfs:range rdf:resource="&data;Accessor"/>
        <rdfs:label rdf:datatype="&xsd;string">has Accessor</rdfs:label>
        <rdfs:subPropertyOf>
            <owl:ObjectProperty rdf:about="&data;hasInputProcessor"/>
        </rdfs:subPropertyOf>
    </owl:ObjectProperty>
</rdf:RDF>

