Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[higgins-dev] OWL for Bandit XML File Higgins Context Provider

Before I get into this, I should note that our XML File Context Provider
is largely experimental and we wouldn't necessarily envision it ever
being a production type thing.  However, it allows us to try out join
scenarios and it allows us a simple place to test out higgins interfaces
quickly.

That said, I've created an OWL ontology document that I'd like to
return from the Context.getSchema() call.  If we're understanding OWL
correctly, it's really quite simple for our XML File Context Provider. 
All we want to do allow open ended attribute data to be specified in our
XML File.  Basically, an Identity identifier and any attributes we want,
no other restrictions.

So, using Paul's example, here's the OWL I'd produce:

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#";
xmlns:owl="http://www.w3.org/2002/07/owl#";
xml:base="http://www.bandit-project.org/higgins/cp/xmlfile";>
	<rdf:Description rdf:about="urn:unnamed-1">
		<rdf:type>
			<rdf:Description
rdf:about="http://www.w3.org/2002/07/owl#Ontology"/>
		</rdf:type>
		<owl:imports>
			<rdf:Description
rdf:about="file:///c:/higgins0.4.4.owl"/>
		</owl:imports>
	</rdf:Description>
	<rdf:Description rdf:about="#Identity">
		<rdf:type>
			<rdf:Description
rdf:about="http://www.w3.org/2002/07/owl#Class"/>
		</rdf:type>
		<rdfs:subClassOf>
			<rdf:Description
rdf:about="http://www.eclipse.org/higgins/ontologies/2006/5/higgins#DigitalSubject"/>
		</rdfs:subClassOf>
	</rdf:Description>
</rdf:RDF>

Does this allow Identity to contain any arbitrary attribute?  I hoping
we're not required to specify everything that COULD be in an Identity
because, for the XML File Context Provider, that'd entail visiting every
Identity record and seeing what attributes we haven't published as
possibilities yet.

Tom



Back to the top