All, (01)
Wow! 44 postings in 4 days. 15 different people have posted to the
discussion and another three or four have jointed the forum. (02)
I think that we have a viable project (assuming that all us cats can
be herded effectively). (03)
We are still officially in the planning phase, but a number of
conversations have already gotten traction (a semi-detailed analysis
follows). Not too surprising, the conversation has been heavily
focused on tools and technologies. (04)
My first reaction is to employ a conquer and divide strategy: (05)
* Start a thread / team to focus on goals and objectives. (06)
* Start a thread / team to focus on process and project management. (07)
* Let the conversations on tools and modeling issues continue at
their own pace, but try to add a bit more rigor. For each technology
option, provide:
* Name of the Technology
* Functional Description
* Features
* Strengths
* Weaknesses
* Source
* Licensing (08)
* Let the other topics shake out, as appropriate. (09)
A more traditional development model would start with requirements
definition, but I don’t think that the other topics could be
effectively tabled, at this time. Also, what we choose to accomplish
is likely to be what can be achieved by leveraging established
technologies and process. Therefore, I expect that the inventory of
tools and techniques to be a critical input to the scoping and
requirements definition decisions that we need to make. (010)
Many of the potential requirements for this project are implicit in
the technical descriptions that have been provided. Accordingly, for
the next week or so, I suggest that we work both ends towards the middle. (011)
I also propose that we hold a kickoff teleconference relatively soon,
preferably Wednesday, March 12th. At this time, two time-slots are
available: 10:30-12:00 PST (1:30-3:00 EST) or 1:00-2:30 PST
(4:00-5:30 EST). (012)
How many of you could attend a telecon next Wednesday? Which time
would be prefable? (013)
/s/ kwc 2003.03.06 23:33 (014)
QUICK ANALYSIS OF DISCUSSION TO DATE: (015)
Goals (016)
* Identify appropriate metrics to measure and capture those measures
during this project (as a starting point to developing guidance).
[Norma Slattery] (017)
* Open Source [Farrukh Najmi, Mike Daconta, Duane Nickull] (018)
* Concurrent ontology development tools [Leo Obrst] (019)
* Parallel development of a real-life public-domain APPLICATION that
uses the ontology in a non-trivial way to illustrate the reasoning
capacity that the ontology is intended to provide (select one which
is freely available or build one) [Patrick Cassidy] (020)
* Learn about and refine our ontology building skills [Mike Daconta] (021)
* Craft an ontology suitable for adoption by the UBL committee, which
presumes that acceptance equates to accurate modeling of the domain
[Mike Daconta] (022)
* Apply medical ontologies using ebXML Registry [Farrukh Najmi] (023)
* Role: Volunteer to develop use cases [Mike Daconta] (024)
Process and Project Management (025)
* Collaborative work environment options [Peter Yim] (026)
* Need: Someone who has working proficiency with Protégé and is
willing to provide some working guidance/leadership [Peter Yim]
** Response: I have a working proficiency and am willing to provide
Protégé guidance as best as I can. Start by reviewing
http://protege.stanford.edu/publications/ontology_development/ontology101.html
[Mike Daconta] (027)
* Planning/tasking session at the beginning to develop some goals for
the collaboration, etc. [Leo Obrst] (028)
* Agreement on a firm set of rules as to how controversies are to be
decided, and a set of deadlines as to when particular phases of the
effort should be completed [Patrick Cassidy] (029)
* Role: UBL consultant to the project [Tim McGrath] (030)
* Develop some concrete goals for the utility of the ontology beyond
the development of an accurate model [Mike Daconta] (031)
* Consider following the simple ontology development simple process
outlined in the ontology101.html document [Mike Daconta] (032)
* Define some use-cases for the ontology [Mike Daconta] (033)
* Translation/refinement of UBL models [Mike Daconta, Dean Black,
Patrick Cassidy, Leo Obrst] (034)
* Guarino and Welty's OntoClean methodology (now merged with
Methontology) [Leo Obrst] (035)
* NexistWiki [Jack Park] (036)
Opportunities & Threats (037)
* An independent UBL ontology effort could either help normalize
other UBL-related efforts (OAG, UCC/EAN, PIDX, RosettaNet, etc.) or
could be seen as repetitive [John Yunker] (038)
* Drive the requirements and features of ebXML Registry V4 [Farrukh Najmi] (039)
Technology Options (040)
* Use an ebXML Registry as an Ontology/Terminology Server (extend /
include V4 ontology support) [Farrukh Najmi, Mike Daconta, Duane
Nickull, Leo Obrst, John Yunker] (041)
* Protégé [Peter Yim, Leo Obrst] (042)
* Agreed-upon representation language [Leo Obrst] (043)
* Use MS Enterprise Architect and UML-ORM tools to extend the core
documents and related schema [Bob Smith] (044)
* Protégé with OntoViz plugin, using RDF/S as the representation
language [Mike Daconta] (045)
* Content management system [Farrukh Najmi] (046)
* OWL [Farrukh Najmi] (047)
* Open-ended ontology inference engine [Farrukh Najmi] (048)
* Various representation languages (UML, XML [DTDs and Schemas]),
OKBC knowledge model, KIF, Common Logic) [Leo Obrst] (049)
* Prolog engine (XSB, Amzi!, binProlog) [Leo Obrst] (050)
* OntologyWorks tool [Leo Obrst]
* FLORA language plug in for Protégé [Leo Obrst] (051)
* Java + Prolog [Leo Obrst] (052)
* JESS (Java Expert System Shell based on CLIPS) [Leo Obrst] (053)
* IODE from OntologyWorks [Michael Uschold] (054)
* Ontolingua (translation from KIF to Prolog) [Leo Obrst] (055)
* ISO-IEC-11179 classification standard [Leo Obrst] (056)
Application Models (057)
* Deductive database (logic programming + relational database, so
that you get inference and set at a time operations from a RDB) [Leo
Obrst] (058)
Issues (059)
* Formalization model(s) [Mike Daconta] (060)
* Common definition of Ontology (e.g., vs Taxonomy) (061)
___________________________________________________________________
Kurt Conrad
2994 Salem Dr. 408-247-0454
Santa Clara, CA 95051-5502 408-247-0457 (data/fax)
http://www.SagebrushGroup.com mailto:conrad@xxxxxxxxxxxxxxxxxx (062)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Community Wiki: http://ontolog.cim3.net/wiki/
Shared Files: http://ontolog.cim3.net/file/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (063)
|