From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2013: Virtual Panel Session-03 - Thu 2013-01-31     (1)

Summit Theme: "Ontology Evaluation Across the Ontology Lifecycle"     (1A)

Summit Track Title: Track-A: Intrinsic Aspects of Ontology Evaluation     (1B)

Session Topic: Intrinsic Aspects of Ontology Evaluation: Practice and Theory     (1C)

Panelists / Briefings:     (1E)

Abstract     (1J)

OntologySummit2013 Session-03: "Intrinsic Aspects of Ontology Evaluation: Practice and Theory" - intro slides     (1J1)

This is our 8th Ontology Summit, a joint initiative by NIST, Ontolog, NCOR, NCBO, IAOA & NCO_NITRD with the support of our co-sponsors. The theme adopted for this Ontology Summit is: "Ontology Evaluation Across the Ontology Lifecycle."     (1J2)

Currently, there is no agreed methodology for development of ontologies, and there are no universally agreed metrics for ontology evaluation. At the same time, everybody agrees that there are a lot of badly engineered ontologies out there, thus people use -- at least implicitly -- some criteria for the evaluation of ontologies.     (1J3)

During this Ontology Summit, we seek to identify best practices for ontology development and evaluation. We will consider the entire lifecycle of an ontology -- from requirements gathering and analysis, through to design and implementation. In this endeavor, the Summit will seek collaboration with the software engineering and knowledge acquisition communities. Research in these fields has led to several mature models for the software lifecycle and the design of knowledge-based systems, and we expect that fruitful interaction among all participants will lead to a consensus for a methodology within ontological engineering. Following earlier Ontology Summit practice, the synthesized results of this season's discourse will be published as a Communiqu��.     (1J4)

At the Launch Event on 17 Jan 2013, the organizing team provided an overview of the program, and how we will be framing the discourse around the theme of of this OntologySummit. Today's session is one of the events planned.     (1J5)

In this 3rd virtual panel session of the Summit, we focus on theory and practice for intrinsic aspects of ontology evaluation. Our speakers will present a number of approaches and frameworks for evaluating the quality of ontologies, and some theoretical discussion of what constitutes intrinsic evaluation. Our main goal in this virtual session is to begin to lay out the criteria for intrinsic evaluation of ontologies, some possible metrics, and the rationale for these. We hope that all of the participants in the open discussion and chat will join us in helping to flesh out intrinsic evaluation criteria and their dimensions.     (1J6)

More details about this Ontology Summit is available at: OntologySummit2013 (homepage for this summit)     (1J7)

Briefings     (1J8)

  • Ms. MariaPovedaVillalon (Universidad Polit��cnica de Madrid), Dr. MariCarmenSuarezFigueroa (Universidad Polit��cnica de Madrid) and Dr. AsuncionGomezPerez (Universidad Polit��cnica de Madrid) - "A Pitfall Catalogue and OOPS!: An Approach to Ontology Validation" ... [ slides ]     (1J8A)
    • Abstract: ... One of the advantages of using methodologies for building ontologies is to improve the quality of the resultant ontology. However, due to the difficulties involved in ontology modelling, such quality is not totally guaranteed. These difficulties are related to the inclusion of anomalies or worst practices. Our approach contributes to the ontology validation activity by (1) providing a catalogue of common worst practices, which we call pitfalls, and (2) proposing a web-based tool, called "OOPS!". This approach will help developers in two following ways: (1) to avoid the appearance of pitfalls in ontologies, and (2) to improve ontology quality by automatically detecting potential errors.     (1J8A1)
  • Dr. SamirTartir (Philadelphia University, Amman, Jordan), Dr. IsmailcemBudakArpinar (University of Georgia), Dr. AmitSheth (Wright State University) - "Ontology Evaluation and Ranking using [[ConferenceCall_2013_01_31|OntoQA]]" ... [ slides ]     (1J8B)
    • Abstract: ... Ontologies form the cornerstone of the Semantic Web and are intended to help researchers to analyze and share knowledge, and as more ontologies are being introduced, it is difficult for users to find good ontologies related to their work. Therefore, tools for evaluating and ranking the ontologies are needed. In our talk, we present [[ConferenceCall_2013_01_31|OntoQA]], a framework that evaluates ontologies related to a certain set of terms and then ranks them according a set of metrics that captures different aspects of ontologies. Since there are no global criteria defining how a good ontology should be, [[ConferenceCall_2013_01_31|OntoQA]] allows users to tune the ranking towards certain features of ontologies to suit the need of their applications.     (1J8B1)
  • Dr. JesualdoTomasFernandezBreis (Universidad de Murcia), Dr. AstridDuqueRamos (Universidad de Murcia), Dr. RobertStevens (University of Manchester), Dr. NathalieAussenacGilles (Institute de Recherche en Informatique de Toulouse (IRIT), Universit�� Paul Sabatier) - "The OQuaRE Framework for Ontology Evaluation" ... [ slides ]     (1J8C)
    • Abstract: Many Software Engineering methods have been adapted and applied to ontology engineering in the last decades. This has not been the case so far of ontology evaluation despite the availability of international software quality standards. In contrast, the increasing importance of ontologies has resulted in the development of a large number of ontologies, but there is a lack of mechanisms for guiding users in making informed decisions on which ontology to use under given circumstances make hard to ontology users and tool developers selecting ontologies to be used and reused. We propose a framework named OQuaRE for evaluating the quality of ontologies based on the SQuaRE standard for software quality evaluation. The main objective of OQuaRE is to provide an objective, standardized framework for ontology quality evaluation in order to identify the strengths and weaknesses of ontologies. OQuaRE aims at helping users in making informed decisions and ontology experts in evaluating the quality of their ontologies with the support of automatically calculated metrics. We will not only describe the current version of the framework but also the results and evaluation of its application by external experts.     (1J8C1)

Agenda     (1K)

OntologySummit2013 - Panel Session-03     (1K1)

  • Session Format: this is a virtual session conducted over an augmented conference call     (1K2)

Proceedings     (1L)

Please refer to the above     (1L1)

IM Chat Transcript captured during the session    (1L2)

see raw transcript here.     (1L2A)

(for better clarity, the version below is a re-organized and lightly edited chat-transcript.)     (1L2B)

Participants are welcome to make light edits to their own contributions as they see fit.     (1L2C)

-- begin in-session chat-transcript --     (1L2D)

[08:23] Peter P. Yim: Welcome to the     (1L2E)

Ontology Summit 2013: Virtual Panel Session-03 - Thu 2013-01-31     (1L2F)

Summit Theme: Ontology Evaluation Across the Ontology Lifecycle     (1L2G)

  • Summit Track Title: Track-A: Intrinsic Aspects of Ontology Evaluation     (1L2H)

Session Topic: Intrinsic Aspects of Ontology Evaluation: Practice and Theory     (1L2I)

Panelists / Briefings:     (1L2K)

  • "A Pitfall Catalogue and OOPS!: An Approach to Ontology Validation"     (1L2L)

- Ms. MariaPovedaVillalon (Universidad Politecnica de Madrid)     (1L2M)

- Dr. MariCarmenSuarezFigueroa (Universidad Politecnica de Madrid)     (1L2N)

- Dr. AsuncionGomezPerez (Universidad Politecnica de Madrid)     (1L2O)

- Dr. Samir Tartir (Philadelphia University, Amman, Jordan)     (1L2Q)

- Dr. IsmailcemBudakArpinar (University of Georgia)     (1L2R)

- Dr. Amit Sheth (Wright State University)     (1L2S)

- Dr. JesualdoTomasFernandezBreis (Universidad de Murcia)     (1L2U)

- Ms. AstridDuqueRamos (Universidad de Murcia)     (1L2V)

- Dr. Robert Stevens (University of Manchester)     (1L2W)

- Dr. NathalieAussenacGilles (Institute de Recherche en Informatique de Toulouse (IRIT), Universite Paul Sabatier)     (1L2X)

Logistics:     (1L2Y)

  • (if you haven't already done so) please click on "settings" (top center) and morph from "anonymous" to your RealName (in WikiWord format)     (1L2AA)
    • for Linux Skype users: please note that the dial-pad is only available on v4.1 (or later or the earlier Skype versions 2.x,)     (1L2AE1)

if the dialpad button is not shown in the call window you need to press the "d" hotkey to enable it.     (1L2AF)

Proceedings:     (1L2AG)

[09:06] anonymous1 morphed into MariaPovedaVillalon     (1L2AH)

[09:14] anonymous1 morphed into Megan Katsumi     (1L2AI)

[09:16] anonymous1 morphed into Carmen Chui     (1L2AJ)

[09:19] anonymous morphed into Jim Disbrow     (1L2AK)

[09:20] anonymous morphed into JesualdoTomasFernandezBreis     (1L2AL)

[09:24] anonymous morphed into Mohammad Aqtash     (1L2AN)

[09:25] anonymous1 morphed into David Makovoz     (1L2AO)

[09:26] MeganKatsumi1 morphed into Michael Grüninger     (1L2AP)

[09:28] Leo Obrst: Hi, Jesualdo, Maria, Mohammad and all!     (1L2AQ)

[09:28] anonymous morphed into Samir Tartir     (1L2AR)

[09:28] Leo Obrst: Hi, Samir!     (1L2AT)

[09:30] Mohammad Aqtash: Hi LeoObrst!     (1L2AV)

[09:30] astridduque morphed into AstridDuqueRamos     (1L2AW)

[09:31] anonymous morphed into Mike Denny     (1L2AX)

[09:31] anonymous morphed into Doug Foxvog     (1L2AY)

[09:31] anonymous1 morphed into Torsten Hahmann     (1L2AZ)

[09:32] anonymous1 morphed into Clare Paul     (1L2AAA)

[09:32] anonymous morphed into Joseph Tennis     (1L2AAB)

[09:32] anonymous morphed into IsmailcemBudakArpinar     (1L2AAC)

[09:34] anonymous morphed into James Odell     (1L2AAD)

[09:35] Ram D. Sriram: I do have a problem viewing slides on a Mac (using VNC). It seems to work on a     (1L2AAE)

[09:50] Steve Ray: @Ram: My theory remains that this problem relates to the latest version of Java,     (1L2AAG)

which somehow keeps the VNC from working properly.     (1L2AAH)

[09:52] Todd Schneider: Steve, Ram, I checked and the browser has the Java plug-in disabled.     (1L2AAI)

[09:36] anonymous morphed into JoaoPauloAlmeida     (1L2AAJ)

[09:38] Peter P. Yim: == Steve Ray opens the session ... see: [0-Chair] slides     (1L2AAK)

[09:42] Peter P. Yim: Hi Duane, welcome to the session     (1L2AAT)

[09:42] Duane Nickull: Please to be here.     (1L2AAU)

[09:45] Peter P. Yim: == MariaPovedaVillalon presenting ... see: [1-Poveda] slides     (1L2AAV)

[09:45] anonymous1 morphed into Trish Whetzel     (1L2AAW)

[09:52] Steve Ray: We are now on slide 7     (1L2AAX)

[09:54] Bob Schloss: As I listen to the approach Maria has started doing, it reminds me of some work     (1L2AAY)

I did with my colleague Achille Fokoue-Nkoutche in the very early days of the XML Schema language.     (1L2AAZ)

We released a tool called IBM XML Schema Quality Checker through the IBM alphaWorks program, it was     (1L2AAAA)

very widely used because this kind of document / message / vocabulary modeling was unfamiliar to a     (1L2AAAB)

lot of people, and top quality tools for construction of these XML Schemas (such as from companies     (1L2AAAC)

such as Altova, Progress Software, IBM Rational) were still not widely available.     (1L2AAAD)

[09:56] Bob Schloss: Equally importantly, guidelines, best practices and patterns for XML Schema     (1L2AAAE)

development, which were later compiled by a number of people, were not yet documented... so our tool     (1L2AAAF)

warned people when they were using a construct that was strictly legal but might limit evolvability     (1L2AAAG)

of their schema or reuse by others.     (1L2AAAH)

[09:56] Bob Schloss: [I have to leave for another meeting... Will review all slides and the recording     (1L2AAAI)

of this chat later. Thanks all]     (1L2AAAJ)

[09:57] MariCarmenSuarezFigueroa: @BobSchloss, interesting work.     (1L2AAAK)

[09:56] Steve Ray: @Maria: Question for later: To recognize your Pitfall #5, it would seem that you     (1L2AAAL)

would need to know the intent of a term such as isSoldIn and isBoughtIn. How does your automated     (1L2AAAM)

tool do this?     (1L2AAAN)

[09:57] MariCarmenSuarezFigueroa: @SteveRay: at this moment our tool OOPS! detect in an automated     (1L2AAAO)

way a subset of the pitfalls in the catalogue     (1L2AAAP)

[09:58] MariCarmenSuarezFigueroa: @SteveRay for those detected by OOPS! there are different     (1L2AAAQ)

approaches as Maria is explaining     (1L2AAAR)

[09:59] MariCarmenSuarezFigueroa: (is going to explain in next slides)     (1L2AAAS)

[09:59] Doug Foxvog: @Steve. The inverse relationship between isSoldIn & isBoughtIn can be determined     (1L2AAAT)

to be inconsistent with having the argument types reversed. By noting that the argument types match     (1L2AAAU)

(arg1<=>arg1 & arg2<=>arg2) one can suggest that the error is in calling it an inverse relationship     (1L2AAAV)

instead of being in mis-assignment of argument types.     (1L2AAAW)

[10:01] Steve Ray: @MariCarmenSuarezFigueroa, Doug Foxvog: Ah yes, I see now - Domain and Range     (1L2AAAX)

[10:04] Doug Foxvog: Slide 14 suggests possible symmetric or transitive properties if there are equal     (1L2AAAZ)

domain & range. Such suggestions should not be made if the relations are already defined as     (1L2AAAAA)

asymmetric or functional.     (1L2AAAAB)

[10:00] anonymous1 morphed into Bruce Bray     (1L2AAAAE)

[09:59] Samir Tartir: Hello Dr. @Arpinar, @MohammadAqtash... Nice to see you here.     (1L2AAAAF)

[10:06] Samir Tartir: Some definitions I will be using in the my presentation can be found in this paper:     (1L2AAAAG)

[10:06] Terry Longstreth: Maria- have you considered running OOPS! against public domain ontologies,     (1L2AAAAI)

and publishing the resulting evaluations?     (1L2AAAAJ)

[10:07] MariCarmenSuarezFigueroa: @TerryLongstreth: thanks for the suggestion. Yes, we have already     (1L2AAAAK)

made an experiment in this sense; and our idea is to evaluate more available ontologies in order to     (1L2AAAAL)

see the current state of public ontologies.     (1L2AAAAM)

ontologies might be interesting     (1L2AAAAO)

[10:10] MariCarmenSuarezFigueroa: @Jesualdo, thanks! We have already evaluate a subset of OBO and     (1L2AAAAP)

BioPortal ontologies, but our plan is to made the evaluation for more     (1L2AAAAQ)

[10:10] Todd Schneider: Can the OOPS! source code be obtained?     (1L2AAAAR)

[10:11] MariCarmenSuarezFigueroa: @ToddSchneider: at this moment the source code is not available.     (1L2AAAAS)

[10:12] Todd Schneider: Maria, Too bad. Can your team consider working with OOR initiative?     (1L2AAAAT)

[10:13] MariCarmenSuarezFigueroa: @ToddSchenider: we are analysing how to proceed with our code.     (1L2AAAAU)

Maybe we can consider your suggestion     (1L2AAAAV)

[10:13] MariaPovedaVillalon: we will provide web services soon Todd     (1L2AAAAW)

[10:14] Todd Schneider: Maria's, For performance reasons having a more 'local' instance of OOPS!     (1L2AAAAX)

would be optimal.     (1L2AAAAY)

[10:15] MariCarmenSuarezFigueroa: @Todd, yes you are right. As mentioned, we are now analysing     (1L2AAAAZ)

different options for our code :-D     (1L2AAAAAA)

[10:15] MariaPovedaVillalon: @ToddSchneider you are right, as Mari Carmen said we need to think     (1L2AAAAAB)

about to to proceed with the code     (1L2AAAAAC)

[10:15] MariaPovedaVillalon: @Todd I totally agree with the idea of sharing the code     (1L2AAAAAD)

[10:16] MariaPovedaVillalon: @Todd as first step we are creating the web services so that everybody     (1L2AAAAAE)

can include the features in their code, but sure, we also need to share the code     (1L2AAAAAF)

[10:12] Leo Obrst: @Maria: 3 questions: 1) These are all OWL/RDF ontologies; are you considering     (1L2AAAAAG)

other languages, e.g., Common Logic? 2) What if the ontology you are evaluating contains imports or     (1L2AAAAAH)

references to other ontologies, do you track down these and evaluate them? 3) What is "P9. Missing     (1L2AAAAAI)

basic information"?     (1L2AAAAAJ)

[10:13] Amanda Vizedom: @Maria: Very nice. I have seen several large projects spend extensive effort     (1L2AAAAAK)

in developing their own, in-house versions of something like this approach. This speaks to the     (1L2AAAAAL)

relevance of the approach to real work-flows. However, due to lack of resources and/or expertise,     (1L2AAAAAM)

those in-house versions usually end up not as good as OOPS! appears to be. They also often generate     (1L2AAAAAN)

repeating cycles of management or collaborator doubt, as their developers cannot point to     (1L2AAAAAO)

independent grounding and acceptance. OOPS! seems to me like a valuable contribution to operational     (1L2AAAAAP)

use of ontologies.     (1L2AAAAAQ)

[10:14] MariCarmenSuarezFigueroa: @Amanda, thank you for your comment.     (1L2AAAAAR)

[10:12] Trish Whetzel: Of the ontologies in BioPortal, do you find errors correlated to any of the     (1L2AAAAAS)

groups, such as OBO Foundry or UMLS, and/or ontology format .. which is also somewhat an indicator     (1L2AAAAAT)

of ontology design patterns?     (1L2AAAAAU)

[10:15] JesualdoTomasFernandezBreis: @TrishWhetzel: in another project we have done a systematic     (1L2AAAAAV)

analysis of the labels of bioportal ontologies and we found some problems with formats and     (1L2AAAAAW)

availability of some files     (1L2AAAAAX)

[10:19] Trish Whetzel: @Jesualdo Thanks, I'm interested in these issues     (1L2AAAAAY)

[10:25] JesualdoTomasFernandezBreis: @Trish: I will send you an email with the details     (1L2AAAAAZ)

[10:16] Megan Katsumi: @Maria: Sorry if you mentioned this already, but how do you decide if a     (1L2AAAAAAA)

particular characteristic qualifies as a pitfall?     (1L2AAAAAAB)

[10:17] MariaPovedaVillalon: @Megan we have observed the pitfalls we list as errors in ontologies     (1L2AAAAAAC)

when we manually analyzed them, however, the same "characteristic" might not be an error in other     (1L2AAAAAAD)

ontology, so at the end the user decide. Sometimes the error does not need to be checked but that is     (1L2AAAAAAE)

not always the case.     (1L2AAAAAAF)

[10:15] Amanda Vizedom: @Maria: A few questions: (1) Is it correct that OOPS! works specifically on     (1L2AAAAAAG)

OWL? Is it further narrowed to specific dialects (such as DL)? Does your group have any plans or     (1L2AAAAAAH)

interests in extending to other languages (for example, Common Logic?)     (1L2AAAAAAI)

[10:19] Doug Foxvog: @Amanda, re your first question. OOPS! only accepted OWL RDF/XML when I looked     (1L2AAAAAAJ)

at it in December.     (1L2AAAAAAK)

[10:16] Amanda Vizedom: @Maria: (2) Can OOPS! detect errors (or warnings/suggestions) based on     (1L2AAAAAAL)

general logical entailments? Does OOPS! make use of, or contain, a general OWL reasoner?     (1L2AAAAAAM)

[10:19] MariaPovedaVillalon: @Amanda we think about leaving that decision to the user     (1L2AAAAAAN)

[10:20] MariaPovedaVillalon: @Amanda reasoners do already exist and we don't want to rethink the     (1L2AAAAAAO)

wheel, however we can benefit from them to detec more pitfall but the computational price will be     (1L2AAAAAAP)

[10:34] MariaPovedaVillalon: @Amanda in summary, at any case our idea is that we should leave the     (1L2AAAAAAR)

decision of using reasoners to the user (maybe a checkbox in OOPS!) or point to existing reasoners     (1L2AAAAAAS)

giving the user some guidelines about which things to check and common errors     (1L2AAAAAAT)

[10:22] Amanda Vizedom: @Maria (3) Have you run into any difficulties concerning what seem to be     (1L2AAAAAAU)

pitfalls and the behavior of OWL reasoners? An example that comes to mind is the fact if a property     (1L2AAAAAAV)

is applied used to relate two things, one of which is not stated to satisfy the range requirements,     (1L2AAAAAAW)

for example, it will be inferred that the thing *does* meet the range requirements. But in some     (1L2AAAAAAX)

(many?) cases, the omission is actually indicative of an error. Would OOPS! treat as a pitfall or     (1L2AAAAAAY)

warning the fact that the thing in the range is not stated to meet the range requirements?     (1L2AAAAAAZ)

[10:25] MariaPovedaVillalon: @AmandaVizedom excuse me, if I'm not wrong you talk about instances,     (1L2AAAAAAAA)

right now OOPS! only looks at the schema level     (1L2AAAAAAAB)

[10:26] MariaPovedaVillalon: @Amanda have I answered your question? I do not think I understood it     (1L2AAAAAAAC)

properly, maybe...     (1L2AAAAAAAD)

[10:32] Amanda Vizedom: @Maria: That's fine. I think that last question may be confusing if we are     (1L2AAAAAAAE)

accustomed to working at different levels of language expressiveness. If you are working in DL it     (1L2AAAAAAAF)

may be a instance-level issue; less so if working expressiveness beyond DL. Thanks!     (1L2AAAAAAAG)

hackathon exercise, it will be great if you team can join us in that effort (we have yet to refine     (1L2AAAAAAAI)

on what exactly would that "hackathon" entail though, so participant input are solicited)     (1L2AAAAAAAJ)

[10:17] MariCarmenSuarezFigueroa: @Peter, yes, count with us     (1L2AAAAAAAK)

[10:19] Peter P. Yim: Thanks, Maria.     (1L2AAAAAAAN)

[10:19] Ken Baclawski: @Maria: I built a system very similar to yours back in 2004. I called the     (1L2AAAAAAAO)

problems with an ontology symptoms rather than pitfalls, but it is the same idea. It used a     (1L2AAAAAAAP)

rule-based approach which was extendible. One interesting feature was that the symptoms that were     (1L2AAAAAAAQ)

generated were in a Symptom ontology and we performed reasoning on the symptoms that were generated     (1L2AAAAAAAR)

to find relationships among symptoms since we found that a single error can generate many symptoms     (1L2AAAAAAAS)

(which, by the way, is the reason for using the word "symptom"). Here is a reference to the paper:     (1L2AAAAAAAT)

K. Baclawski, C. Matheus, M. Kokar and J. Letkowski. Toward a Symptom Ontology for Semantic Web     (1L2AAAAAAAU)

Applications. In ISWC'04, pages 650-667. Lecture Notes in Computer Science 3298:650-667.     (1L2AAAAAAAV)

Springer-Verlag. (2004)     (1L2AAAAAAAW)

[10:20] MariCarmenSuarezFigueroa: @KenBaclawski, thanks for the reference.     (1L2AAAAAAAX)

[10:21] MariaPovedaVillalon: @KenBaclawski, thank you very much for the reference, sounds really     (1L2AAAAAAAY)

interesting and familiar what you said about one error many symptoms...     (1L2AAAAAAAZ)

[10:13] Doug Foxvog: (re. Maria's slide#14) One can suggest transitivity if the domain is a subclass     (1L2AAAAAAAAA)

of the range. They need not be equal.     (1L2AAAAAAAAB)

[10:28] MariaPovedaVillalon: @DougFoxvog we check what you said about suggestion in slide 14     (1L2AAAAAAAAC)

[10:29] MariaPovedaVillalon: @DougFoxvog we fixed the errors it had in December, OOPS! was supposed     (1L2AAAAAAAAD)

to check it and if everything is fine it should work by now     (1L2AAAAAAAAE)

[10:30] JesualdoTomasFernandezBreis: I think tools like OOPS! are fundamental for ontology     (1L2AAAAAAAAF)

engineers, thanks for your work!     (1L2AAAAAAAAG)

[10:31] MariaPovedaVillalon: Thank you @Jesualdo     (1L2AAAAAAAAH)

[10:31] MariCarmenSuarezFigueroa: @Jesualdo, thank you very much for your comment!     (1L2AAAAAAAAI)

[10:12] Peter P. Yim: == Samir Tartir presenting ... see: [2-Tartir] slides     (1L2AAAAAAAAJ)

[10:14] anonymous1 morphed into Dennis Wisnosky     (1L2AAAAAAAAK)

[10:14] anonymous1 morphed into YuvaTarunVarmaDatla     (1L2AAAAAAAAL)

[10:17] anonymous2 morphed into NathalieAussenacGilles     (1L2AAAAAAAAM)

[10:20] Joseph Tennis: can someone extract all the citations being shared and put them in one spot?     (1L2AAAAAAAAN)

[10:21] Steve Ray: @Joseph: There is one spot we are collecting references. Amanda can say more about     (1L2AAAAAAAAO)

that (and did in an earlier session).     (1L2AAAAAAAAP)

[10:22] Joseph Tennis: sweet! thanks!     (1L2AAAAAAAAQ)

[10:23] Steve Ray: @Joseph: I should add that it is our shared responsibility to populate it.     (1L2AAAAAAAAR)

[10:28] Todd Schneider: Samir, Would you provide the definitions for each of the variables in your     (1L2AAAAAAAAS)

metrics in the chat?     (1L2AAAAAAAAT)

{{{ [10:28] Amanda Vizedom: @Steve and @Joseph I will post a note to the summit list under the {biblio} subject soon. I've been away for a bit and have begun getting the Zotero library caught up. Meanwhile, the library itself is at }}}     (1L2AAAAAAAAU)

[10:33] Doug Foxvog: @Samir: many of your metrics are metrics for knowledge bases. It might be useful     (1L2AAAAAAAAV)

to distinguish the two classes of metrics, and have different scores for ontologies (which define     (1L2AAAAAAAAW)

types and relations) and knowledge bases (which define individuals and provide information about the     (1L2AAAAAAAAX)

individuals by asserting relations that apply to them).     (1L2AAAAAAAAY)

[10:36] Doug Foxvog: @Samir: I see that you do distinguish multiple ranking types in slides 16 & 17.     (1L2AAAAAAAAZ)

But defining different sets of rankings for different types of KBs or ontologies might be useful.     (1L2AAAAAAAAAA)

[10:34] Leo Obrst: @all: I think these evaluation tools and metrics would be very useful in the Open     (1L2AAAAAAAAAB)

Ontology Repository (OOR). Perhaps the speakers would like to join our OOR group and provide     (1L2AAAAAAAAAC)

potential services?     (1L2AAAAAAAAAD)

[10:36] MariCarmenSuarezFigueroa: @Leo, yes, we can consider to join the OOR group and see how we     (1L2AAAAAAAAAE)

can contribute to it     (1L2AAAAAAAAAF)

[10:40] MariaPovedaVillalon: @Leo where can we find information to join and contribute to OOR?     (1L2AAAAAAAAAG)

[10:39] Leo Obrst: @Samir: can you provide definitions for your variables?     (1L2AAAAAAAAAJ)

[10:43] Samir Tartir: @ToddSchneider & @LeoObrst: There is a large number of variables used. E.g. A     (1L2AAAAAAAAAK)

set of classes, C., A set of relationships, P. An inheritance function, Hc. A set of class     (1L2AAAAAAAAAL)

attributes, Att.     (1L2AAAAAAAAAM)

[10:44] Samir Tartir: @ToddSchneider & @LeoObrst: The definitions are all included in the paper I     (1L2AAAAAAAAAN)

referenced right before I started presenting.     (1L2AAAAAAAAAO)

[10:45] Samir Tartir: I will be more than happy to send you the paper if you'd like.     (1L2AAAAAAAAAP)

[10:45] Todd Schneider: Samir, I missed that reference.     (1L2AAAAAAAAAQ)

[10:46] Samir Tartir: Todd, here it is again:     (1L2AAAAAAAAAR)

[10:46] Todd Schneider: Samir, Great. Thank you.     (1L2AAAAAAAAAT)

[10:47] Torsten Hahmann: @Samir: before weighting, are the various metrics standardized (to values     (1L2AAAAAAAAAU)

between 0 and 1, for example)? Otherwise two metric with equal weight may still influence the total     (1L2AAAAAAAAAV)

score differently     (1L2AAAAAAAAAW)

[10:47] Samir Tartir: @Torsten: Yes.     (1L2AAAAAAAAAX)

[10:50] Samir Tartir: @DougFoxvog: Not sure what you mean here. Maybe discuss this after the current     (1L2AAAAAAAAAY)

speaker finishes.     (1L2AAAAAAAAAZ)

[10:51] Torsten Hahmann: @Samir: I take your answer as they are standardized.     (1L2AAAAAAAAAAA)

[10:53] Samir Tartir: @Torsten. Sorry for not being clear. Yes they are standardized.     (1L2AAAAAAAAAAB)

[10:53] Torsten Hahmann: @Samir: thanks.     (1L2AAAAAAAAAAC)

[10:38] Peter P. Yim: == AstridDuqueRamos presenting ... see: [3-DuqueRamos] slides     (1L2AAAAAAAAAAD)

[10:53] Joseph Tennis: This was great! Wish I could stay longer. I look forward to using some of     (1L2AAAAAAAAAAE)

these metrics for my work. One question I have is what do these metrics look like on different     (1L2AAAAAAAAAAF)

versions of the same ontology? Do they change dramatically? Or do they not change much at all? It     (1L2AAAAAAAAAAG)

might be something we can look at here. In case you're interested in my work on versioning, you can     (1L2AAAAAAAAAAH)

[10:52] Amanda Vizedom: @Astrid (actually, this applies to @Samir's presentation as well): your     (1L2AAAAAAAAAAL)

approach measures some numeric/ topographic qualities of an ontology, such as depth of inheritance,     (1L2AAAAAAAAAAM)

breadth of relationships, number of ancestors. I have seen many cases in which ontology teams, or     (1L2AAAAAAAAAAN)

projects of which they are a part, are required to report such metrics upward to management, and are     (1L2AAAAAAAAAAO)

held in some sense accountable for them, but it is very hard to see whether they are actually     (1L2AAAAAAAAAAP)

indicative of quality (and if so how). It may be that they are meaningful given some interpretation,     (1L2AAAAAAAAAAQ)

given some requirements in place, or under some other conditions. What do they mean, in your view?     (1L2AAAAAAAAAAR)

[10:54] Torsten Hahmann: +1 to @Amanda's comment: that should be one of the goals of this track (in     (1L2AAAAAAAAAAS)

[10:54] JesualdoTomasFernandezBreis: @Amanda: one of the next slides has some comments I think     (1L2AAAAAAAAAAU)

related to yours     (1L2AAAAAAAAAAV)

[10:54] Steve Ray: @Amanda & @Astrid: Amanda, I think you are precisely raising the question about     (1L2AAAAAAAAAAW)

intrinsic vs. extrinsic evaluation. Management often cares about the latter more than the former,     (1L2AAAAAAAAAAX)

and sometimes at the expense of attention to the former.     (1L2AAAAAAAAAAY)

[10:57] Samir Tartir: @Steve, @Amanda & @Astrid: It's relevant to each user or scenario. I think     (1L2AAAAAAAAAAZ)

@Steve 's comment is right on target.     (1L2AAAAAAAAAAAA)

[10:58] Leo Obrst: @Steve, Amanda, and all: Yes, because the current application is local and of     (1L2AAAAAAAAAAAB)

highest priority to management: extrinsic typically is more valued.     (1L2AAAAAAAAAAAC)

[10:59] Amanda Vizedom: @SteveRay: Although I'm very interested in the intrinsic/extrinsic question,     (1L2AAAAAAAAAAAD)

I see *this* question a bit differently. Staying within the intrinsic evaluation topic, there is an     (1L2AAAAAAAAAAAE)

independent question about which, of the many intrinsic characteristics an ontology may be said to     (1L2AAAAAAAAAAAF)

have, are actually measurements of quality. That a quality exists and can be measured, or even that     (1L2AAAAAAAAAAAG)

it has some intuitive or aesthetic appeal, is not enough to establish that it is an aspect of     (1L2AAAAAAAAAAAH)

ontology *quality*. The question is: Are these? And if so, why?     (1L2AAAAAAAAAAAI)

[11:02] Doug Foxvog: +1 @Amanda. many of the mentioned characteristics are *features* of the     (1L2AAAAAAAAAAAJ)

ontologies. Whether they are measures of *quality* may in some instances be context dependent.     (1L2AAAAAAAAAAAK)

[11:03] Torsten Hahmann: I agree with @Doug: independent of whether intrinsic metrics are valued by     (1L2AAAAAAAAAAAL)

management, we have to figure whether they are correlated to the intended qualities     (1L2AAAAAAAAAAAM)

[11:03] Leo Obrst: @Amanda: perhaps more to your point, an approach such as OntoClean that uses     (1L2AAAAAAAAAAAN)

ontological analysis more clearly may have higher real value/quality, but is not necessarily     (1L2AAAAAAAAAAAO)

immediately understandable to management, though application value can be demonstrated.     (1L2AAAAAAAAAAAP)

[11:00] Steve Ray: We could discuss (at a later time) whether ontology development environments could     (1L2AAAAAAAAAAAQ)

hard-wire evaluation during the ontology development process.     (1L2AAAAAAAAAAAR)

[11:00] Steve Ray: @Amanda: Need to think about your question in a few minutes.     (1L2AAAAAAAAAAAS)

[11:03] Amanda Vizedom: @Steve, et al., it may also be that *extrinsically* relevant characteristics     (1L2AAAAAAAAAAAT)

are so consistently relevant in some domain / context of application that folks trained in that     (1L2AAAAAAAAAAAU)

context believe them to be *intrinsic*. I do not mean to pre-judge the question for the     (1L2AAAAAAAAAAAV)

characteristics I mentioned. Rather that I would be interested in the presenters' thoughts on those,     (1L2AAAAAAAAAAAW)

and whether they can offer particular reasons for considering those intrinsic measurements to be     (1L2AAAAAAAAAAAX)

measures of *quality*.     (1L2AAAAAAAAAAAY)

[11:01] Matthew West: An even better approach is to have a develop method that avoids the quality     (1L2AAAAAAAAAAAZ)

[11:01] Peter P. Yim: == Q&A and Open Discussion ...     (1L2AAAAAAAAAAAAB)

[11:01] Peter P. Yim: question for all panelists - how do some of the more rigorously developed     (1L2AAAAAAAAAAAAC)

ontologies (like BFO, DOLCE, PSL, SUMO, CYC, etc.) fare, when put through your     (1L2AAAAAAAAAAAAD)

evaluation system/tool; anyone tried? observations & insights gained?     (1L2AAAAAAAAAAAAE)

[11:15] MariCarmenSuarezFigueroa: We have already evaluate DOLCE with OOPS! (among other     (1L2AAAAAAAAAAAAF)

established ontologies)     (1L2AAAAAAAAAAAAG)

[11:17] Terry Longstreth: @MariCarmenSuarezFigueroa - is there a URL for the results of the DOLCE     (1L2AAAAAAAAAAAAH)

[11:19] MariCarmenSuarezFigueroa: @terry, results are not available yet     (1L2AAAAAAAAAAAAJ)

[11:15] JesualdoTomasFernandezBreis: We are in the process of evaluating all the BioPortal     (1L2AAAAAAAAAAAAK)

ontologies with OQuaRE, but we do not have the results yet     (1L2AAAAAAAAAAAAL)

[11:21] Amanda Vizedom: Following up on Peter's question: For all panelists: What are the     (1L2AAAAAAAAAAAAM)

expressivity constraints or expectations of these tools? Are they limited to DL ontologies?     (1L2AAAAAAAAAAAAN)

OWL-Full? Has anyone applied their techniques to ontologies represented in FOL or higher languages?     (1L2AAAAAAAAAAAAO)

[11:22] MariCarmenSuarezFigueroa: (re. Peter's follow-up question on whether they had tried how the     (1L2AAAAAAAAAAAAP)

tools scale with larger ontologies like SUMO or CYC) We did not try with Cyc yet, for     (1L2AAAAAAAAAAAAQ)

[11:03] anonymous1 morphed into Hashem Shmaisani     (1L2AAAAAAAAAAAAS)

[11:03] Duane Nickull: (ref. the reverb/echo when Doug Foxvog tried to patch in) Nice audio effects     (1L2AAAAAAAAAAAAT)

[11:03] Duane Nickull: Very Dr. Who - ish     (1L2AAAAAAAAAAAAV)

[11:04] Duane Nickull: Exterminate, exterminate, exterminate.....     (1L2AAAAAAAAAAAAW)

[11:04] Amanda Vizedom: Audio sounds like we have fallen down the rabbit hole!     (1L2AAAAAAAAAAAAY)

[11:04] Bobbin Teegarden: @DougFoxvog: 'context dependent'... or, in the eye of the beholder?     (1L2AAAAAAAAAAAAZ)

[11:05] Matthew West: Some very interesting presentations, but I'm afraid I have to go now.     (1L2AAAAAAAAAAAAAA)

[11:05] anonymous morphed into AsuncionGomezPerez     (1L2AAAAAAAAAAAAAB)

[11:08] Jim Disbrow: Steve's first point of a measurement being "well-designed" is: "Proper use of     (1L2AAAAAAAAAAAAAC)

various relations found within an ontology". This has been an issue that has been sorely     (1L2AAAAAAAAAAAAAD)

underrepresented, but may now be breaking through - as demonstrated by the presentations. Insertion     (1L2AAAAAAAAAAAAAE)

of reflexivity in relationships, however, was not mentioned as a criteria. Is there any progress in     (1L2AAAAAAAAAAAAAF)

this ontological concepts implementations? (ref. below [11:28])     (1L2AAAAAAAAAAAAAG)

[11:11] Leo Obrst: @Doug: I think Samir's analysis of both ontology and KB are very useful for     (1L2AAAAAAAAAAAAAH)

ontologists, even though KBs will potentially be different across applications, companies, etc.     (1L2AAAAAAAAAAAAAI)

[11:12] Doug Foxvog: @Leo: I agree. But I'm suggesting that these distinctions should be identified.     (1L2AAAAAAAAAAAAAJ)

[11:15] Terry Longstreth: @Leo - I'm not convinced that there's an objective procedure for separating     (1L2AAAAAAAAAAAAAK)

the two. Linnean classification requires a 'type instance' to fully describe a species type. Would     (1L2AAAAAAAAAAAAAL)

that be in the Ontology, or in the KB?     (1L2AAAAAAAAAAAAAM)

[11:15] Samir Tartir: Thanks Leo. Doug: I agree that it might be useful.     (1L2AAAAAAAAAAAAAN)

[11:18] Samir Tartir: (re. Amanda's positive verbal remark about the relationship diversity metric)     (1L2AAAAAAAAAAAAAO)

[11:19] Leo Obrst: @Terry: to your point, that is an issue. E.g., usually classes are considered     (1L2AAAAAAAAAAAAAQ)

universals, and instances particulars, but some ontologies (and metaphysics) don't makes those     (1L2AAAAAAAAAAAAAR)

distinctions, e.g., identifying all "ontology" notions as particulars (e.g., tropes, etc.)     (1L2AAAAAAAAAAAAAS)

[11:20] Doug Foxvog: @Terry: OWL DL does not allow meta-classes, so that the instances of species,     (1L2AAAAAAAAAAAAAT)

genus, bio-kingdom, etc. are classes, themselves. A system that merely defines these, their     (1L2AAAAAAAAAAAAAU)

hierarchy, and relations that may apply to them would be, imho, an ontology. However, if data is     (1L2AAAAAAAAAAAAAV)

provided about these taxons (geological range, endangerment, diet, etc.), then it would be a KB,     (1L2AAAAAAAAAAAAAW)

even though what is being described are themselves classes.     (1L2AAAAAAAAAAAAAX)

[11:22] Terry Longstreth: Then I think evaluation has to include the KB if it's required for full     (1L2AAAAAAAAAAAAAY)

interpretation of the ontology     (1L2AAAAAAAAAAAAAZ)

[11:22] Leo Obrst: @Terry: I agree. Both need to be evaluated.     (1L2AAAAAAAAAAAAAAA)

[11:28] Jim Disbrow: @Steve: In your first slide, your first point of a measurement for being     (1L2AAAAAAAAAAAAAAB)

well-designed is: "Proper use of various relations found within an ontology". This has been an     (1L2AAAAAAAAAAAAAAC)

issue that has been sorely underrepresented, but may now be breaking through - as demonstrated by     (1L2AAAAAAAAAAAAAAD)

the presentations. Insertion of reflexivity in relationships, however, was not mentioned as a     (1L2AAAAAAAAAAAAAAE)

criteria. Similarly, there was no mention of an active "not" verb (not just the English negation     (1L2AAAAAAAAAAAAAAF)

term), concatenated into the middle term of the OWL "triple". A question for the presenters: Is     (1L2AAAAAAAAAAAAAAG)

there any progress in implementing these ontological concepts?     (1L2AAAAAAAAAAAAAAH)

[11:31] Steve Ray: Anybody want to comment on Jim's question about addressing reflexivity?     (1L2AAAAAAAAAAAAAAI)

[11:34] Jim Disbrow: I would offer that an ontology without proper use of relationships cannot claim     (1L2AAAAAAAAAAAAAAJ)

to claim "quality".     (1L2AAAAAAAAAAAAAAK)

[11:22] Leo Obrst: @Amanda: (re. Amanda's verbal remark questioning some of the metrics and how they     (1L2AAAAAAAAAAAAAAL)

relate to "quality") Is your issue about the definition of "quality"? I think the notion of quality     (1L2AAAAAAAAAAAAAAM)

will vary between an ontologist and an application user/manager.     (1L2AAAAAAAAAAAAAAN)

[11:25] Amanda Vizedom: @Leo, yes, I am asking whether -- and if so, why -- these characteristics are     (1L2AAAAAAAAAAAAAAO)

intrinsic aspects of *quality*. It could be that they are intrinsic metrics, but the relevance to     (1L2AAAAAAAAAAAAAAP)

quality depends on extrinsic factors.     (1L2AAAAAAAAAAAAAAQ)

[11:25] Amanda Vizedom: @Samir, I think that nails it. Thank you. (re. Samir's verbal response.)     (1L2AAAAAAAAAAAAAAR)

[11:25] Samir Tartir: @Amanda: Thank you.     (1L2AAAAAAAAAAAAAAS)

[11:25] MariaPovedaVillalon: In addition there is a temporal aspect on that, one class can have few     (1L2AAAAAAAAAAAAAAT)

instances today, but will populated later     (1L2AAAAAAAAAAAAAAU)

[11:28] Amanda Vizedom: @Leo and @Samir: My reason for wanting the relationship addressed may also be     (1L2AAAAAAAAAAAAAAV)

a reason that some reviewers objected: there is a lot of history of these being treated as quality     (1L2AAAAAAAAAAAAAAW)

metrics, without any obvious reason. @Samir, if that's true, then making clear the relationship you     (1L2AAAAAAAAAAAAAAX)

see, as you articulated it, might well satisfy those critics.     (1L2AAAAAAAAAAAAAAY)

[11:29] Doug Foxvog: @Maria & @Mari: if one has several local ontologies, one that includes the     (1L2AAAAAAAAAAAAAAZ)

other, can the combined ontologies be analyzed together?     (1L2AAAAAAAAAAAAAAAA)

[11:29] MariaPovedaVillalon: @doug you can either make them available online so that the owl:imports     (1L2AAAAAAAAAAAAAAAB)

can be resolved or gather them in one file and paste it into OOPS! textbox     (1L2AAAAAAAAAAAAAAAC)

[11:31] Leo Obrst: Behind some of this discussion is the presupposition that evaluation is only about     (1L2AAAAAAAAAAAAAAAD)

[11:31] Peter P. Yim: @Leo - is that presupposition proper (in the context of this summit) or not?     (1L2AAAAAAAAAAAAAAAF)

[11:32] Amanda Vizedom: Suggestion: So, we see the likelihood that there are (many, I'd say)     (1L2AAAAAAAAAAAAAAAG)

suitability is *extrinsic* (at least partially).     (1L2AAAAAAAAAAAAAAAI)

[11:33] Steve Ray: @Amanda: I agree with you.     (1L2AAAAAAAAAAAAAAAJ)

[11:34] Leo Obrst: @Peter: I think comparison of ontologies is an important issue for ontology     (1L2AAAAAAAAAAAAAAAK)

evaluation, and one person's notion of "quality" may vary from another person's, so comparing     (1L2AAAAAAAAAAAAAAAL)

different metrics and allowing weighting of various metrics may be useful.     (1L2AAAAAAAAAAAAAAAM)

[11:34] Samir Tartir: @Amanda: You mean intrinsic-extrinsic links? That's a good idea.     (1L2AAAAAAAAAAAAAAAN)

[11:37] Amanda Vizedom: @Leo, that may be so. Or it may simply be that we want/need to clarify the     (1L2AAAAAAAAAAAAAAAO)

relationship. Some evaluations (or evaluation tools) may be designed to rank ontologies by quality     (1L2AAAAAAAAAAAAAAAP)

without further information. Those, IMHO, are misguided. What is more promising, IMHO, is a     (1L2AAAAAAAAAAAAAAAQ)

framework/toolkit with the capability of evaluating many characteristics, perhaps neutrally to their     (1L2AAAAAAAAAAAAAAAR)

relevance to quality in specific cases. It could be up to the user to select which characteristics     (1L2AAAAAAAAAAAAAAAS)

they care about. Or, in my fantasy system (such as that which Joanne Luciano and other have     (1L2AAAAAAAAAAAAAAAT)

proposed), a tool in which the use case could be described and ontologies evaluated according to     (1L2AAAAAAAAAAAAAAAU)

[11:37] Terry Longstreth: @Leo - any metacharacteristic may be the basis for a quality judgement,     (1L2AAAAAAAAAAAAAAAW)

depending on what's important to the user community. Size for example may be impactful in     (1L2AAAAAAAAAAAAAAAX)

determining what systems resources will need procurement actions.'     (1L2AAAAAAAAAAAAAAAY)

[11:38] Torsten Hahmann: Some addition to the example that Fabian used in his remark (depth may be     (1L2AAAAAAAAAAAAAAAZ)

useful only in specific contexts): the context also determines how to measure depth. There are     (1L2AAAAAAAAAAAAAAAAA)

dozens of ways one could measure depth, for example: average, shallowest, deepest, relative to     (1L2AAAAAAAAAAAAAAAAB)

breadth, standard deviation, etc. Which of those metrics properly measures the intended quality (a     (1L2AAAAAAAAAAAAAAAAC)

quality "specificity", for example)? Something to explore in the future.     (1L2AAAAAAAAAAAAAAAAD)

[11:40] Doug Foxvog: @Torsten: that would depend upon the task. It might be interesting to define     (1L2AAAAAAAAAAAAAAAAE)

desired features of ontologies & KBs using some of the metrics that have been described.     (1L2AAAAAAAAAAAAAAAAF)

[11:37] Peter P. Yim: great session ... thanks everyone!     (1L2AAAAAAAAAAAAAAAAG)

[11:37] Samir Tartir: Thank you all. Very interesting, looking forward to more discussions.     (1L2AAAAAAAAAAAAAAAAH)

[11:37] MariCarmenSuarezFigueroa: Thank you very much for your comments and suggestions.     (1L2AAAAAAAAAAAAAAAAJ)

[11:37] MariaPovedaVillalon: Thank you for your comments :-) bye     (1L2AAAAAAAAAAAAAAAAO)

[11:38] Doug Foxvog: This was a very good session! Bye!     (1L2AAAAAAAAAAAAAAAAQ)

[11:38] Peter P. Yim: join us again, same time next week, for Ontology Summit 2013 session-04: "Building     (1L2AAAAAAAAAAAAAAAAR)

Ontologies to Meet Evaluation Criteria - I" - Co-chairs: Matthew West & Mike Bennett -     (1L2AAAAAAAAAAAAAAAAS)

[11:37] Peter P. Yim: -- session ended: 11:37 am PST --     (1L2AAAAAAAAAAAAAAAAU)

-- end of in-session chat-transcript --     (1L2AAAAAAAAAAAAAAAAAD)

Additional Resources     (1M)

How To Join (while the session is in progress)     (1N)

  • Dial-in:     (1N4D)
    • Phone (US): +1 (206) 402-0100 ... (long distance cost may apply)     (1N4D1)
    • Skype: joinconference (i.e. make a skype call to the contact with skypeID="joinconference") ... (generally free-of-charge, when connecting from your computer)     (1N4D2)
      • when prompted enter Conference ID: 141184#     (1N4D2A)
      • Unfamiliar with how to do this on Skype? ...     (1N4D2B)
        • Add the contact "joinconference" to your skype contact list first. To participate in the teleconference, make a skype call to "joinconference", then open the dial pad (see platform-specific instructions below) and enter the Conference ID: 141184# when prompted.     (1N4D2B1)
      • Can't find Skype Dial pad? ...     (1N4D2C)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1N4D2C1)
        • for Linux Skype users: please note that the dial-pad is only available on v4.1 (or later; or on the earlier Skype versions 2.x,) if the dialpad button is not shown in the call window you need to press the "d" hotkey to enable it. ... (ref.)     (1N4D2C2)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at:     (1N4E)
    • view-only password: "ontolog"     (1N4E1)
    • if you plan to be logging into this shared-screen option (which the speaker may be navigating), and you are not familiar with the process, please try to call in 5 minutes before the start of the session so that we can work out the connection logistics. Help on this will generally not be available once the presentation starts.     (1N4E2)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the slides above (where applicable) and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1N4E3)
    • instructions: once you got access to the page, click on the "settings" button, and identify yourself (by modifying the Name field from "anonymous" to your real name, like "JaneDoe").     (1N4F1)
    • You can indicate that you want to ask a question verbally by clicking on the "hand" button, and wait for the moderator to call on you; or, type and send your question into the chat window at the bottom of the screen.     (1N4F2)
    • thanks to the folks, one can now use a jabber/xmpp client (e.g. gtalk) to join this chatroom. Just add the room as a buddy - (in our case here) ... Handy for mobile devices!     (1N4F3)
  • Discussions and Q & A:     (1N4G)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1N4G1)
    • To un-mute, press "*7" ... To mute, press "*6" (please mute your phone, especially if you are in a noisy surrounding, or if you are introducing noise, echoes, etc. into the conference line.)     (1N4G2)
    • we will usually save all questions and discussions till after all presentations are through. You are encouraged to jot down questions onto the chat-area in the mean time (that way, they get documented; and you might even get some answers in the interim, through the chat.)     (1N4G3)
    • During the Q&A / discussion segment (when everyone is muted), If you want to speak or have questions or remarks to make, please raise your hand (virtually) by clicking on the "hand button" (lower right) on the chat session page. You may speak when acknowledged by the session moderator (again, press "*7" on your phone to un-mute). Test your voice and introduce yourself first before proceeding with your remarks, please. (Please remember to click on the "hand button" again (to lower your hand) and press "*6" on your phone to mute yourself after you are done speaking.)     (1N4G4)
  • RSVP to with your affiliation appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the community already.)     (1N4I)
  • Please note that this session may be recorded, and if so, the audio archive is expected to be made available as open content, along with the proceedings of the call to our community membership and the public at-large under our prevailing open IPR policy.     (1N4K)

Attendees     (1O)

This page has been migrated from the OntologWiki - Click here for original page     (1O5)