From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2014 session-13: Communique Draft Review - Thu 2014-04-10     (1)

  • Summit Theme: OntologySummit2014: "Big Data and Semantic Web Meet Applied Ontology"     (1A)

Reference:     (1D)

Abstract     (1L)

OntologySummit2014 Session-13: "OntologySummit2014_Communique: Draft Review"     (1L1)

This is our 9th Ontology Summit, a joint initiative by Ontolog, NIST, NCOR, NCBO, IAOA & NCO_NITRD with the support of our co-sponsors.     (1L2)

Since the beginnings of the Semantic Web, ontologies have played key roles in the design and deployment of new semantic technologies. Yet over the years, the level of collaboration between the Semantic Web and Applied Ontology communities has been much less than expected. Within Big Data applications, ontologies appear to have had little impact.     (1L3)

This year's Ontology Summit is an opportunity for building bridges between the Semantic Web, Linked Data, Big Data, and Applied Ontology communities. On the one hand, the Semantic Web, Linked Data, and Big Data communities can bring a wide array of real problems (such as performance and scalability challenges and the variety problem in Big Data) and technologies (automated reasoning tools) that can make use of ontologies. On the other hand, the Applied Ontology community can bring a large body of common reusable content (ontologies) and ontological analysis techniques. Identifying and overcoming ontology engineering bottlenecks is critical for all communities.     (1L4)

Ontology Summit 2014 will pose and address the primary challenges in these areas of interaction among the different communities. The Summit activities will bring together insights and methods from these different communities, synthesize new insights, and disseminate knowledge across field boundaries.     (1L5)

At the Launch Event on 16 Jan 2014, the organizing team has provided an overview of the program, and how we will be framing the discourse - namely, to pursue that along four different content tracks that address different aspects of the issue at hand.     (1L6)

In today's session, our Lead Editors will be presenting, for the first time, a working draft of the OntologySummit2014_Communique for review and discussion. We will not be wordsmithing yet (that will be part of next week's agenda), but will be doing a higher level review, to make sure we have included everything we want to see in the Communique, and will attempt to expose and close all gaps.     (1L7)

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

Agenda     (1M)

OntologySummit2014 - Panel Session-13     (1M1)

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

Proceedings     (1N)

Please refer to the above     (1N1)

IM Chat Transcript captured during the session    (1N2)

see raw transcript here.     (1N2A)

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

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

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

Chat transcript from room: summit_20140410     (1N2E)

2014-04-10 GMT-08:00 [PDT]     (1N2F)

[9:20] Peter P. Yim: Welcome to the     (1N2G)

Ontology Summit 2014 session-13: Communique Draft Review - Thu 2014-04-10     (1N2H)

Summit Theme: Ontology Summit 2014: "Big Data and Semantic Web Meet Applied Ontology"     (1N2I)

Session Topic: Session Topic: OntologySummit2014_Communique: Draft Review and Discussion     (1N2J)

Session Co-chairs & Communique Co-Lead Editors: Professor Michael Grüninger and Dr. Leo Obrst     (1N2K)

One of the objectives will be to develop a clearer picture of the ideas that we want to cover in this section.     (1N2T)

Logistics:     (1N2X)

  • (if you haven't already done so) please click on "settings" (top center) and     (1N2AB)

morph from "anonymous" to your RealName; also please enable "Show timestamps" while there.     (1N2AC)

(i.e. even if it says it is "offline," you should still be able to connect to it.)     (1N2AG)

VoIP line, etc.) either your phone, skype-out or google-voice and call the US dial-in number: +1 (206) 402-0100     (1N2AI)

... when prompted enter Conference ID: 141184#     (1N2AJ)

  • when posting in this Chat-room, kindly observe the following ...     (1N2AN)
    • whenever a name is used, please use the full WikiWord name format (every time you don't, some volunteer will have to make an edit afterwards)     (1N2AO1)
    • always provide context (like: "[ref. JaneDoe's slide#12], I think the point about context is great" ... rather than "that's great!"     (1N2AP1)

as the latter would mean very little in the archives.)     (1N2AQ)

the timestamp (in PST) of his/her post that you are responding to (e.g. "@JaneDoe [11:09] - I agree, but, ...")     (1N2AS)

    • use fully qualified url's (include http:// ) without symbols (like punctuations or parentheses, etc.) right before of after that URL     (1N2AT1)

Proceedings     (1N2AZ)

1. Overview of Communique rough draft     (1N2AAB)

2. Discuss Bottlenecks and Barriers section     (1N2AAC)

3. Identify any missing material or ideas that need to be emphasized     (1N2AAD)

4. Discuss recommendations     (1N2AAE)

5. Action Items     (1N2AAF)

[9:31] AmandaVizedom1 morphed into Amanda Vizedom     (1N2AAH)

[9:33] anonymous morphed into Lamar Henderson     (1N2AAI)

[9:36] Peter P. Yim: == Michael Grüninger starts session on behalf of the co-chairs ... see prepared     (1N2AAJ)

[9:40] anonymous morphed into Les Morgan     (1N2AAL)

[9:40] anonymous morphed into Megan Katsumi     (1N2AAM)

[9:43] ... Anne Thessen: Sorry I'm late     (1N2AAN)

[10:04] Michael Grüninger: the draft on google-doc is at:     (1N2AAO)

it is configured so anyone who has the link can view and comment     (1N2AAQ)

[9:45] Amanda Vizedom: If you want leave a comment on the Google Doc, it is helpful if you can make     (1N2AAR)

it non-anonymous so that editors can come back to you for clarification. To become non-anonymous: At     (1N2AAS)

top right of page, to left of "Comments" button, there is a little chat icon. Click that (it will     (1N2AAT)

say something like "join chat" on hover-over). It will pop open a chat window, which you can     (1N2AAU)

minimize. The main consequences will be that any comment you leave now will be attributed to you,     (1N2AAV)

and also that other participants will see your name & icon (instead of anonymous) in the pull-down     (1N2AAW)

list of viewers.     (1N2AAX)

[9:58] Steve Ray: @Peter, @Amanda: A logistics question. I tried to add a comment, but the pop-up     (1N2AAY)

says I don't have permission to add comments. Any ideas how to change that?     (1N2AAZ)

[9:59] Amanda Vizedom: @Steve: Michael said he'd changed it to "Anyone with the link can comment," so     (1N2AAAA)

I don't know why it would do that.     (1N2AAAB)

[10:12] Steve Ray: Mystery solved on the comments addition. I was also logged in on another tab with     (1N2AAAC)

a different account. Once I logged out of that account, it worked.     (1N2AAAD)

[10:14] Alex Shkotin: @SteveRay, I do not have different account but "You do not have permission to     (1N2AAAE)

add comments." :-( ... [(subsequent comment) you might want make sure you have already signed into     (1N2AAAF)

the google work environment with your gmail (or gmail associated) account first. =ppy]     (1N2AAAG)

[9:34] Ed Bernot: Please note the typo "reasoner on a small ontologies" in section 1.     (1N2AAAH)

[9:45] Todd Schneider: Some description of 'reuse' needs to be included.     (1N2AAAI)

[9:45] Andrea Westerinen: Track A tried to define what reuse is... Should that discussion be included?     (1N2AAAJ)

[9:45] Andrea Westerinen: @ToddSchneider [9:45] Yes, that is my question as well.     (1N2AAAK)

[9:46] Todd Schneider: Well, at least the different ways ontologies could be reused.     (1N2AAAL)

[9:47] Todd Schneider: As example, an ontology may not be able to be reused 'directly', but the fact     (1N2AAAM)

the certain notions are represented or the way they're represented.     (1N2AAAN)

[9:48] Steve Ray: I think Section 2.1.2 should include the notion of "acceptance by the community".     (1N2AAAO)

That is, "I found this random ontology on the web - how does it rate in the eyes of the ontology community?"     (1N2AAAP)

[9:49] ... anonymous morphed into Bobbin Teegarden     (1N2AAAQ)

[9:49] Andrea Westerinen: Also, a lot of time was spent on defining the conditions for reuse and best     (1N2AAAR)

practices. The current best practices is a bit behind the synthesis page. I think that Mike Bennett     (1N2AAAS)

updated recently (Wednesday?).     (1N2AAAT)

[10:02] Mike Bennett: Re @Andrea [0:49] I added two sentences in Wednesday. Will review.     (1N2AAAU)

[9:51] Peter P. Yim: == Q & A and Open Discussion ...     (1N2AAAV)

[9:53] ... anonymous morphed into Lamar Henderson     (1N2AAAW)

[9:52] Peter P. Yim: @ALL contributors - e.g. re. @AndreaWesterinen [9:49] ... it would be great if you     (1N2AAAX)

have made a major update to the wiki, to draw people's attention to it on the [ontology-summit] list     (1N2AAAY)

to notify everyone (especially the editors)     (1N2AAAZ)

[9:55] Peter P. Yim: Further to the Peter P. Yim [9:52] comment ... @ALL contributors, the best place to get     (1N2AAAAA)

the editors attention would probably be making a comment on the google-doc working draft of the     (1N2AAAAB)

Communique ... please do that     (1N2AAAAC)

[9:57] Christoph Lange: Re @PeterYim [9:55] one can also force comments to be sent as emails to some     (1N2AAAAD)

people by including in the comment     (1N2AAAAE)

[9:54] Amanda Vizedom: IMHO, one of the barriers to reuse is the state of tools (lack of mature (or     (1N2AAAAF)

any) tools to facilitate use of the ontology features and processes that create reusability and/or     (1N2AAAAG)

support evaluation for reuse.     (1N2AAAAH)

[9:50] Henson Graves: On the face of it, it seems that section 3 (use) should precede section 2     (1N2AAAAI)

[9:54] Steve Ray: @Henson: It is true that when Michael introduced the sections, he started     (1N2AAAAK)

with "What ontologies are out there" (Section 3), and then "How to use them" (Section 2).     (1N2AAAAL)

I can see either ordering working.     (1N2AAAAM)

[9:56] Henson Graves: I like the "what are out there, how to use them,and potential places where they     (1N2AAAAN)

could be used to come before the more detailed resuse, tools, etc     (1N2AAAAO)

[10:00] Mike Bennett: I'm having connection issues, but just to say that re-use has been considered     (1N2AAAAP)

more broadly than just getting an ontology and using it. We need to review and make sure that's     (1N2AAAAQ)

clear, as it certianly was to us     (1N2AAAAR)

[10:00] Matthew West: [I found I did not have permission to add comments (... subsequently fixed)] so     (1N2AAAAS)

just to say that when you do decide to create yet another ontology, that you are adding to the list     (1N2AAAAT)

of ontologies others may need to integrate with, adding to the work of those that come after you,     (1N2AAAAU)

even if it reduces work for you.     (1N2AAAAV)

[10:00] Mike Bennett: We included re-use by inspiration (ref. ToddSchneider's verbal comment) in the     (1N2AAAAW)

[10:00] Terry Longstreth: Doesn't reuse imply usage beyond the required applicability of the ontology?     (1N2AAAAY)

[10:01] Todd Schneider: Terry, yes.     (1N2AAAAZ)

[10:01] Mike Bennett: @Terry certainly. That's a major factor since the requirements for a given use     (1N2AAAAAA)

case are narrower than being able to re-use it elsewhere.     (1N2AAAAAB)

[10:05] Andrea Westerinen: @MikeBennett [10:01] I will include in comments and Mike indicated that he     (1N2AAAAAC)

would pull them.     (1N2AAAAAD)

[10:01] Ram D. Sriram: Todd Schneider brought up an important issue on the semantics of Reuse     (1N2AAAAAE)

[10:05] Terry Longstreth: Then, perhaps the essence of reuse is the unanticipated application of an     (1N2AAAAAF)

ontology in an unexpected way or to an unforeseen purpose. For example, using a formal (OWL, CL ...)     (1N2AAAAAG)

ontology to instruct a programming staff.     (1N2AAAAAH)

[10:15] Andrea Westerinen: @TerryLongstreth [10:05] Unexpected use MAY result from reuse, but does     (1N2AAAAAI)

not have to. Reusing an event ODP would not be unexpected.     (1N2AAAAAJ)

[10:22] Terry Longstreth: I was going to say that 'Use' specifies an intended purpose -that satisfies     (1N2AAAAAK)

some requirement(s)- while reuse suggests anything beyond requirements. The conundrum is how to deal     (1N2AAAAAL)

with the requirement that "X shall be reusable", but that's equivalent to the old systems     (1N2AAAAAM)

engineering shibboleth that a product "shall be user friendly."     (1N2AAAAAN)

[10:22] Andrea Westerinen: @TerryLongstreth Can you look at the reuse definition on Track A's     (1N2AAAAAO)

synthesis page? The first 2 paragraphs of the Synthesis deal with the definition. And, I just     (1N2AAAAAP)

updated it to reflect the conversation in this call.     (1N2AAAAAQ)

[10:23] Terry Longstreth: @Andrea - I'll look at it     (1N2AAAAAR)

[10:05] Ram D. Sriram: I think the recommendations section should probably say something useful that the     (1N2AAAAAS)

reader can take away with. We should provide some answers -- based on the presentations in the     (1N2AAAAAT)

tracks -- to the questions posed in this section.     (1N2AAAAAU)

[10:07] ... Ram D. Sriram: Need to go out for 30mins. Will be back at 1:30pm     (1N2AAAAAV)

[10:09] Henson Graves: agree with 3.1 first     (1N2AAAAAW)

[10:10] Christoph Lange: Suggestion was: put 3.1 "What Ontologies are Needed?" (or, in other words     (1N2AAAAAX)

why ontologies?") before "reuse     (1N2AAAAAY)

[10:12] Christoph Lange: Regarding "what did section 3 miss from the Track B synthesis": I forgot     (1N2AAAAAZ)

to _say_ it, but I scattered a few more such comments over the document. Over sections _other_ than 3.     (1N2AAAAAAA)

[10:14] Mike Bennett: One issue with tools for me (relating to re-use and beyond) is the abscence of     (1N2AAAAAAB)

tools at the level of a "system" design of a group of ontologies and the relationships (imports)     (1N2AAAAAAC)

[10:17] Christoph Lange: @TorstenHahmann @MichaelGruninger I'm currently looking up whether/where     (1N2AAAAAAE)

Till Mossakowski mentioned visualization in Track B     (1N2AAAAAAF)

[10:18] Christoph Lange: @ChristophLange [10:17] See Till Mossakowski slide 17 and 18 on visualizing     (1N2AAAAAAG)

ontology module imports and other links     (1N2AAAAAAH)

[10:21] Torsten Hahmann: visualization is mentioned quite frequently in the track B summary:     (1N2AAAAAAJ)

... Partiuclar examples mentioned are OntoIOp and the Open Semantic Framework     (1N2AAAAAAL)

[10:25] Henson Graves: second Michael's comment on need to discuss reuse and other issues in context of big data.     (1N2AAAAAAM)

[10:26] Andrea Westerinen: Michel Dumontier talked about reuse and big data.     (1N2AAAAAAN)

[10:26] Andrea Westerinen: Michel's talk was during Track A's second session.     (1N2AAAAAAO)

[10:26] Mike Bennett: [I think my sound must be one way at the moment. Anyway,] I think on re-use     (1N2AAAAAAP)

there are issue around what the ontology was created for versus what it's used for, which I think     (1N2AAAAAAQ)

goes beyond simply whether the creator thought about Big Data and Linked Data contexts. For example,     (1N2AAAAAAR)

the levels of abstraction of the concepts may have been very specific to the creator's use case, and     (1N2AAAAAAS)

it's not a criticism to say that they won't have had the budget / justification to think about the     (1N2AAAAAAT)

broader meanings of the concepts in their ontologies - i.e. no reason they should think about the     (1N2AAAAAAU)

re-usability of their ontology unless it's intended as an industry standard.     (1N2AAAAAAV)

[10:28] Amanda Vizedom: FYI, I have been putting most of my comments in comments on the Google doc,     (1N2AAAAAAW)

rather than here.     (1N2AAAAAAX)

[10:28] Andrea Westerinen: @Steve Track A recommends examining the content to make sure that they     (1N2AAAAAAY)

address their competency questions.     (1N2AAAAAAZ)

[10:29] ... Mike Bennett: @Amanda my bandwidth today is too narrow for me to contribute to the Google area.     (1N2AAAAAAAA)

[10:30] Andrea Westerinen: @Amanda [10:28] I will add later when I am not multi-tasking on the call     (1N2AAAAAAAB)

and chat. :-)     (1N2AAAAAAAC)

[10:30] Mike Bennett: We have barely scratched the surface in the area of re-use. We need to make     (1N2AAAAAAAD)

sure the Communique catalogues the questions that are out there.     (1N2AAAAAAAE)

[10:31] Terry Longstreth: @Andrea - from Synthesis Para 1 "The reuse may directly align with the     (1N2AAAAAAAF)

original intentions of the developers" -- I'd maintain that direct alignment should fall within the     (1N2AAAAAAAG)

intended use requirements. Finding the discontinuity between intended use and unintended reuse is     (1N2AAAAAAAH)

probably in NP.     (1N2AAAAAAAI)

[10:35] Andrea Westerinen: @TerryLongstreth [10:31] But reuse for the intended design is still reuse     (1N2AAAAAAAJ)

... and builds trust in the original content.     (1N2AAAAAAAK)

[10:35] Andrea Westerinen: @TerryLongstreth [10:31] Just like reuse of software.     (1N2AAAAAAAL)

[10:35] Peter P. Yim: I still think we need to be more convincing to the Big data community, especially     (1N2AAAAAAAM)

those in data analytics which makes up the bulk of commercial applications now (than the one     (1N2AAAAAAAN)

paragraph under 3.1) ... Ontology can give them much more than that. ... [I looked through, say the     (1N2AAAAAAAO)

attendees in today's session, and I can't even be sure if we have any representation from that group     (1N2AAAAAAAP)

here ... which means we *really* have a gap to close (starting from grabbing their attention and     (1N2AAAAAAAQ)

getting them interested).]     (1N2AAAAAAAR)

[10:34] Todd Schneider: For the challenge problems, what about the challenge of building/designing     (1N2AAAAAAAS)

ontologies for reuse?     (1N2AAAAAAAT)

[10:35] Mike Bennett: @Todd but does anyone want to design ontologies for re-use? Other than industry     (1N2AAAAAAAU)

standards ontologies, what cost justification is there?     (1N2AAAAAAAV)

[10:36] Andrea Westerinen: @Mike [10:35] Even ontologies defined for standards are usually specific-to-purpose.     (1N2AAAAAAAW)

[10:41] Mike Bennett: @Andrea +1 and sometimes too much so. (my detailed response here got eaten)     (1N2AAAAAAAX)

[10:36] Sunday Ojo: Reusability is constrained by semantic compatibility of the intended use     (1N2AAAAAAAY)

application domain and the unintended reuse application domain     (1N2AAAAAAAZ)

[10:37] Andrea Westerinen: @SundayOjo [10:36] +1. Track A's synthesis tries to say this. If it can be     (1N2AAAAAAAAA)

made better, please let us know.     (1N2AAAAAAAAB)

[10:39] Bart Gajderowicz: Regarding finding ontologies on crowd sourced websites like stackoverflow,     (1N2AAAAAAAAC)

the purpose is also for experimentation, not just design or implementation. Analogous to software     (1N2AAAAAAAAD)

engineering, ontologies fall somewhere between software and data. To ensure a copy/pasted algorithm     (1N2AAAAAAAAE)

does what you want, you run it against some input values and compare the output to what was     (1N2AAAAAAAAF)

expected. With data you run queries in a more structured environment (think SQL). I think ontologies     (1N2AAAAAAAAG)

work in the same way. We currently have a set of tools that we can use to quickly verify an ontology     (1N2AAAAAAAAH)

against some set of queries. The gap exists in helping engineers identify and create the queries     (1N2AAAAAAAAI)

they need to ensure an ontology is right for them.     (1N2AAAAAAAAJ)

[10:41] Bart Gajderowicz: The main benefit of this is that it allows engineers to experiment before     (1N2AAAAAAAAK)

committing to a more in depth analysis and verification.     (1N2AAAAAAAAL)

[10:46] Peter P. Yim: === Michael Grüninger: soliciting input - if you have one "recommendation" what     (1N2AAAAAAAAM)

would it be - please enter into chat or verbally say it     (1N2AAAAAAAAN)

[10:46] Andrea Westerinen: Standard, searchable metadata     (1N2AAAAAAAAO)

[10:46] Todd Schneider: Documentation of ontologies: Assumptions, requirements, scope, intent, ....     (1N2AAAAAAAAP)

[10:47] Mike Bennett: Recommendations: Metadata: include details of intended use case of ontology.     (1N2AAAAAAAAQ)

[10:48] Mike Bennett: Recommendation: Tooling: model driven, top down tooling with TBox and ABox     (1N2AAAAAAAAR)

level visualisation, need to exist.     (1N2AAAAAAAAS)

[10:48] Torsten Hahmann: my #1 recommendation: tools all the way down, including for designing,     (1N2AAAAAAAAT)

publishing, finding, understanding, visualizing, verifying, maintaining, translating, integrating     (1N2AAAAAAAAU)

ontologies on the web     (1N2AAAAAAAAV)

[10:50] Bart Gajderowicz: Adding to @TorstenHahmann's point regarding tools, tools for     (1N2AAAAAAAAW)

experimentation with ontologies on the web, to promote reuse.     (1N2AAAAAAAAX)

[10:47] Steve Ray: Suggestion for recommendation: You don't need to jump in the deep end of the pool     (1N2AAAAAAAAY)

to use ontologies. "A little semantics goes a long way" Try it.     (1N2AAAAAAAAZ)

[10:49] Christoph Lange: @SteveRay [10:47] I think somewhere in the Track C (?) synthesis (from     (1N2AAAAAAAAAA)

OscarCorcho's talk IIRC) I saw a reference to the importance of noting down a commonly agreed-upon     (1N2AAAAAAAAAB)

vocabulary in whatever tool, even Excel, and that capturing such information is more important than     (1N2AAAAAAAAAC)

first discussing what ontology engineering methodology to use     (1N2AAAAAAAAAD)

[10:50] Steve Ray: @Christoph: Agreed.     (1N2AAAAAAAAAE)

[10:50] Peter P. Yim: +1 to earlier discussed recommendation (verbal: Vizedom-Gruninger-Yim) that there     (1N2AAAAAAAAAF)

needs to have better communication/dialog/collaboration at the community level     (1N2AAAAAAAAAG)

[10:51] Peter P. Yim: @ALL: Please mark your calendars and reserve this same time for the next Thursday,     (1N2AAAAAAAAAH)

when we will, hopefully, be finalizing the OntologySummit2014_Communique, after the editors have     (1N2AAAAAAAAAI)

incorporated all the input from this session into that document - ref. developing details at:     (1N2AAAAAAAAAJ)

[10:51] Ed Bernot: Thanks all. Good session!     (1N2AAAAAAAAAM)

[10:52] Peter P. Yim: @ALL: as announced by our Symposium co-chairs, Dr. Ram Sriram & Professor Tim Finin     (1N2AAAAAAAAAN)

our Apr 28~29 Symposium (at NSF in Greater Washington DC) is now open for registration. Please     (1N2AAAAAAAAAO)

register yourself ASAP, as capacity is limited - see OntologySummit2014_Symposium details at:     (1N2AAAAAAAAAP)

NOW, if you haven't already! - see:     (1N2AAAAAAAAAR)

[10:52] Peter P. Yim: -- session ended: 10:49am PDT --     (1N2AAAAAAAAAT)

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

Additional Resources     (1O)

For the record ...     (1O7)

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

  • Dial-in:     (1P4D)
    • Phone (US): +1 (206) 402-0100 ... when prompted enter Conference ID: 141184# ... (long distance cost may apply)     (1P4D1)
    • Skype: joinconference (i.e. make a skype call to the contact with skypeID="joinconference") ... (generally free-of-charge, when connecting from your computer ... ref.)     (1P4D2)
      • when prompted enter Conference ID: 141184#     (1P4D2A)
      • Unfamiliar with how to do this on Skype? ...     (1P4D2B)
        • 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.     (1P4D2B1)
        • you may connect to (the skypeID) "joinconference" whether or not it indicates that it is online (i.e. even if it says it is "offline," you should still be able to connect to it.)     (1P4D2B2)
      • Can't find Skype Dial pad? ...     (1P4D2C)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1P4D2C1)
        • 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.)     (1P4D2C2)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at: ... view-only password: "ontolog"     (1P4E)
    • 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.     (1P4E1)
    • 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.     (1P4E2)
    • 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").     (1P4F1)
    • 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.     (1P4F2)
    • thanks to the folks, one can now use a jabber/xmpp client (e.g. Digsby or Adium) to join this chatroom. Just add the room as a buddy - (in our case here) ... Handy for mobile devices!     (1P4F3)
  • Discussions and Q & A:     (1P4G)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1P4G1)
    • 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.)     (1P4G2)
    • 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.)     (1P4G3)
    • 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.)     (1P4G4)
  • RSVP to with your affiliation, ... or simply just by adding yourself to the "Expected Attendees" list below (if you are already a member of the community.)     (1P4I)
  • 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.     (1P4K)

Attendees     (1Q)

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