DAML Task Signup by Team

This page lists the task(s) that each team signed up for during the July 2001 DAML PI Meeting.

Please send updates or corrections to Jim Hendler and Mike Dean

Team	Task(s)
bah	DAML XSLT filtering capabilities http://www.daml.org/tools/wishlist.daml#filtering XML Schema
bbn	DAML emacs mode
bowie	supporting Ralph Swick with Web Services industry participation
cmu	initial tools for linking ontologies
cycorp	DAML Dublin Core
drc	new ontology: glossary new ontology: mine clearing/explosive ordnance disposal (EOD) new ontology: task list (UJTL, etc)
grci	Performance/Scalability Analysis UML Visualization DAML API
isi	release WebScripter by Sept 15, including concise training materials
lm	DAML Design Case Studies
mit	DAML diff
sri	publish initial ontologies of resources and execution processes by mid-Sep tie up core DAML-S
stanfordDB	DAML+OIL interoperability with Topic Maps DAML+OIL importable to XSB
stanfordKSL	initial DAML+OIL query language document tie-up DAML-S initial release of JTP reasoner
teknowledgeLA	installation package for Briefing Associate with tutorial
teknowledgePaloAlto	deployment of semantic search engine including support for DAML+OIL subclass/subproperty
umbc	ontology for distributed trust with use cases for IT talks HAIRCUT use of DAML Crawler content provide agent and human interfaces to query HAIRCUT DAML Design Case Studies publish ontology showing DAML as FIPA-compliant content language post strawman DAML-Rules
uwf	Equivalent Semantics
yale	PDDL to DAML translator, storing currently inexpressible items as reified statements.

Colophon

This page was generated from

URI daml:versionInfo

http://www.daml.org/2001/07/signup/signup.daml $Id: signup.daml,v 1.9 2001/07/25 11:20:37 mdean Exp $

http://www.daml.org/researchers.daml#DAML $Id: researchers.xml,v 1.46 2001/07/31 06:50:53 mdean Exp $

http://www.daml.org/2001/07/signup/teams.n3 $Id: teams.n3,v 1.13 2001/08/07 15:37:17 mdean Exp $

and possibly other inputs using teams.xsl, a version of DAML XSLT, and genhtml.bat.

URI	daml:versionInfo
http://www.daml.org/2001/07/signup/signup.daml	$Id: signup.daml,v 1.9 2001/07/25 11:20:37 mdean Exp $
http://www.daml.org/researchers.daml#DAML	$Id: researchers.xml,v 1.46 2001/07/31 06:50:53 mdean Exp $
http://www.daml.org/2001/07/signup/teams.n3	$Id: teams.n3,v 1.13 2001/08/07 15:37:17 mdean Exp $

Lessons learned/relearned include:

DAML XSLT needs to accept multiple model inputs (unlike XML XSLT)
daml:versionInfo can be applied to any resource
DAML XSLT needs to provide access to the URI associated with each node (e.g. @uri and @fragment)
DAML XSLT should provide access to the URIs used as model inputs
It can be very useful to be able to give a property either a xsd:string or object value (as also found in Dublin Core).
We don't have a great way of associating additional/elaboration information with a relation, e.g. linking to DAML Design Case Study and then indicating what the case study is about. If we'd recognized this when designing the ontology, we could have created an extra object to hold both link and a comment. Reification is also a possibility, though awkward and not consistently supported.