<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:daml="http://www.daml.org/2001/03/daml+oil#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://www.daml.org/tools/wishlist-ont#">
  <Wishlist>
    <daml:versionInfo>$Id: wishlist.xml,v 1.44 2003/11/17 01:44:20 mdean Exp $</daml:versionInfo>
    <tool>
      <Tool rdf:ID="validator">
        <name>DAML Validator</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[ 
   Current tools will check DAML syntax, but not check for the
   existence of referenced ontologies, definition of Classes and
   properties, check property ranges/domains, identify references to
   undefined URI's, etc.
   <p />
   Ideally, the validator would have a WWW interface (hosted on
   www.daml.org) and also be downloadable for local bulk use.
   <p />
   The W3C HTML Validator and the ICS-FORTH Validating RDF Parser
   might provide useful starting points.  It would be great if this
   could be packaged as a plug-in to XML Spy.
   <p />
   <a href="mailto:drager@bbn.com">Dave Rager</a>
   is working on this.
   See 
   <a href="http://www.daml.org/validator/">here</a>.
   <p />
   ISI has volunteered to maintain a WebScripter list
   (<a href="http://www.isi.edu/webscripter/validator.gen.html">static</a>
    and
    <a href="http://aquinas.isi.edu/webscripter/ws?reportURL=http%3A%2F%2Fwww.isi.edu%2Fwebscripter%2Fvalidator.wsrd&reportXSL=">dynamic</a>)
   of desired Validator features.
   If you wish to contribute to this list,
   <ol>
     <li>copy 
         <a href="http://www.isi.edu/webscripter/mrf-validator.d.daml">this DAML file</a>
         to a publicly accessible Web server
     <li>substitute your to-do items
     <li>send the URL where you put it to <a href="mailto:frank@isi.edu">frank@isi.edu</a>
   </ol>
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="damlapi">
        <name>DAML API</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   There may be DAML-specific abstractions that could be built above
   the existing RDF API.  For example, the DAML API might implement a
   node-centric rather than a statement-centric view.
   <p />
   Java implementations of the DAML API should be put in the org.daml
   package.
   <p />
   GRCI has released a
   <a href="http://grcinet.grci.com/maria/www/codipsite/Tools/Components.html">DAML API</a>.
   <p />
   <a href="http://www.hpl.hp.com/semweb/">Jena</a>
   now includes a DAML API.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="mozilla_sidebar">
        <name>DAML Mozilla Sidebar</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[ 
   The <a href="http://www.mozilla.org">Mozilla</a> browser supports
   "sidebars" which can monitor the content of the current window.  We
   would like to develop a sidebar that would indicate when a page
   contains DAML content and allow the user to browse the available
   statements, referenced ontologies, etc.
   <p />
   An early prototype was developed by BBN and demonstrated at the
   DAML Kickoff Meeting.
   <p />
   <a href="mailto:mike@yellowhouseassociates.com">Mike Schrader</a>
   has implemented the
   <a href="http://yellowhouseassociates.com/damlbar">DAML Sidebar</a>.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="ontedit">
        <name>DAML Ontology Editor</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   Several developers are working on tools to define ontologies in UML
   or PowerPoint, or by combining existing theories.  No one is
   currently developing a GUI to create an ontology "from scratch" in
   DAML terms.
   <p />
   Protege can be used to create/modify RDF Schemas, and could
   probably be extended to handle DAML.  Ontolingua now handles
   DAML-ONT.
   <p />
   <a href="http://img.cs.man.ac.uk/oil/">OilEd</a> may fulfill this
   role.
   <p />
   SRI has developed a DAML+OIL plugin for Protege.
   The Protege team is now developing a plugin for OWL.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="markup">
        <name>DAML Markup Tool</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   We would like a GUI tool that allows a user to add DAML statements
   to existing HTML pages.
   <p />
   We may be able to leverage Jeff Heflin's <a
   href="http://www.cs.umd.edu/projects/plus/SHOE/KnowledgeAnnotator.html">Knowledge
   Annotator</a> for SHOE
   and/or W3C's
   <a href="http://www.w3.org/2001/Annotea/">Annotea</a>.
   <p />
   For DAML Homework Assignment 1, Stanford KSL developed a tool to
   take DAML instance information and distribute it among HTML pages.
   <p />
   <a href="http://ontobroker.semanticweb.org/annotation/">OntoMat</a>
   does this.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="instance">
        <name>DAML Instance Editor</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   We would like to have a tool that can be used to create, modify,
   and associate instances of DAML classes based on a DAML Ontology.
   <p />
   Mike Dean <a
   href="http://www.daml.org/projects/integration/homework/1/lessons.html">adapted</a>
   BBN's paramedit tool to generate RDF and RDF Schema for use in DAML
   Homework Assignment 1.
   <p />
   Siegfried Handschuh has developed
   <a href="http://ontobroker.semanticweb.org/annotation/">OntoMat</a>. 
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="map">
        <name>DAML Ontology Mapping Tool</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#idea"/>
        <description><![CDATA[
   We need a GUI to allow a user to define/refine the mapping between
   2 ontologies.
   <p />
   It might be desirable to extend the Microsoft BizTalk Mapper to do
   this.
   <p />
   We may be able to leverage the merging system of Chimaera to help
   with the mapping problem.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="gateway">
        <name>HTML to DAML (DAML Gateway)</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#inprogress"/>
        <description><![CDATA[
   It would be desirable to have a general set of tools and techniques
   to easily construct gateways that provide a DAML interface to
   existing non-DAML WWW sites.
   <p />
   Stanford KSL and SRI have used W4 and WebL to provide OAA
   interfaces to WWW sites.
   <p />
   Could this be driven directly off 
   <a href="http://www.daml.org/services/">DAML-S</a>
   service descriptions?
   <p />
   Mike Dean has started to develop a set of
   <a href="http://www.daml.org/2001/10/html/">DAML HTML Gateway tools</a>.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="xsd">
        <name>XML to DAML</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#inprogress"/>
        <description><![CDATA[
   It would be desirable to be able to import any XML data set as DAML
   content.  XML DTDs primarily express "contains" relationships among
   element types and element attributes.
   <p />
   At least two approaches are possible: 1) provide general tools and
   techniques (e.g. XSLT) to generate DAML from XML, 2) specify rules
   which allow the direct mapping from an XML Document Object Model to
   a DAML model.
   <p />
   A tool that converted from XML Schema to DAML+OIL (March 2001 or later,
   with data type support)
   would be very useful.
   <p />
   <a href="mailto:neighbors_mark@bah.com">Mark Neighbors</a>
   of Booz-Allen is
   implementing an XML Schema to DAML translator.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="xslt">
        <name>DAML XSLT</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#inprogress"/>
        <description><![CDATA[
   XSLT is a very powerful langage for processing XML data.  It would be
   great to be able to use XSLT for processing DAML.  Rather than
   an XML document, it should be possible to run an XSLT
   stypesheet over a DAML document or a DAML knowledge base.  This would have
   to account for some differences:
   <ul>
     <li>DAML documents do not have a distinguished root
         (a Class might be specified instead -- the leaves of the simulated
	 root would consist of all instances of that class)</li>
     <li>DAML documents describe graphs rather than trees</li>
     <li>DAML documents allow cycles (but most XSLT scripts only traverse
         a fixed number of levels)</li>
   </ul>
   but these seem surmountable.
   <p />
   The 
   <a href="http://xml.apache.org/">Apache xalan</a>
   implementation of XSLT (versions 1 and 2)
   provides interfaces to support a DOM model as input.  This DOM model
   could be "lazily" created from a DAML document and/or knowledge base.
   <p />
   Mike Dean has done some work on a prototype implementation.
   <p />
   See also 
   Stefan Kokkelink's
   <a href="http://zoe.mathematik.uni-osnabrueck.de/QAT/qat.html">Querying and transforming RDF</a>.
   <p />
   Booz-Allen has released an initial implementation of their
   <a href="http://www.davincinetbook.com:8080/daml/damlxslt/">DAML/XSLT Adapter</a>.
   <p />
   N3 rules can be used with cwm's --filter option to perform such graph transformations.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="hyperdaml">
        <name>Hypertext DAML Ontologies</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   For viewing ontologies (e.g. in the 
   <a href="http://www.daml.org/ontologies/">DAML Ontology Library</a>),
   it would be helpful to have a tool that could markup a DAML ontology
   (class and property definitions) to add anchors for IDs, provide hyperlinks
   to referenced resources, etc.
   <p>
   <a href="http://www.daml.org/2001/04/hyperdaml/">HyperDAML</a>
   has now been implemented.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="diff">
        <name>DAML diff</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#inprogress"/>
        <description><![CDATA[
   The structure and semantics of DAML offers leverage advantages in comparing
   evolving
   DAML content over time (e.g. last month's version of a DAML-ized
   project plan vs this month's).  This could also potentially relate to the
   work that DRC and Jeff Heflin have done on versioning.
   <p>
   <a href="http://www-uk.hpl.hp.com/people/bwm/rdf/jena/index.htm">Jena</a>
   1.1 includes <code>jena.rdfcompare</code>,
   which tests for equivalence.
   <p>
   W3C
   <a href="http://www.daml.org/2001/04/iow/mit/">is developing</a>
   an RDF/DAML repository difference calculation module.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="emacs">
        <name>DAML emacs mode</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   The GNU emacs text editor supports modes customized to support editing
   of different programming languages and other structured data formats.
   A mode specifically designed for DAML (probably based on an existing
   SGML or HTML mode) would be valuable.
   <p />
   <a href="mailto:burstein@bbn.com">Mark Burstein</a>
   has released 
   <a href="http://openmap.bbn.com/~burstein/daml-emacs/">DAML Emacs Mode</a>.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="graphfilter">
        <name>Graph Filtering</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   It would be desirable to have general tools for filtering
   DAML+OIL content based on user preferences,
   e.g. for download into
   <a href="http://www.daml.org/PalmDAML/">PalmDAML</a>.
   A general purpose program 
   might take a collection of DAML source URIs and user preferences
   and use tagging to associate a weight/value with each
   node and arc (based on node type, property type, proximity to
   other interesting objects, etc.) and then produce a file containing
   the highest priority statements
   (limited by size or other criteria).
   <p />
   Booz-Allen is working on this.
   <p />
   cwm includes several facilities for filtering.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="cvsweb">
        <name>DAML-ized cvsweb</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#idea"/>
        <description><![CDATA[
   Many open source and other projects use the
   <a href="http://www.cvshome.org">Concurrent Versions System (CVS)</a>
   for source code control.
   CVS collects historical statistics with each file
   and in a central repository history file.
   Several tools such as 
   <a href="http://viewcvs.sourceforge.net/">ViewCVS</a>
   (used by 
    <a href="http://www.sourceforge.net">SourceForge</a>)
   and
   <a href="http://stud.fh-heilbronn.de/~zeller/cgi/cvsweb.cgi/">cvsweb</a>
   (used by
    <a href="http://dev.w3.org/cvsweb">W3C's public CVS repository</a>)
   provide a WWW interface to CVS repositories.
   Modifying one or more of these tools to produce DAML+OIL as well as HTML
   versions of the log data,
   and getting the changes incorporated into their official releases,
   could provide widespread use of DAML and
   greatly ease analysis of this data.
   It could also introduce DAML to the community of open source developers.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="n3java">
        <name>Java N3 Parser</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   <a href="http://www.w3.org/DesignIssues/Notation3.html">Notation 3 (N3)</a>
   is becoming widely used as a presentation syntax for DAML+OIL.
   The only tool that currently supports N3,
   <a href="http://www.w3.org/2000/10/swap">cwm</a>,
   is written in Python.
   A Java implementation of N3 would open it to a wider
   audience
   and allow direct use by tools such as the 
   <a href="http://www.daml.org/crawler/">DAML Crawler</a>. 
   <p>
   Jena 2 includes an N3 parser.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="fastdaml">
        <name>High-Performance DAML Parser</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#inprogress"/>
        <description><![CDATA[
   Current RDF/DAML parsers
   consume large
   amounts of CPU and memory when processing significant data sets.
   <a href="http://www.daml.org/2001/07/pi-integration/slide3-0.html">Preliminary analysis</a>
   suggests that this is in large part due to the
   layered implementation of these tools (e.g. XML, RDF statements, nodes).
   A DAML-specific Java parser designed and implemented from the outset to minimize processing time and memory consumption
   could remove this limitation and be of great benefit in promoting widespread use of DAML.
   <p />
   Short of a new implementation from scratch,
   use of the Document Table Model (DTM) in
   <a href="http://xml.apache.org/xalan-j/index.html">Xalan-Java 2</a>
   might be helpful.
   <p />
   Booz-Allen plans to work on this.
   <p />
   <a href="http://www.hpl.hp.com/semweb/">ARP</a>
   provides a streaming parser with good performance.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="erwin2daml">
        <name>ERwin to DAML Translator</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#implemented"/>
        <description><![CDATA[
   ERwin from Computer Associates is an entity-relationship modeling tool
   used by many projects to design relational databases.
   It would be useful to be able to translate an ERwin model into a DAML+OIL ontology,
   similar to what we can do with UML 
   (a streamlined procedure for converting ERwin to UML and UML to DAML+OIL is also a
   possibility).
   <p>
   ERwin 4.0 can store an XML representation of the model.
   Mike Dean has done some preliminary work in mapping this representation to DAML+OIL.
   <p>
   The Unicorn System can read ERwin and export DAML+OIL or OWL.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="java2daml">
        <name>Java to DAML Translator</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#inprogress"/>
        <description><![CDATA[
   Since many projects already have "ontologies" encoded as Java classes,
   it would be useful to be able to generate
   DAML+OIL ontologies from Java class definitions
   and DAML+OIL content from Java objects.
   <p>
   Mike Dean is working on 
   <a href="http://www.daml.org/2001/09/java2daml/">java2daml</a>,
   which includes use of XML Schema datatypes and cardinality constraints.
   <p>
   The 
   <a href="http://www.dfki.uni-kl.de/frodo/rdf2java/">FRODO rdf2java</a>
   tool provides bi-directional mappings for RDF.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="ldap2daml">
        <name>LDAP to DAML</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#idea"/>
        <description><![CDATA[
   Provide a tool to export information available via the
   Lightweight Directory Access Protocol (LDAP)
   in DAML format.
   <p>
   See the
   <code>javax.naming.ldap</code>
   package in JDK 1.3+.
  
  
 ]]></description>
      </Tool>
    </tool>
    <tool>
      <Tool rdf:ID="forms">
        <name>DAML Forms</name>
        <state rdf:resource="http://www.daml.org/tools/wishlist-ont#idea"/>
        <description><![CDATA[
   Investigate whether
   <a href="http://www.w3.org/MarkUp/Forms/">XForms</a>
   can be effectively used to generate DAML content.
  
  
 ]]></description>
      </Tool>
    </tool>
  </Wishlist>
</rdf:RDF>
