<?xml version="1.0"?>

<!DOCTYPE owl [
	<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
	<!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">
	<!ENTITY owl "http://www.w3.org/2002/07/owl#">
	<!ENTITY cc "http://web.resource.org/cc/#">
	<!ENTITY person "http://ebiquity.umbc.edu/ontology/person.owl#">
	<!ENTITY project "http://ebiquity.umbc.edu/ontology/project.owl#">
	<!ENTITY pub "http://ebiquity.umbc.edu/ontology/publication.owl#">
	<!ENTITY assoc "http://ebiquity.umbc.edu/ontology/association.owl#">
	<!ENTITY research "http://ebiquity.umbc.edu/ontology/research.owl#">
	<!ENTITY assert "http://ebiquity.umbc.edu/ontology/assertion.owl#">
]>

<!--

This ontology document is licensed under the Creative Commons
Attribution License. To view a copy of this license, visit
http://creativecommons.org/licenses/by/2.0/ or send a letter to
Creative Commons, 559 Nathan Abbott Way, Stanford, California
94305, USA.

-->

<rdf:RDF 
		xmlns:rdf = "&rdf;"
		xmlns:rdfs = "&rdfs;"
		xmlns:xsd = "&xsd;"
		xmlns:owl = "&owl;"
		xmlns:cc = "&cc;"
		xmlns:person = "&person;"
		xmlns:project = "&project;"
		xmlns:pub = "&pub;"
		xmlns:assoc = "&assoc;"
		xmlns:research = "&research;"
		xmlns:assert = "&assert;">
	<project:Proposal rdf:about="http://ebiquity.umbc.edu/project/html/id/52/OWLCHecker">
		<rdfs:label><![CDATA[OWLCHecker]]></rdfs:label>
		<project:title><![CDATA[OWLCHecker]]></project:title>
		<project:description><![CDATA[<p>Develop a tool to help OWL ontology writers follow good style.  The
first step is to come up with a set of style conventions. these could
include conventions for documentation, importing ontologies,
organization, etc.  An author could apply the tool to an ontology and
get a HTML report on warnings and errors detected by the checker.</p>

<p>One model might be <a href="http://checkstyle.sourceforge.net/"> Checkstyle</a>
-- a development tool to help programmers write Java code that adheres
to a coding standard. It automates the process of checking Java code
to spare humans of this boring (but important) task. This makes it
ideal for projects that want to enforce a coding standard.  It's
highly configurable and can be made to support almost any coding
standard. An example configuration file is supplied supporting the Sun
Code Conventions. As well, other sample configuration files are
supplied for other well known conventions.</p>
]]></project:description>
		<project:startDate rdf:datatype="&xsd;dateTime">2004-02-01T00:00:00-05:00</project:startDate>
		<project:endDate rdf:datatype="&xsd;dateTime">2004-12-01T00:00:00-05:00</project:endDate>
		<project:tag><![CDATA[ontology]]></project:tag>
		<project:tag><![CDATA[owl]]></project:tag>
		<project:tag><![CDATA[style checker]]></project:tag>
	</project:Proposal>

<rdf:Description rdf:about="">
	<cc:License rdf:resource="http://creativecommons.org/licenses/by/2.0/" />
</rdf:Description>

</rdf:RDF>
