From OntologPSMW

Revision as of 01:41, 9 January 2016 by KennethBaclawski (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
[ ]


Ontology Summit 2013 (Pre-launch) Community Input and Planning Session - Thu 2012-12-13     (1)

  • Summit Theme: Ontology Evaluation Across the Ontology Lifecycle     (1A)
  • Agenda: This is a (pre-launch) communitywide brainstorming and planning session for OntologySummit2013     (1C)

Abstract     (1E)

The upcoming Ontology Summit 2013 is co-organized by Ontolog, NIST, NCOR, NCBO, IAOA, NCO_NITRD.     (1E1)

This is the 8th year we are organizing this annual, international, open Ontology Summit event. The general format of the event comprises a series of both virtual and face-to-face activities that span about 3 months (roughly, January through mid April each year). These activities include a vigorous three-month online discourse on the theme of the Summit, which, for this upcoming season, virtual panel discussions, research activities, and so on, which will culminate in a two-day face-to-face workshop and symposium at NIST in Gaithersburg, Maryland, USA. Each year, we publish a Summit Communiqu�� to offer a message from the Summit participants to the world-at-large as a signature activity of the Ontology Summit series.     (1E2)

Based on input collected and considering what would be of strategic importance to the ontology domain that is worthy of focusing the energy of the Ontology Summit community into, the co-organizers has picked "Ontology Evaluation Across the Ontology Lifecycle" as the theme for this Summit.     (1E3)

As most of us are aware, 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.     (1E4)

The goal for Ontology Summit 2013 is 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��.     (1E5)

This is the (pre-launch) communitywide brainstorming and planning session for those who are passionate about the subject and would like to influence and help drive the outcome by helping refine the ideas, program, organization and process for the 2013 Ontology Summit season.     (1E6)

Our developing 2013 Ontology Summit home page is at: OntologySummit2013     (1E7)

Agenda & Proceedings     (1F)

0. Participant self-introduction (if size of participants is manageable) (15~30 seconds each)     (1F1)

1. Opening �� co-chairs - [ slides ]     (1F2)

2. Open floor for ideas on developing and executing the program (All) -- please refer to [ process above]     (1F3)

2.1 Defining the theme and its scope     (1F4)
o the selected theme is: Ontology Evaluation Across the Ontology Lifecycle     (1F4A)
2.2 Brainstorming on ideas that support the theme - ref. OntologySummit/Suggestions     (1F5)
o who (organizations, individuals) should we really try to engaging     (1F5A)
o Tracks, Topics, Speakers, Invitees, Publicity ... and more     (1F5B)
o see a strawman for the choice of tracks in the co-chairs' post at:     (1F5B1)
o Crafting a program that will allow us to make the best out of this next Ontology Summit     (1F5C)
o Approach and Execution     (1F5D)

3. A call for volunteers and champions ... and, getting ourselves organized - note: first organizing committee meeting tomorrow - Fri 2012.12.14 - 2-Hr meeting starting 8:00am PST / 11:00am EST / 5:00pm CET / 16:00 GMT/UTC - see:     (1F6)

3.1 Members of the organizing committee will be invited to join by either the general co-chairs or the summit co-organizers.     (1F7)
3.2 Volunteers who want to join us in the organizing committee should so indicate during this meeting* and be prepared to participate at the first organizing committee meeting on Fri 2012.12.14. ... (*Those who cannot make it to this meeting should indicate their interesting to join the organizing committee by emailing the general co-chairs: <>, <> with a copy to <> by mid-day Thu 2012.12.13.)     (1F8)
3.3 Those who are planning to participate in the organizing committee should be cognizant of the committee process and expectations.     (1F9)

4. A discussion and call for:     (1F10)

  • Communities we should engage to advance the agenda of this summit     (1F11)
  • Co-sponsors ...('Co-sponsors' are organizations who are providing technical or funding support, and/or endorsing the purpose (i.e. the objective) of this Ontology Summit)     (1F12)
  • Recommendations on candidates for the Advisory Committee     (1F13)

5. Summary and wrap-up (co-chairs)     (1F14)

  • please mark Ontology Summit 2013 Launch date, and be sure to join us at that event: Thursday 17-Jan-2012 - 2-Hr session starting 9:30am PST / 12:30pm EST / 6:30pm CET / 17:30 GMT/UTC     (1F15)
  • get subscribed to the [ontology-summit] mailing list if you aren't on it already.     (1F16)

Proceedings     (1G)

Please refer to the above     (1G1)

IM Chat Transcript captured during the session    (1G2)

see raw transcript here.     (1G2A)

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

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

-- begin of chat session --     (1G2D)

[09:00] Peter P. Yim: Welcome to the     (1G2E)

Ontology Summit 2013 (Pre-launch) Community Input and Planning Session - Thu 2012-12-13     (2)

  • Summit Theme: Ontology Evaluation Across the Ontology Lifecycle     (2A)

Logistics:     (2D)

  • (if you haven't already done so) please click on "settings" (top center) and morph from "anonymous" to your RealName (in WikiWord format)     (2F)

earlier Skype versions 2.x,) if the dialpad button is not shown in the call window you need to press     (2K)

the "d" hotkey to enable it.     (2L)

Proceedings:     (2M)

[09:20] Matthew West: @Peter: Michael will present, I will do process.     (2M7)

[09:23] anonymous morphed into Robert Rovetto     (2M8)

[09:25] anonymous morphed into Javier G     (2M9)

[09:29] anonymous1 morphed into Amanda Vizedom     (2M10)

[09:29] anonymous morphed into Simon Spero     (2M11)

[09:33] Peter P. Yim: == Matthew West starts the session ...     (2M12)

[09:35] anonymous morphed into Onno Paap     (2M13)

[09:37] Peter P. Yim: == self-introductions by everyone in the session ...     (2M14)

[09:39] anonymous morphed into ZubeidaCasmodDawood     (2M15)

[09:38] GaryBergCross: David M Let's talk something about the NLP help you might provide to extract     (2M16)

concepts from text as a way of starting ontology work.     (2M17)

[09:40] David Mendes: Please start to contact me via skype: (diverzulu [at] or mail:     (2M18)

dmendes [at] . Whenever suits you best. Thank you very much in advance :)     (2M19)

[09:42] David Mendes: Please provide me with your contacts Gary !     (2M20)

[09:43] Anatoly Levenchuk: We have experiments with NLP for ISO 15926 --     (2M21)

stics-analysis (but now we have more).     (2M23)

[09:43] anonymous2 morphed into Alan Rector     (2M24)

[09:43] anonymous morphed into Jack Ring     (2M25)

[09:43] anonymous1 morphed into Deana Pennington     (2M26)

[09:44] Alan Rector: Something bizarre has happened to the wiki. It seems to be serving things so     (2M27)

thatthey only show up in raw HTML, -= three browsers on two machines tried.     (2M28)

[09:45] Ram D. Sriram: @Alan: Same thing happened to me on the Mac. Try clicking on the link in the     (2M29)

jumbled version and you will be taken to the right page.     (2M30)

[09:46] Peter P. Yim: @AlanRector - thank you for notifying us of the issue ... fixed now! (a bug in the     (2M31)

wiki - happens when there is a write conflict.)     (2M32)

[09:44] David Mendes: Seems to be working fine here, Alan !     (2M33)

[09:44] anonymous morphed into Joanne Luciano     (2M34)

[09:48] anonymous morphed into Tom Tinsley     (2M35)

[09:49] anonymous morphed into Pavithra Kenjige     (2M36)

[09:54] anonymous morphed into Marcela Vegetti     (2M37)

[09:55] Peter P. Yim: on the call (but not in the chat-room yet): Ed Lowry, ...     (2M38)

[09:56] Joanne Luciano: @LeoObrst - Leo, I've just gotten back from travel. I got your email and     (2M39)

would like to follow up.     (2M40)

[09:58] Peter P. Yim: Ram D. Sriram ask what day of week is preferred for the symposium (in April)     (2M41)

[09:45] Ram D. Sriram: I will need to leave at 1pm for another meeting. Will need know the potential     (2M42)

dates in April for the face-face meeting at NIST.     (2M43)

[09:42] Fabian Neuhaus: Ram: you meant April (not January, right?)     (2M44)

[09:58] Peter P. Yim: general preference seems to be Thursday & Friday ... but then locals in the     (2M45)

Washington DC area prefers that we don't pick Fridays     (2M46)

[09:58] David Mendes: Any date is fine for me !     (2M47)

[10:00] Amanda Vizedom: Suggest leaving a day after Symposium for associated / follow-up workshops,     (2M48)

vocamps, etc.     (2M49)

[10:01] anonymous morphed into Trish Whetzel     (2M50)

[10:02] Michael Grüninger: Possible Symposium Dates: a) 16,17 b) 17,18 c)11,12 d) 18,19     (2M51)

[10:03] Matthew West: (after much deliberation) Proposed dates are for the Symposium, in order of     (2M52)

preference, are: April 16-17 (Tue-Wed), 17-18 (Wed-Thu), 11-12 (Thu-Fri).     (2M53)

[10:10] List of members in the chat now: Aida Gandara, Alan Rector, Alex Shkotin, Amanda Vizedom,     (2M54)

[10:09] Peter P. Yim: == Michael Grüninger walking us through the slides ...     (2M60)

Theme: "Ontology Evaluation Across the Ontology Lifecycle" ( ref.     (2M61)

Proposed Tracks:     (2M63)

1. Dimensions of Ontology Evaluation - addresses notions of verification, validation, quality,     (2M64)

ranking, ... (02)     (2M65)

2. Evaluation and the Ontology Application Framework - looks at the problem of ontology evaluation     (2M66)

from the perspective of the applications that use the ontologies. This Framework was one of the     (2M67)

outcomes of Ontology Summit 2011     (2M68)

3. Best Practices in Ontological Analysis - focuses on the ontology evaluation based on the ontology     (2M70)

itself, such as logical criteria (consistency, completeness, modularity) and ontological analysis     (2M71)

techniques (e.g. OntoClean). (04)     (2M72)

4. Requirements for Ontologies - how do we specify the requirements against which we evaluate     (2M73)

ontologies? (05)     (2M74)

5. Environments for Developing and Evaluating Ontologies - what are best practices for evaluation     (2M75)

that we can adapt from software engineering, particularly with distributed open-source software     (2M76)

development? (06)     (2M77)

[10:18] Peter P. Yim: == starting Discussion segment: Review of current proposals for topics and tracks     (2M79)

for this year's theme     (2M80)

[10:12] GaryBergCross: Michael why not call it "Ontology Development and Evaluation across...."?     (2M81)

That is add Development explicitly.     (2M82)

[10:17] Terry Longstreth: @Gary - Track 4 talks to evolvability, implying that development may not     (2M83)

have a fixed completion point, in contrast to systems development     (2M84)

[10:13] Jack Ring: The characterization of life cycle can be improved.     (2M85)

[10:16] RosarioUcedaSosa: Seems like tracks 2 and 4 are closely related.     (2M86)

[10:16] Mike Bennett: Ontology Application Framework is important as it challenges the assumptions     (2M87)

some practitioners may have to the effect that what they assume an ontology is "for" is the only     (2M88)

thing they are for. Sometimes the development and QA questions are framed with one specific "for" in     (2M89)

[10:17] RosarioUcedaSosa: From what I hear Michael propose, we're dealing with Ontology     (2M92)

specification and goals, Ontology Quality and Ontology Usability (how it's easier to use)     (2M93)

[10:17] Alex Shkotin: For evaluation we need metrics.     (2M94)

[10:17] Anatoly Levenchuk: Track 4: Better "requirements engineering" because "requirements     (2M96)

management" is only about configuration management and distribution of already created requirements.     (2M97)

[10:18] Jack Ring: there may be more to learn from system engineering than from software engineering.     (2M98)

[10:19] Anatoly Levenchuk: @JackRing: we should take from both Software and Systems Engineering.     (2M99)

[10:18] GaryBergCross: Comment on track 5. I think the issue of including ontology development as     (2M100)

part of app/system development is important.     (2M101)

[10:19] Amanda Vizedom: Re: requirements -- not only specification but *identification*     (2M102)

[10:20] Amanda Vizedom: that is, the process of looking at a use case and figuring out what about it     (2M103)

has implications for ontology requirements...     (2M104)

[10:21] Amanda Vizedom: ... and then, figuring out what those implications *are*...     (2M105)

[10:22] Amanda Vizedom: Requirements ID is necessary background for evaluation. It is often skipped,     (2M106)

precisely because people too often make the assumption Mike Bennett mentions above.     (2M107)

[10:21] Alex Shkotin: Other dimension - what kind of methodology has been used to create ontology? If     (2M108)

[10:21] Joanne Luciano: How many of the candidates do we select, or is it just one?     (2M110)

[10:23] Joanne Luciano: HOW MANY TRACKS do we select?     (2M111)

[10:25] Leo Obrst: @Joanne: We can decide that all 5 tracks will be selected, and probably max of 5     (2M112)

tracks for logistical purposes. We are also considering whether these tracks are the ones we agree     (2M113)

[10:24] Fabian Neuhaus: I have a clarification question concerning track 1 to Michael. The list     (2M115)

verification, validation ..., metrics seems to include very different notions. What do you mean by     (2M116)

dimension?     (2M117)

[10:30] Michael Grüninger: @Fabian: re: dimension I was trying to convey the idea that there are     (2M118)

different sets of criteria that are independent of each other. The notion of metrics was added     (2M119)

because it was appearing in many postings, but the other notions (such as verification and     (2M120)

validation) were more qualitative.     (2M121)

[10:30] Steve Ray: @Mike: +1     (2M122)

[10:21] Michael Grüninger: What makes an ontology usable by domain experts? (Rosario)     (2M123)

[10:24] RosarioUcedaSosa: Three dimensions associated with the ontology lifecycle: Ontology     (2M124)

specification (roughly track 1) Ontology building (roughly track 3) and then ontology querying and     (2M125)

navigation (usability) by domain users (not sure what this track would be). Mostly a re-factoring to     (2M126)

follow the ontology lifecycle theme.     (2M127)

[10:27] Robert Rovetto: If I may suggest an answer to the question 'What makes an ontology usable by     (2M128)

domain experts?'... Perhaps this is an obvious or simple answer but an ontology is usable by a     (2M129)

domain expert if (U1) the ontology accurately reflects the universe of discourse (the domain subject     (2M130)

matter) that is the expertise of the domain expert, (U2) the ontology supports the expert in their     (2M131)

research/work,...(Un)     (2M132)

[10:25] Jack Ring: The 'ontology life cycle' is naive. There will be numerous ontologies in any     (2M133)

system of non-trivial size and each will likely evolve greatly so the notion of begin-middle-end is     (2M134)

misleading.     (2M135)

[10:26] Amanda Vizedom: @Jack: I don't think "lifecycle" assumes begin-middle-end... there are still     (2M136)

lifecycles in continuous processes.     (2M137)

[10:26] Simon Spero: @AmandaVizedom it's why it's called a cycle     (2M138)

[10:27] Terry Longstreth: @Todd, Jack, Amanda: Ontology lifecycle probably more like the data     (2M139)

lifecycle, which may extend into eternity (i.e. well passed the cycle of any one system)     (2M140)

[10:28] Amanda Vizedom: @Terry, I'd suggest that it's often a hybrid, and also varies with     (2M141)

application     (2M142)

[10:29] Pavithra Kenjige: Life cycle refers to stages of development, maintenance, usage, disposal     (2M143)

... and Reuse too, which is part Usage..     (2M144)

[10:33] Anatoly Levenchuk: @PavithraKenjige: before development there are stage of conception (before     (2M145)

requirements engineering and architectural design of development substage). Decision to invest in     (2M146)

development. Loooong stage usually :-)     (2M147)

[10:29] RosarioUcedaSosa: @Jack We're trying to categorize the validation criteria for an ontology     (2M148)

at different stages, not necessarily thinking that these stages are linear or iterative.     (2M149)

[10:27] GaryBergCross: As information products ontologies have some of the usual phases from Req and     (2M150)

anlysis to design to building, evaluation etc.     (2M151)

[10:28] Matthew West: I'd like to see how Information quality Management can help us frame and     (2M152)

justify how we evaluate ontologies since ontologies ultimately provide information to support     (2M153)

decisions.     (2M154)

[10:28] Todd Schneider: First, need to include operations or operational use.     (2M155)

[10:29] Peter P. Yim: +1 on Todd and others, on the consideration for the "full" lifecycle, and the need     (2M156)

to ground our discourse to domain applications, too ... Within the application track, I suggest     (2M157)

sub-tracks (to the extent that collaborating communities and champions are available) covering     (2M158)

specific domains, against whose requirements and use case scenarios, we will craft the evaluation     (2M159)

criteria - candidate domains may include (a) use of ontology in standards, (b) use of ontology in     (2M160)

harnessing data (bigdata? ... if that's too "big" try "research data), (c) ontology in earth     (2M161)

science, (d) ontology in bio of medical informatics, (e) ...etc.     (2M162)

[10:30] GaryBergCross: Ontology content will have requirements, but also the ontology product may     (2M163)

have architectural and interface requirements to work within a system.     (2M164)

[10:30] Steve Ray: The larger issue is one of scope for the summit. We need to decide if we are going     (2M165)

to address "evaluation", or a broader "ontology lifecycle" that could include development,     (2M166)

requirements gathering, etc. etc. One risk is that many people argue that xyz is important, so we     (2M167)

should include it, at the expense of focus for the summit.     (2M168)

[10:33] Michael Grüninger: @SteveRay: The focus is still on Ontology Evaluation. The tracks are     (2M169)

intended to explore this in more detail by identifying the different ways in which people evaluate     (2M170)

ontologies, particularly with respect to applications and the original intention of the ontology     (2M171)

[10:30] Todd Schneider: What are the differences among 'ontology lifecycle' and engineering     (2M172)

lifecycle? Should they be considered equivalent and hence adopted as an organizing paradigm for this     (2M173)

[10:30] Tom Tinsley: Lifecycle in software and hardware means cradle to grave. Since ontology is     (2M175)

capturing knowledge, is there a grave?     (2M176)

[11:01] Amanda Vizedom: @TomTinsley, it could be used that way, but it could also be used to measure     (2M177)

fitness of ontologies to uses, and ontologists' ability to develop usable ontologies for particular     (2M178)

kinds of uses.     (2M179)

[10:30] Amanda Vizedom: I have worked on cases where ontology is system component, developed and test     (2M180)

incrementally everyday along with other system components, with periodic freezes with more formal     (2M181)

testing that then, when sufficiently QAed, become the live system. The next live system is never not     (2M182)

under development and testing and the most recent one to be frozen & QAed is never not live.     (2M183)

[10:30] Terry Longstreth: @Amanda: of course, but I'm pushing back against the engineering lifecycle,     (2M184)

which ends in disposal     (2M185)

[10:32] Amanda Vizedom: @Terry, Ok, get it. I'd say that applies to some and not others. If dev     (2M186)

continues, with versioning, then any individual version does have that kind of cycle. But not all.     (2M187)

[10:32] Mike Bennett: @Terry Amanda Surely any lifecycle leads to some sort of success, whether that     (2M188)

is then built on for some subsequent success or not?     (2M189)

[10:32] Jack Ring: @All, the sooner you shed lifecycle and focus on usage scenarios the quicker you     (2M190)

will become relevant to and appreciated by practitioners.     (2M191)

[10:32] RosarioUcedaSosa: It may be worth describing the different ways to specify an ontology     (2M192)

(whether it's existing or not) for a particular goal. Also, there needs to be a disciplined way to     (2M193)

build' or change the ontology. The considerations here may be different, as we're trying to build     (2M194)

(or modify, or integrate) a high quality ontology. The third discussion is around how easy it is to     (2M195)

use. This may require usability studies, or comparisons with existing vocabulary.     (2M196)

[10:32] Leo Obrst: Lifecycle has to include how the ontology interacts with other components of the     (2M197)

architecture and the data/software deployments, e.g., mapping vocabularies to the ontologies,     (2M198)

linking data sources to the ontologies, application interface and reasoning services, etc. An     (2M199)

excellent ontology does not mean that a given ontology application effort will succeed; so we need     (2M200)

to evaluate the ontology within its emerging application environment(s), maintenance, and reuse,     (2M201)

redeployment, etc.     (2M202)

[10:33] Simon Spero: @Rosario: Of possible relevance is some of the work that Hollie White did for     (2M203)

her dissertation, where she compared the metadata & term assignment behavior of domain scientists     (2M204)

[10:33] Alan Rector: It's critical to evaluate the ontology against its purposes and its claims and     (2M206)

what would count as evidence. We have lots of claims in the biomedical community for criteria for     (2M207)

quality, frequently without explicit purpose or agreement of what counts as evidence     (2M208)

[10:41] Joanne Luciano: @ AlanRector's "It's critical to evaluate the ontology against its purposes     (2M209)

and its claims and what would count as evidence" ... The little research I did, when I took the     (2M210)

framework approach - that included extrinsic and intrinsic quality metrics was that these can be     (2M211)

articulated in use case formalization. I would like to see use case as part of the evaluation     (2M212)

criteria. So, agree and +1 with Amanda in the @Gary post     (2M213)

[10:33] RosarioUcedaSosa: thanks, Simon. I'll check it out.     (2M214)

[10:31] Alex Shkotin: Ontology classification theme should be very important. As we should have many     (2M215)

different kinds. And evaluate differently:-)     (2M216)

[10:33] Amanda Vizedom: @Alex, IME, there is to much variety and uniqueness to make classification of     (2M217)

ontologies as whole very useful. I think it more useful to talk in terms of *features* (some of     (2M218)

which may come in degrees) which ontologies may or may not have...     (2M219)

[10:36] Alex Shkotin: @Amanda, consider different kind of databases - operational, analytical... We     (2M220)

should have even more, I think.     (2M221)

[10:33] Jack Ring: Seems like we need an ontology for "ontology"     (2M222)

[10:34] GaryBergCross: Some people may evaluate an ontology based on how easy it might be for their     (2M223)

group to maintain. So modularity might come into play, but also whether the formalism are understood     (2M224)

and well supported etc.     (2M225)

[10:34] Terry Longstreth: I'm probably going against the flow here, but I believe that a successful     (2M226)

ontology is an organic object, that grows and evolves in step with the human (or cultural, or world,     (2M227)

or sentient) knowledge that informs it.     (2M228)

[10:34] Mike Bennett: Sorry I have to go!     (2M229)

[10:34] RosarioUcedaSosa: @Gary, that's part of the usability criteria.     (2M230)

[10:35] Amanda Vizedom: ... and how ontology requirements point to the ontology features that     (2M231)

matter... and then, hugely important, how (and to what extent) those features can be evaluated.     (2M232)

[10:35] Alan Rector: I would like to second this. What counts as evidence?     (2M233)

[10:35] GaryBergCross: @Rosario yes, usability criteria sounds like a good dimension.     (2M234)

[10:37] Amanda Vizedom: @Gary, I would relate that to the extent to which a use case requires expert     (2M235)

verification and/or human end-user support. Either of these adds understandability, by some group of     (2M236)

humans, to the requirements.     (2M237)

[10:41] Joanne Luciano: +1 with Amanda in the @Gary post     (2M238)

[10:35] Michael Grüninger: Track 3 will be "Best Practices and Techniques in Ontology Evaluation"     (2M239)

[10:37] Jack Ring: I suggest that Track 3 include instances of Worst Practices as well. Mistakes are     (2M241)

the prime root of learning.     (2M242)

[10:38] Simon Spero: @JackRing: These are usually referred to as AntiPatterns     (2M243)

[10:38] Alex Shkotin: @Jack Yes!     (2M244)

[10:40] John Bateman: @JackRing and some other comments: Note also results of the Ontology Summit 2007     (2M245)

on the classification of distinct types (dimensions) of ontologies: seems that this might also come     (2M246)

in as a way of characterising what *can* be done with an ontology and so whether it might be     (2M247)

expected to meet some requirements -     (2M248)

[10:40] Amanda Vizedom: @Jack - this is something I wanted to evoke in the survey last year. I know     (2M250)

that there are many, many examples out there of people doing evaluation that is not predictive of     (2M251)

whether the ontology works for intended use. I hoped to get folks to share them, along with more     (2M252)

successful evaluations, so that we could learn. Unfortunately, building survey ended up     (2M253)

harder/longer than worked with summit timeline. But I still thing that the very large pile of     (2M254)

community wide experiences, and/or lessons learned, is a gold mine for this.     (2M255)

[10:41] Terry Longstreth: Pavithra has a standard model of Ontology development that parallels system     (2M256)

development; is it possible that ontologies might be products (at least partially) of system     (2M257)

execution?     (2M258)

[10:38] GaryBergCross: @Rosario as with any Info product its documentation across the cycle is     (2M259)

important.     (2M260)

[10:41] RosarioUcedaSosa: @Gary Yes, but we have to be careful. Requiring a full specification as in     (2M261)

a software lifecycle may be too complex for most practitioners (and has had limited success in the     (2M262)

wider software engineering community) There may be alternate -easier- requirements in the linked     (2M263)

data community... I don't claim to have the answers, but would advocate keeping the validation and     (2M264)

formal aspects as simple as possible.     (2M265)

[10:43] Michael Grüninger: I didn't mean for the Ontology Lifecycle to be the focus; rather, it was     (2M266)

meant to draw attention to a broader approach to evaluation that includes requirements and     (2M267)

applications. If the phrase "Ontology Lifecycle" is getting in the way, we can drop it from the     (2M268)

title. The important thing is the set of topics covered in the tracks.     (2M269)

[10:50] Leo Obrst: @Michael: I think it's important to keep emphasizing the Ontology "Lifecycle" in     (2M270)

the Summit, since the ontology may have to morph or separate into components, get refined, etc.,     (2M271)

based on evolution of the application(s).     (2M272)

[10:41] Simon Spero: @GaryBergCross: Documentation-and-software-engineering "Ron Jeffries: "I was     (2M273)

taught by Kent Beck that need for a comment is the code's way of asking to be more clear. I strive     (2M274)

to make the code more clear and to see if the need for the comment goes away. Usually it does."     (2M275)

[10:41] Jack Ring: @Simon, "usually" doesn't cover most of the 1 million people engaged in system     (2M276)

engineering, the 6 million software engineering or the few who are concerned with semantic accuracy.     (2M277)

Where I come from Anti- means Not or As Contrasted To whereas worst practices are patterns, too. See     (2M278)

John Gall, Systemantics.     (2M279)

[10:46] Simon Spero: @jackRing: Koenig, A. (1995). "Patterns and Antipatterns". Journal of     (2M280)

Object-Oriented Programming 8 (1): 4648. See also     (2M281)

[10:44] GaryBergCross: @Simon I'm not sure that I agree with this idea of clean code speaking as     (2M282)

clearly as documentation. In ontology development one often needs to explain scoping and commitment     (2M283)

choices and what went into that.     (2M284)

[10:43] Till Mossakowski: Considering candidate Track 5: the open ontology repository (OOR) community     (2M285)

has developed an architecture for ontology development in distributed, federated, heterogeneous     (2M286)

repositories, generalising what is there in Bioportal. This includes ontology development, logical     (2M287)

reasoning, ontology review and workflows. Heterogeneous means that not only OWL, but also RDF,     (2M288)

Common Logic, UML,... are possible languages. Ontohub is a current open-source effort that tries to     (2M289)

implement this architecture in a style inspired by github. Would there be interest in discussing the     (2M290)

design principles of ontohub and also in doing some coding?     (2M291)

[10:46] Peter P. Yim: +1 to TillMossakowski's comment ... using OOR as a platform/environment to     (2M292)

instantiate ontology evaluation tools     (2M293)

[10:46] Peter P. Yim: also suggesting, we form implementation teams for, for example, (i) extreme     (2M294)

programming team(s) to do things on, say, on some ontology evaluation platform, (ii) a semantic wiki     (2M295)

team (we may start using the OntologPSMW (purple semantic media wiki) this year, as a beta for this     (2M296)

summit, (iii) integration and demo team (in preparation for something we might possibly do, as a     (2M297)

segment of the symposium, (iv) a Public Relations / Marketing team that gets the word out, so this     (2M298)

summit can make an impact ... some of the above tasks may be merged and streamlined (so it may only     (2M299)

be a couple of teams we would need to create)     (2M300)

[11:02] Peter P. Yim: For the PSMW (purple semantic mediawiki) effort, we are planning on making a debut     (2M301)

of the OntologPSMW next week - see:     (2M302)

[10:50] Simon Spero: @PeterYim: XP/Agile bib entries from last year:     (2M304)

[10:56] Peter P. Yim: @SimonSpero - thank you for the references to Agile Methodologies and Extreme     (2M306)

Programming     (2M307)

[10:58] Amanda Vizedom: RE: sharing reference resources: Last year we built the zotero library @Simon     (2M308)

just pointed to, as an auxiliary, collaborative library/bibliography. We started it mid-summit,     (2M309)

though, and wished we'd started from the beginning. I can start one for this year this moment, if     (2M310)

folks would find it useful... we can cross list items from last year over to it without duplicating     (2M311)

resources.     (2M312)

[10:44] Peter P. Yim: for "best practice" or "environments" - who (person, community, ...) in Software     (2M313)

Engineering, or Systems Engineering, can we engage and collaborate with, to help us advance the     (2M314)

cause of this summit? ... need specific names of champions/volunteers who can push this forward     (2M315)

[10:44] Joanne Luciano: Don't know if this is appropriate here, but I'm also looking for anyone who     (2M316)

want to collaborate on developing the framework further. I have an implementation started but need     (2M317)

other ontogeeks to play with to help it develop     (2M318)

[10:45] Alex Shkotin: Ontology itself is a piece of knowledge. And should be some methods of     (2M319)

knowledge evaluation. Other point - the place, role of ontology in information system - like     (2M320)

database...     (2M321)

[10:49] Robert Rovetto: @Alex Depending on what you mean by 'a piece of knowledge'... Ontology,     (2M322)

itself (and historically), is roughly the study of existence/being, of what exists. It is not a     (2M323)

piece of knowledge. :)     (2M324)

[10:50] Amanda Vizedom: @Robert that is true of *philosophical ontology*. Applied, formal ontology,     (2M325)

as practice or artifact, is a different beast.     (2M326)

[10:51] Alex Shkotin: @Amanda, another way to classify ontology - domain of knowledge is very     (2M327)

important.     (2M328)

[10:51] Matthew West lowered your hand     (2M329)

[10:53] Robert Rovetto: @Amanda Thanks for reiterating the distinction and possibly clarifying the     (2M330)

intended meaning of the statement. I know the distinction, but the phrasing and my reading of the     (2M331)

statement suggested something more general. :) No worries.     (2M332)

[10:53] Amanda Vizedom: @Alex: true, but in this case I was speaking not of the domain of knowledge     (2M333)

  • covered by an ontology* but as "ontology" being a term for two very different, though historically     (2M334)

related, fields of study and practice.     (2M335)

[10:47] Jack Ring: A few years ago a friend spent five years in Cyprus evolving a way for the Greeks     (2M336)

and Turks to pursue mutual ends. This largely evolved an ontology of their mental and emotional     (2M337)

models. Are we thinking of this scope or only regarding IT?     (2M338)

[10:49] Joanne Luciano: Does it make sense to evaluate an ontology outside of a (any) use case? Is     (2M339)

that different from asking "is x big enough?" [big enough for what? does the shoe fit? (which     (2M340)

foot?)] these questions require asking and answering these questions for each use case. And if there     (2M341)

isn't a use case in mind (at the least), then why is the ontology being built?     (2M342)

[10:54] Jack Ring: In one use case we are concerned with automatically composing an ontology with     (2M343)

respect to an intended usage by surveying ontologies and selecting modules that can be harmonized.     (2M344)

The method of composing is now known. Now we need to state the rules for qualifying any candidate     (2M345)

[10:54] Leo Obrst: One issue, e.g., is if you expose the ontology too early to domain experts or     (2M347)

users who do not have sufficient understanding of what ontology is, they will confuse the ontology     (2M348)

with the emerging application that uses it, dig in their heels, and potentially cause the effort to     (2M349)

fail. Representation is not presentation, and you can have many application "presentations" of the     (2M350)

same underlying ontology representation.     (2M351)

[10:53] GaryBergCross: @Anatoly I take this meaning of standard to mean something like "ontology X     (2M352)

is the standard for Hydrology objects."     (2M353)

[10:55] Terry Longstreth: @Anatoly - I agree. I'd suggest you're describing an Ontology as a standard     (2M354)

model of something else     (2M355)

[10:55] Simon Spero: The standard for standards: "Rough Consensus and Running Code". Consensus is     (2M356)

measured by humming.     (2M357)

[10:58] Leo Obrst: Thanks, all: must leave for another meeting.     (2M358)

[10:58] Peter P. Yim: thanks, Leo, bye!     (2M359)

[10:58] Michael Grüninger: Ontology evaluation is closely tied to ontology testing -- ideally,     (2M360)

ontology evaluation criteria should be testable in some way     (2M361)

[10:59] Terry Longstreth: @Todd - Agile still has a pretty well-defined end point: what about an     (2M362)

Ontology that models an evolving natural process?     (2M363)

[10:59] GaryBergCross: Thanks, all: I also must leave for another meeting.     (2M364)

[11:00] Joanne Luciano: @MichaelGruninger -- it's tied to requirements, they define the test     (2M365)

[11:00] Joanne Luciano: @Tom +1 governance     (2M366)

[11:01] Alan Rector: But who is the "user". In many of our scenarios the primary users are either     (2M367)

configuration engineers or software engineers trying to develop software that uses an ontology.     (2M368)

Whether they can understand and use it - e.g. whether it is easy to relate to UML or their OO     (2M369)

designs may be critical for them but of no interest to the end users of the application. In fact if     (2M370)

the ontology is really successful the end users may never know it's there. There was a large     (2M371)

semantic web technologies including ontologies implementation behind the BBC Olympics web site, but     (2M372)

if you were browsing the system, all you knew was that it worked (almost always).     (2M373)

[11:01] Joanne Luciano: Propose SADI services as a registry ( SADI - Semantic Automated Discovery and     (2M374)

[11:01] Simon Spero: ICANN came after the Internet had grown; it took over the role of IANA, which     (2M376)

was basically Jon and Joyce.     (2M377)

[11:01] Michael Grüninger: Question 1: Are there any topics missing in the current tracks?     (2M378)

[11:02] Michael Grüninger: Question 2: Are there any missing tracks?     (2M379)

[11:03] Michael Grüninger: Question 3: Should any of the Tracks be split/merged?     (2M380)

[11:03] Michael Grüninger: If additional topics can fit into an existing Track, then we can let     (2M381)

participants of that Track start their own discussions     (2M382)

[11:04] Tom Tinsley: Establishing quality can lead to certification. This could lead to establishing     (2M383)

an organization to internationally govern ontology development in a similar way ICANN manages the     (2M384)

internet.     (2M385)

[11:03] David Mendes: @Michael: I would suggest mentioning specifically "metrics for evaluation" in     (2M386)

some tracking ...     (2M387)

[11:04] Michael Grüninger: @DavidMendes: "Metrics" is included in Track 1 (slide 7)     (2M388)

[11:04] David Mendes: metrics in ontology, or anywhere else, have to be discussed for something to be     (2M389)

comparable that is fundamental for evaluating.     (2M390)

[11:06] David Mendes: Yes, I missed that. Thank you !     (2M391)

[11:04] Asma Miniaoui: @Michael :I suggest Evaluation Context , Quality is not property of something     (2M392)

but a judgment, so must be relative to some purpose according to a given context     (2M393)

[11:07] Joanne Luciano: Yes, capturing context. Use case provides context. Some metrics are context     (2M394)

free and some context sensitive. What are the outcomes -- think these should be articulated at the     (2M395)

[11:12] Asma Miniaoui: yes, in fact , for each context we have different evaluators,different     (2M397)

evaluation metrics, different goals..etc     (2M398)

[11:13] Amanda Vizedom: +1 @AsmaMiniaoui     (2M399)

[11:07] Todd Schneider: Where are evaluation techniques represented?     (2M400)

[11:07] Joanne Luciano: I hear - max of 5 tracks     (2M401)

[11:07] Joanne Luciano: thank you     (2M402)

[11:08] Steve Ray: Suggest we consider merging tracks 2 and 4     (2M403)

[11:09] Richard Martin: It seems that Track 5 could be subsumed by the other tracks.     (2M404)

[11:09] Joanne Luciano: suggestion -- Track 4 could be folded into 1     (2M405)

[11:09] Todd Schneider: Suggest dropping track 4.     (2M406)

[11:09] Amanda Vizedom: @Steve is that essentially treating application/use case features as input to     (2M407)

requirements identification?     (2M408)

[11:09] David Mendes: Is there anywhere specific directions about Multilingual or     (2M409)

Internationalization problems or issues in evaluation ?     (2M410)

[11:10] Amanda Vizedom: @David, I would treat that a specific case of a cluster use case features     (2M411)

that have particular implications for ontology requirements.     (2M412)

[11:11] David Mendes: TY @Amanda     (2M413)

[11:10] Jack Ring: Apparently my Skype has a BS filter. ;-) I am concerned about the use of the     (2M414)

singular throughout this discussion. There are 7 billion ontologies today and some of these people     (2M415)

create a local, mutual ontology which doesn't interoperate with other local ones. Is this community     (2M416)

presuming to pursue one standard ontology or a standard for producing multiple ontologies or what?     (2M417)

[11:12] Amanda Vizedom: @Jack: I certainly don't think most of us are. The very notion of     (2M418)

understanding the variety of use cases, the variety of ontology requirements that can emerge from     (2M419)

such use cases, and need to evaluate ontologies along the dimensions that matter for the use case --     (2M420)

all of that speaks against the kind of presumption you mention.     (2M421)

[11:14] Alex Shkotin: @JackRing, do you have a reference to "7 billion ontologies"?     (2M422)

[11:15] Michael Grüninger: @JackRing: We are talking about evaluating many different ontologies. Or     (2M423)

do you mean that there should be more emphasis on evaluation of a set of ontologies all at once     (2M424)

(e.g. how well do ontologies play with each other)? If so, I agree, and this can be addressed     (2M425)

somewhere.     (2M426)

[11:13] Fabian Neuhaus: (Summary of what I said earlier) Different ontology evaluation methodologies     (2M427)

are appropriate at different times during the ontology life-cycle. During the development of an     (2M428)

ontology the developers have the need to measure progress and whether the ontology meets the     (2M429)

requirements. After deployment one can evaluate the use of ontology; in particular for ontologies     (2M430)

that are used for annotating texts this essential. A different (potential) phase in an ontology     (2M431)

life-cycle is reuse: people evaluating existing ontologies with the goal to decide which one they     (2M432)

should use (if any).     (2M433)

[11:05] Amanda Vizedom: +1 @Fabian     (2M434)

[11:14] Alan Rector: I'd argue that in many cases, we find that, in collaborative development as in     (2M435)

large medical ontologies/terminologies, different people have different requirements and making     (2M436)

those differences explicit is one key to resolving the resulting disagreements.     (2M437)

[11:14] Joanne Luciano: One question I'd like to see addressed (in some track) is how does one     (2M438)

determine the expressivity and language needed in the application that one is presuming one needs an     (2M439)

ontology developed for? and how can one evaluate whether is is correct before the investment is     (2M440)

[11:15] Terry Longstreth: In any living ontology based upon requirements, there will be a continuing     (2M442)

requirements evolution driving ontology evolution     (2M443)

[11:15] Pavithra Kenjige: I think we should evaluate each phase of life cycle and agree upon them.     (2M444)

Requirements are one phase of the life cycle     (2M445)

[11:15] Joanne Luciano: And how does one make public the requirements that the ontology was designed     (2M446)

[11:15] Amanda Vizedom: IMHO, what we need is (a) better understanding of the relationship between     (2M448)

use case/context features and ontology requirements, and (b) better understanding of how to evaluate     (2M449)

ontologies along particular dimensions that correspond to those requirements.     (2M450)

[11:16] Joanne Luciano: (agree with Amanda's HO)     (2M451)

[11:17] Todd Schneider: Amanda, definitely!     (2M452)

[11:15] Joanne Luciano: The sound went dead...     (2M453)

[11:15] John Bateman: I think we lost the call?     (2M454)

[11:16] Todd Schneider: Peter we've lost audio.     (2M455)

[11:16] Amanda Vizedom: skype says "joinconference is offline"     (2M456)

[11:16] Alex Shkotin: me too.     (2M457)

[11:16] Matthew West: Sorry, my turn to go offline     (2M458)

[11:16] Joanne Luciano: "The moderator has left the conference."     (2M459)

[11:16] Steve Ray: Ah, I thought it was my end...     (2M460)

[11:16] Terry Longstreth: We're waiting for the moderator     (2M462)

[11:17] Amanda Vizedom: Bring Your Own Hold Music...     (2M463)

[11:17] Joanne Luciano: Hmm, now there's an idea that has market potential!     (2M464)

[11:17] Joanne Luciano: select 1 for classical, 2 for folk, 3 for jazz, 4 for wrap, 5 to upload your     (2M465)

own, 6 for talk radio....     (2M466)

[11:17] Michael Grüninger: I'm cutoff, and I am unable to reconnect     (2M467)

[11:17] Todd Schneider: Nice filler music.     (2M468)

[11:17] Steve Ray: Is anybody not using Skype? Do they have audio?     (2M469)

[11:17] Peter P. Yim: looks like there is some problem with the phone bridge network, and a whole bunch     (2M470)

of people have been dropped (including myself) ... please hang on     (2M471)

[11:18] Todd Schneider: Not using Skype; and lost audio.     (2M472)

[11:18] Anatoly Levenchuk: skype connect disappear for me     (2M473)

[11:18] Pavithra Kenjige: We got music .. indicating we are on hold     (2M474)

[11:18] Todd Schneider: So, have we defined the tracks and their subjects?     (2M475)

[11:19] Michael Grüninger: @Todd: There seems to be a rough consensus on the Tracks, although their     (2M476)

contents will still need to be developed by the Champions     (2M477)

[11:20] Steve Ray: I suggest we move forward with these tracks, and if merging or adding is needed,     (2M478)

we can do that (like last year).     (2M479)

[11:18] Michael Grüninger: Ok, let's continue in the chat.     (2M480)

[11:18] Michael Grüninger: Are there any volunteers to be Track Champions?     (2M481)

[11:18] Peter P. Yim: == who is coming to the organizing committee call tomorrow? ... please indicate     (2M482)

(as an rsvp) below - please make sure you go through details at:     (2M483)

of the organizing committee is a fairly serious commitment     (2M485)

[11:19] Todd Schneider: I'll be there.     (2M486)

[11:19] Pavithra Kenjige: I would like to attend     (2M487)

[11:20] Tom Tinsley: I am on.     (2M489)

[11:21] Matthew West: OK I'm being told that joinconference is Offline on Skype.     (2M490)

[11:21] Peter P. Yim: I am back ... calling into the phone number still works ... Phone (US): +1 (206)     (2M491)

402-0100 ... PIN 141184#     (2M492)

[11:23] David Mendes: I can't call the States from here ! I will wait for joinconference to get back     (2M493)

online, it was working very well for me.     (2M494)

[11:24] Alex Shkotin: Sorry, it's too late in Moscow:-) Bye.     (2M495)

[11:21] Peter P. Yim: Please try to call in or stay on the chat     (2M496)

[11:21] Joanne Luciano: @StevenRay No, I'm dialed in from my office landline     (2M497)

[11:23] Michael Grüninger: If anyone knows other people who would make good Track Champions, please     (2M498)

make your suggestions     (2M499)

[11:20] Steve Ray: @Joanne: On Skype?     (2M500)

[11:24] Joanne Luciano: I will consider being on the organizing committee - I think the track     (2M501)

champion role may be too time consuming for me (it was last time, but will discuss and consider     (2M502)

various options) - given I'm doing active research in a generalized framework of methods and metrics     (2M503)

in ontology evaluation, for use and reuse     (2M504)

[11:25] Matthew West: We generally had co-champions last year, and I know I found that very helpful.     (2M505)

[11:24] Peter P. Yim: == if you can planning to join the organizing committee, please post your name     (2M506)

below now     (2M507)

[11:24] Steve Ray: I plan to participate on the organizing committee call tomorrow.     (2M508)

[11:24] Terry Longstreth: I'm happy to participate in the organizing committee     (2M509)

[11:25] Amanda Vizedom: I will be in the call tomorrow.     (2M510)

[11:25] Pavithra Kenjige: I will participate tomorrow     (2M511)

[11:25] Joanne Luciano: what time is it tomorrow?     (2M512)

[11:25] Fabian Neuhaus: I plan to participate tomorrow.     (2M513)

[11:25] Todd Schneider: I'll be there.     (2M514)

[11:25] Joanne Luciano: I plan to participate if I don't have a pre-existing conflict (i.e. one I     (2M515)

can't move or skip)     (2M516)

[11:25] Michael Grüninger: Given the technical difficulties, we will need to finish today's meeting.     (2M517)

If anyone wants to participate in the Organizing Committee, please join tommorrow's meeting.     (2M518)

[11:26] Terry Longstreth: I suggest you put the call for participation on the mailing list.     (2M519)

[11:26] Joanne Luciano: Thanks everyone!     (2M520)

[11:26] Marcela Vegetti: I will be in the call tomorrow. But I consider that the champion role is too     (2M521)

big for me     (2M522)

[11:26] Mike Bennett: I have other meetings at that time.     (2M523)

[11:27] Peter P. Yim: sorry about the technical difficulty ... after collecting names of people who have     (2M524)

signed up for the organizing committee, we will adjourn this meeting. Michale & Matthew will     (2M525)

synthesize the input collected today, and we can tie down the tracks, and who will be co-championing     (2M526)

them at the meeting tomorrow -     (2M527)

[11:27] Matthew West: Time to call time I think. Thank you everyone for your participation today. I     (2M529)

hope to "see" many of you tomorrow.     (2M530)

[11:27] David Mendes: IMHO, I don't think you need me in the Organizing Committee.     (2M531)

[11:28] Matthew West: @David: I'm sure you would be valuable, the question is whether you can make     (2M532)

the commitment.     (2M533)

[11:29] David Mendes: I am here to help should any need arises     (2M534)

[11:28] Marcela Vegetti: Sorry I have to go. Thanks to all     (2M535)

[11:29] Peter P. Yim: Meeting adjourned     (2M536)

[11:29] Peter P. Yim: -- session ended 11:29am PST --     (2M537)

[11:29] Michael Grüninger: OK, everyone -- we will officially conclude today's meeting. Talk to     (2M538)

people at tomorrow's Organizing Committee meeting     (2M539)

[11:29] David Mendes: Thank You All     (2M540)

- end of in-session chat-transcript -     (2M547)

Resources     (2N)

  • To participate:     (2N3)
    • please post further thoughts to the [ ontology-summit ] listserv     (2N3A)
    • all subscribers to the previous summit discussion, and all who responded to today's call will automatically be subscribed to the [ ontology-summit ] listserv     (2N3B)
    • if you are already subscribed, post to <ontology-summit [at]>     (2N3C)
      • all previous subscribers on the list from the past year will be retained. (If you want to be removed, please by sending a blank email to <ontology-summit-leave [at]> from your subscribing email address, or send a note to <> to request that be done for you.)     (2N3C1)
    • (if you are not yet subscribed) you may subscribe yourself to the [ ontology-summit ] listserv, by sending a blank email to <ontology-summit-join [at]> from your subscribing email address, and then follow the instructions you receive back from the mailing list system.     (2N3D)
    • Note that the [ ontology-summit ] listserv will be dedicated to the discourse around this year's summit theme. General ontology-related discussions should be deferred to the [ontolog-forum] mailing list. Those who are not subscribed to that list yet (i.e. not officially registered as members of the Ontolog community) are invited take a look over the Ontolog membership details, and get subscribed accordingly.     (2N3E)

For the record ...     (2N4)

How To Join (while the session is in progress)     (2O)

  • Dial-in:     (2O4D)
    • Phone (US): +1 (206) 402-0100 ... (long distance cost may apply)     (2O4D1)
    • Skype: joinconference (i.e. make a skype call to the contact with skypeID="joinconference") ... (generally free-of-charge, when connecting from your computer)     (2O4D2)
      • when prompted enter Conference ID: 141184#     (2O4D2A)
      • Unfamiliar with how to do this on Skype? ...     (2O4D2B)
        • 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.     (2O4D2B1)
      • Can't find Skype Dial pad? ...     (2O4D2C)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (2O4D2C1)
        • 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,) if the dialpad button is not shown in the call window you need to press the "d" hotkey to enable it. ... (ref.)     (2O4D2C2)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at:     (2O4E)
    • view-only password: "ontolog"     (2O4E1)
    • 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.     (2O4E2)
    • 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.     (2O4E3)
    • 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").     (2O4F1)
    • 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.     (2O4F2)
    • 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!     (2O4F3)
  • Discussions and Q & A:     (2O4G)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (2O4G1)
    • 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.)     (2O4G2)
    • 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.)     (2O4G3)
    • 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.)     (2O4G4)
  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (2O4I)
  • 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.     (2O4K)

Attendees     (2P)

This page has been migrated from the OntologWiki - Click here for original page     (2P4)