ppy/chat-transcript_unedited_20110519a.txt ----------- PeterYim: Welcome to the OntologySummit2011 review and follow-up action planning ("postmortem") session - Thu 19-May-2011 * Chair: Dr. SteveRay and Dr. NicolaGuarino Please refer to details on session page at: http://ontolog.cim3.net/cgi-bin/wiki.pl?ConferenceCall_2011_05_19 . anonymous morphed into vnc2 Ali Hashemi: Does vnc work for anyone? PeterYim: @Ali - no ... you will have to call out the advance, and I will advance the slides for you PeterYim: session starts SteveRay: Matthew: Went well - maturity of how participants approached the topic Michael Uschold: Was it anyone's job to get media coverage? IF not, that is the explanation. LeoObrst: sorry, must call back in! anonymous morphed into FabianNeuhaus SteveRay: In the future, need a publicity chair (Uschold, Obrst) PeterYim: +1 on Gruninger's point about the panel at the Symposium - I agree it went real well and provided a good range of perspectives SteveRay: Gruninger: could have done better on the challenge problems PeterYim: @Steve - vnc still working properly here SteveRay: VNC is back for me - it hiccuped and required me to log in again. FabianNeuhaus: I am basking PeterYim: presentations continued - [ 1-Ray ] (slide#8 now) SteveRay: Michael: Can't help observing that we're really in an Epilogue, rather than a Prologue as noted on your slide. (Shocking misuse of a term for an ontologist! PeterYim: == MichaelUschold presenting == [ 2-Uschold ] LeoObrst: I think that Michael's Ontology Usage Catalog could also become part of the Open Ontology Repository, at some point, since the points on his slide 2 are largely also addressed by the OOR. SteveRay: Michael: What is the relationship between your work and the Open Ontology Repository? RexBrooks: Sorry I'm late folks-conflicting telecon, about an emergency management ontology. PeterYim: Nicola: in favor of Michael's proposal ... cataloging is good, but qualifying it as "exemplary" could be dangerous Ali Hashemi: With respect to the summit, it is also an issue of how suitable the example ontology is for making a case. The OOR encompasses a broader range of ontologies NicolaGuarino: According to the authors, "An exemplary ontology is one that can serve as a model that can be imitated or leveraged by ontology engineers in the future. The most fundamental property of an exemplary ontology is being well designed for its intended purpose". This is risky. LeoObrst: Jumping ahead a bit, Potential Topics for Ontology Summit 2012: 1)Ontology Best Practices, Methodologies, Evaluation, 2) Ontology Self-Correction, Automated Growth, Ontology Learning. To some extent both of these were mentioned at the Symposium. NicolaGuarino: (of course we need some way of quality evaluation, of course) Michael Uschold: Agree with @Nicola about having a way to enter things into a repository, without having to commit to it being exemplary. I agree. The exemplary ontology catalog is just an example of a semantic-form based catalog. An ontology usage framework could use a similar approach. Whether or not we choose to rate the quality of ontology uses is a discussion about just one attribute of the ontology usage, not a big issue per se. MatthewWest: Apologies, but I have to leave now. PeterYim: bye, Matthew Michael Uschold: @Nicola: can you comment on the publication of ontology usages in AoJ accordign to some kind of standard format? RexBrooks: I'll give the standing use-case library some thought. I promised other groups that I would catch on work that took a lower priority before the summit, so I can't commit now, but I may commit after those projects are up to date. LeoObrst: Maybe AO could institute a kind of New Ontologies of Interest section? Brief descriptions of ontologies and their use cases? PeterYim: would those who are not speaking please mute yourself - "*2" NicolaGuarino: Ali's voice arrives extremely bad to me... SteveRay: @Nicola: For me too. Must be Ali's connection. NicolaGuarino: @Michael: definitely we are open to publish ontology usages on the AOJ, but honestly I have no idea of the proper format (there was some discussion with Michael Gruninger at the summit) RexBrooks: Thought for next year's Summit: How do we make people aware of ontooogy by saying "Did you know that YOU have an ontology? Michael Uschold: I could not agree more with Ali Hashemi that there needs to be a better way to show off the results of our work. I do not like sending people to our working wiki site. RexBrooks: The point is showing how there are imoplicit ontologies everywhere, and making people aware of it. What are the consequences of willy nilly ontological practices? NicolaGuarino: @Ali: I definetly support the idea of a nice (non wiki-based) website, certainly it would be great to point at it from the IAOA.org web site (and from MANY different places). RexBrooks: How to put that into a a Summit Theme is a good question. PeterYim: == Brainstorm on possible theme for next year's Ontology Summit == PeterYim: LeoObrst: Jumping ahead a bit, Potential Topics for Ontology Summit 2012: 1)Ontology Best Practices, Methodologies, Evaluation, 2) Ontology Self-Correction, Automated Growth, Ontology Learning. To some extent both of these were mentioned at the Symposium. Michael Uschold: I propose "Ontology Engineering best practice" Michael Uschold: I think that Ontology best practice is too big. PeterYim: a possible theme that came across (when Matthew and I were doing "Strategies") is "Making the Case for Ontology Research" Michael Uschold: I think ontology learning is too small a topic, very important, but represents small part of the cmty PeterYim: it was suggested before (in previous years) the theme of "Ontology and Software and Engineering" - and create a platform to pull together these two communities MichaelGruninger: Rather than ontology learning the topic can be broadened to ontology acquisition e.g. extracting ontologies from unstructured knowledge LeoObrst: I agree that Evaluation is a potentially big topic, as that NIST workshop made clear: many approaches. PeterYim: ERRATA: "Ontology and Software Engineering" FabianNeuhaus: I agree with Nicola, when I said "Best Practices" I should have said "Best Practices & Methodologies" SteveRay: @Peter: or..."Ontology and Systems Engineering" NicolaGuarino: @Peter: BTW, "Making the case for ontology research" is a GREAT topic, although perhaps less popular than best practices & methodology YuriyMilov: alternatives NicolaGuarino: Also: research challenges for ontologies Ali Hashemi: Ontologies as Part of Knowledge Systems (how it fits into other technologies) YuriyMilov: "challenges for ontologies" I agreed RexBrooks: Similar to Best Practices and Software Engineering, and building on this year's topic, I would suggest something along the lines of "What is Ontology Good For? it breaks down into Tracks for things like performance, collateral benefits, etc. MichaelGruninger: Challenge Problems for Ontology Design and Applications LeoObrst: Perhaps related to "Ontology and Software/Systems Engineering" is "Developing Ontology Applications". RexBrooks: "Solving Problems with Ontology"? FabianNeuhaus: For the record, I suggested to distinguish "Ontology Best Practices, Methodologies" and "Evaluation of Ontologies" as separate topics PeterYim: +1 on Ali's "Ontologies as Part of Knowledge Systems" Ali Hashemi: Ontology acquisition might also resonate broadly, as it would help communicate how people who didn't realize they could use ontologies, could. TerryLongstreth: Back to its roots: Ontology usage for Philosophy and the Humanities PeterYim: Nicola / Steve: ask people to continue to contribute ideas (brainstorm on topics) - conversation can and should continue on the [ontology-summit] list PeterYim: Home page: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit LeoObrst: Adios! PeterYim: Steve suggest adding a link on that page to a place where people can suggest "future themes" NicolaGuarino: @Michael: once the communique is ready (with endorsement), submit it to Applied Ontology so we can publish it soon Ali Hashemi: Thank you all. PeterYim: -- session ended: 11:00am PDT -- ----------------