From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2011: Panel Session-9 - All Hands: "Synthesis and Reports" - Thu 2011_03_31     (1)

Summit Theme: OntologySummit2011: Making the Case for Ontology     (1A)

Session Title: All Hands: Synthesis and Reports     (1B)

Session Co-chairs: Dr. Steve Ray & Dr. NicolaGuarino     (1C)

Panelists: Summit Co-chairs, Track Co-champions and Communique Co-Lead Editors (* = presenting today)     (1D)

Abstract     (1M)

OntologySummit2011 Theme: "Making the Case for Ontology"     (1M1)

This is our 6th Ontology Summit, a joint initiative by NIST, Ontolog, NCOR, NCBO, IAOA & NCO_NITRD. The theme adopted for this Ontology Summit is: "Making the Case for Ontology."     (1M3)

This year's Ontology Summit seeks to address the need to provide concrete evidence of successful deployment of ontologies by examining several application domains for such examples, and in better articulating where different "strengths" of ontological representation are best applied. To support that, the summit also aims to classify the categories of applications where ontology has been, and could be, successfully applied; to identify distinct types of metrics that might be used in evaluating the return on investment in an ontology application (cost, capability, performance, etc.); to lay out some strategies for articulating a case for ontological applications; and to identify remaining challenges and roadblocks to a wider deployment of such applications that represent promising application areas and research challenges for the future. The findings of the summit will be documented in the form of a communiqu�� intended for public consumption.     (1M4)

In our "All Hands" session today we will be pulling things together. The general co-chairs, all track champions and the communique lead editors will be reporting their respective synthesis of the discourse and work that has transpired to date.     (1M5)

See developing details on this Summit series of events at: OntologySummit2011 (home page for this summit)     (1M6)

Agenda     (1N)

Ontology Summit 2011 - Panel Session-9     (1N1)

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

Proceedings     (1O)

Please refer to the above     (1O1)

IM Chat Transcript captured during the session    (1O2)

see raw transcript here.     (1O2A)

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

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

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

Peter P. Yim: Welcome to the ...     (1O2E)

Ontology Summit 2011: Panel Session-9 - All Hands: "Synthesis and Reports" - Thu 2011_03_31     (1O2F)

Summit Theme: Ontology Summit 2011: Making the Case for Ontology     (1O2G)

Session Title: All Hands: Synthesis and Reports     (1O2H)

Session Co-chairs: Dr. Steve Ray & Dr. Nicola Guarino     (1O2I)

Panelists: Summit Co-chairs, Track Co-champions and Communique Co-Lead Editors (* = presenting today)     (1O2J)

Please refer to details on the session page     (1O2R)

anonymous morphed into Brian Haugh     (1O2T)

anonymous morphed into Matthew West     (1O2U)

Rex Brooks: I'm stil getting "incorrect conference id" I use Vonage and this is the first time this     (1O2W)

has happened. ... I even rebooted the device. But no change.     (1O2X)

Mike Bennett: @Rex w some phones, have to hold down keys for 1 sec each.     (1O2Y)

John Bateman: I got the incorrect conference id a couple of times, then it worked     (1O2Z)

Rex Brooks: Finally got through!     (1O2AA)

Peter P. Yim: @RexBrooks, Mike Bennett, John Bateman, Michael Grüninger et al. - the conference bridge is a     (1O2AB)

bit tricky ... you almost has to space out the keystrokes evenly (especially with the # sign at the     (1O2AC)

end) to have it work well - see:     (1O2AD)

Mike Bennett: OK, I'm going to have to redial in     (1O2AF)

Michael Grüninger: I'm online, but I cannot unmute     (1O2AH)

Peter P. Yim: @MichaelGruninger - let me unmute you, please try your voice when you have a chance     (1O2AI)

anonymous morphed into David Leal     (1O2AJ)

Steve Ray: Standard cheat sheet: *2 to mute, *3 to unmute     (1O2AK)

Peter P. Yim: Michael Grüninger: additionally, will also incorporate the ontology classifications that OMV     (1O2AL)

has provided     (1O2AM)

Nicola Guarino: Anyway, I'll state my question on the chat: my problem is related to the very name     (1O2AN)

"ontology application framework"     (1O2AO)

Peter P. Yim: discussion below is in reference to a possible change of the Track-1 label to disambiguate     (1O2AP)

the possibility that the audience may misinterpret us (as in the case of Stefano Bertolo, who thought     (1O2AQ)

we were trying to find out if something like that would be a good candidate for research funding)     (1O2AR)

Todd Schneider: @Nicola, the Ontology Spplication Framework (OAF) may be at too low a level for     (1O2AS)

stakeholders/decision makers.     (1O2AT)

Michael Grüninger: Would "Taxonomy of Ontology Applications" be better     (1O2AU)

John Bateman: but taxonomy is bad!     (1O2AV)

Amanda Vizedom: I think "taxonomy" makes certain commitments about the structure/relationship of the     (1O2AW)

feature, and should be avoided     (1O2AX)

Nicola Guarino: I agree it is not a taxonomy     (1O2AY)

Simon Spero: "What Can Ontologies Do For You?"     (1O2AZ)

John F. Sowa: How about a very short title: Applications.     (1O2AAA)

Todd Schneider: John, simple is hard.     (1O2AAB)

John F. Sowa: The word 'ontology' can be deleted, because that's the overall title.     (1O2AAC)

John F. Sowa: The word 'usage' can be deleted, because every application is used.     (1O2AAD)

John F. Sowa: When you delete all the problematical words, the only one left is 'application'.     (1O2AAE)

Tim Wilson: Is that a directive from the Department of Redundancy Department?     (1O2AAF)

Rex Brooks: I think that Ontology USE Framework captures it more succinctly.     (1O2AAG)

Todd Schneider: Michael, the 'application' level may still be too low level, at least for an     (1O2AAJ)

elevator' pitch.     (1O2AAK)

Nicola Guarino: Ontology applications comparison framework?     (1O2AAL)

Michael Riben: Is the group familiar with the caBIG's effort to develop a similar ontology app     (1O2AAM)

framework which they call the Ontology "representation":     (1O2AAN)

Simon Spero: Applications, or Problems?     (1O2AAP)

Amanda Vizedom: Using the language of the Wiki page: Ontology Applications Description Framework     (1O2AAQ)

Michael Uschold: ON ambiguity of the term "ontology application framework" I agree that application     (1O2AAR)

is ambiguous here. How about ontology deployment framework?     (1O2AAS)

Nicola Guarino: @MichaelUschold: +1     (1O2AAT)

Christopher Spottiswoode: Ontology Application Typology?     (1O2AAU)

Simon Spero: "What kind of problems can ontologies solve?"     (1O2AAV)

Tim Wilson: There appears to be little consideration for the use of ontology to augment search,     (1O2AAW)

particularly in the enterprise.     (1O2AAX)

Mike Bennett: Application has 2 meanings     (1O2AAY)

Mike Bennett: Crux of the problem is "Application" as a kind of program v. Application as "how     (1O2AAZ)

something is applied"     (1O2AAAA)

Rex Brooks: Perhaps Ontology Usage Framework?     (1O2AAAC)

Rex Brooks: We're capturing the kinds of uses to which ontology can be put.     (1O2AAAE)

Matthew West: Most of the ambiguity comes from missing prepositions. Framework for the Application of     (1O2AAAF)

Ontologies would (for example) get over that.     (1O2AAAG)

John F. Sowa: Long titles require more explanation than they clarify.     (1O2AAAI)

Amanda Vizedom: "Framework for Understanding Ontology Applications?"     (1O2AAAJ)

Michael Riben: is the purpose for "discovery" in order to know if the person can apply it to their     (1O2AAAK)

Nicola Guarino: Let's delegate to the champions to choose the final title on the basis of the input     (1O2AAAN)

Peter P. Yim: I agree with Nicola ... let's defer to the Track-1 champions     (1O2AAAP)

Amanda Vizedom: @NicolaGuarino: +1 ... and it's then most useful for the rest of us to comment/throw     (1O2AAAQ)

out idea in this chat for them to consider later.     (1O2AAAR)

Simon Spero: (past half hour. Now afraid)     (1O2AAAS)

Simon Spero: [Changed Mikes - Now on track 2 - Use Cases]     (1O2AAAT)

Michael Riben: I think a good healthcare/public health example would be to look at Parsa Mirhaji's     (1O2AAAU)

Sapphire system for the CDC that performs surveillance in the Houston area...see     (1O2AAAV)

Michael Grüninger: Should we think of the Ontology Application Framework as really being "Ontology     (1O2AAAX)

Use Case Metadata"? The idea is that all of the dimensions provide the terminology for describing a     (1O2AAAY)

use case from a technical and (eventually) business perspective.     (1O2AAAZ)

Steve Ray: I think using the word "metadata" is just going to confuse things.     (1O2AAAAA)

Michael Uschold: In discussing benefits of an ontology application, it is critically important to     (1O2AAAAB)

link back to how the ontology makes that possible. Saying 'customer retention' gets people's     (1O2AAAAC)

attention, but you need to explain how the ontology helped to do this.     (1O2AAAAD)

Amanda Vizedom: @MikeBennett: +1 for adding the dimension of What's Modeled. Not only do people     (1O2AAAAE)

differ on this, but a lack of understanding of that difference has caused noticeable confusion and     (1O2AAAAF)

disagreement on list during this summit. It's surely a dimension of difference that affects best     (1O2AAAAG)

practices and measures of quality!     (1O2AAAAH)

Simon Spero: Mike Bennett: were the metrics that you hadn't heard of internal to the use case     (1O2AAAAJ)

Mike Bennett: @Simon yes, it was some CRM acronym     (1O2AAAAL)

Mike Bennett: So, what does AHT stand for? (in CRM / call center context)?     (1O2AAAAM)

Mike Bennett: @Simon - AHT was my unexplained metric from CRM case study, as now noted in Track 3.     (1O2AAAAN)

Simon Spero: @MikeBennett: Either Average Hold Time or Average Handling Time     (1O2AAAAO)

Mike Bennett: @Simon, thanks. Not my guess, so worth defining (terminology!).     (1O2AAAAQ)

Steve Ray: @MikeBennett: I want to ensure we are going to have pointers to as many actual cases as     (1O2AAAAR)

possible. Is that your intention?     (1O2AAAAS)

Mike Bennett: @MichaelUschold @SteveRay yes, I need to take the assertions in these slides and link     (1O2AAAAT)

to the relevant case study. On the Wiki.     (1O2AAAAU)

Tim Wilson: I was hoping to stay on the call for Matthew and Peter's presentation, however I must get     (1O2AAAAV)

back to work. I will be presenting to my superiors next week for the creation of a knowledge     (1O2AAAAW)

initiative using ontology.     (1O2AAAAX)

Tim Wilson: This summit has been invaluable to me in that effort.     (1O2AAAAY)

Rex Brooks: It just dawned on me that one area where we haven't seen specific Use-Cases is internal     (1O2AAAAZ)

corporate governance and management both IT Management and Business Intelligence Management.     (1O2AAAAAA)

Peter P. Yim: @MichaelRiben - thanks for joining, and for the contribution     (1O2AAAAAC)

Simon Spero: @MikeBennett: Do you have the data coded in a way that it could be fed into Multi     (1O2AAAAAD)

Dimensional Scaling for graphing?     (1O2AAAAAE)

Mike Bennett: @Simon re feeding graphing:no. not many numeric measures were asserted.     (1O2AAAAAF)

Rex Brooks: John F. Sowa noted the connection between people using terms in human interoperability and     (1O2AAAAAG)

the improvements that come about due to that.     (1O2AAAAAH)

Nicola Guarino: Excellent question, John a crucial one!     (1O2AAAAAI)

Steve Ray: @John: Fascinating point about getting humans to be interoperable, a la common     (1O2AAAAAJ)

terminology. I am definitely running into that in the world of disaster management interoperability,     (1O2AAAAAK)

where "interoperability" is commonly interpreted as "interchangeability of emergency personnel"     (1O2AAAAAL)

Todd Schneider: Steve, look at the NCOIC SCOPE model to get a better understanding of     (1O2AAAAAM)

interoperability'.     (1O2AAAAAN)

Todd Schneider: One perspective of interoperability is crossing boundaries (that didn't need crossing     (1O2AAAAAO)

in the past or haven't been considered explicitly in the past)     (1O2AAAAAP)

Simon Spero: [summary of discussion: labels/words are for people ; Mike Bennett points out that     (1O2AAAAAQ)

business users are concerned about definitions]     (1O2AAAAAR)

Amanda Vizedom: @JohnSowa: But even in a case that appears to be as you say, nailing down and     (1O2AAAAAS)

tracking the relationship between the different concepts *independently of the local terminology* or     (1O2AAAAAT)

  • across local terminologies* is typically critical to the getting the benefit. That is, the     (1O2AAAAAU)

advantage is in being able to keep *both* local-human-interpretable presentation/usability *and*     (1O2AAAAAV)

machine usability.     (1O2AAAAAW)

Michael Uschold: @JohnSowa - there is a lot of ambiguity in natural language definitions, because we     (1O2AAAAAX)

all use terms in different ways. There is also a lot of ambiguity in formal logic definitions     (1O2AAAAAY)

because they miss so much of the intended meaning, which is more easily expressed in natural     (1O2AAAAAZ)

Nicola Guarino: @JohnSowa (I repeat it because there was a typo): there is a (huge) benefit related     (1O2AAAAAAB)

to the terminology used, ONE related to the way the formalization of the intended meanind is done     (1O2AAAAAAC)

(independently from computational aspects), and finally one related to the computational use of the     (1O2AAAAAAD)

terminology (typically for taxonomic reasoning)     (1O2AAAAAAE)

Nicola Guarino: @MichaelGruninger & Michael Uschold: maybe JohnSowa's point on distinguishing between     (1O2AAAAAAF)

different uses of ontologies (terminological clarification vs. formal clarification vs. automated     (1O2AAAAAAG)

reasoning) can be made explicit in the "application framework"...     (1O2AAAAAAH)

Michael Uschold: Re: @Nicola's comment about incorporating @JohnSowa's distinction. Agree, this     (1O2AAAAAAJ)

should be incorporated. To some extent it is there already.     (1O2AAAAAAK)

Simon Spero: [My diss. topic is on interface between controlled vocabularies and ontologies. It's     (1O2AAAAAAL)

been misunderstood by people on both sides since before Aristotle was a gleam in his father's eye]     (1O2AAAAAAM)

Bart Gajderowicz: Regarding controlled vocabularies, there is a survey out about this. Perhaps     (1O2AAAAAAN)

beneficial to check back on the results:     (1O2AAAAAAO)

Michael Uschold: On Value metrics: if a value model is a subset or subtype of another one, maybe a     (1O2AAAAAAQ)

good idea is to show this in a venn diagram or tree structure.     (1O2AAAAAAR)

Simon Spero: [Now moving to track 3 - Value Models, Value Metrics and Value Proposition]     (1O2AAAAAAS)

Peter P. Yim: ALL: please identify clearly who you are addressing with "@" before your message (like     (1O2AAAAAAT)

@MichaelGruninger or @MichaelUschold, @JohnSowa or @JohnBateman, so that it will not be ambiguous) -     (1O2AAAAAAU)

I need that help because in the post-processing of the chat transcript, I will reshuffle the dialog     (1O2AAAAAAV)

so that Questions and Answers, and related discussion are placed adjacent to one another     (1O2AAAAAAW)

Rex Brooks: @ToddSchneider, I believe you were referring to the granularity matching between use case     (1O2AAAAAAX)

Michael Uschold: Some of @ToddSchneider's material on value models and metrics could be integrated     (1O2AAAAAAZ)

into the ontology application framework, rather than standing alone.     (1O2AAAAAAAA)

Simon Spero: [track change - track 4 - Strategies for "Making the Case"]     (1O2AAAAAAAC)

Simon Spero: [weren't FFC's actors often drunk, on LSD, or both?]     (1O2AAAAAAAD)

Alan Rector: The speaker keeps fading out     (1O2AAAAAAAE)

Rex Brooks: Yes, we need Matthew to speak a little louder.     (1O2AAAAAAAF)

Rex Brooks: The granularity issue applies to the strategy, too. If we narrow our focus to specific     (1O2AAAAAAAG)

use-cases or the most generic use cases, we stand a better chance of scoring well.     (1O2AAAAAAAH)

Rex Brooks: The notion of which values count most is a good consideration.     (1O2AAAAAAAI)

Bart Gajderowicz: Is there any benefit to talking about sub-ontologies, micro-theories (Cyc term) or     (1O2AAAAAAAJ)

axioms in repositories (COLORE) vs. full ontologies? Full ontologies may be overkill for most     (1O2AAAAAAAK)

applications?     (1O2AAAAAAAL)

Mike Bennett: @Bart one or 2 of the case studies showed benefit in reuse of existing, common ontology     (1O2AAAAAAAM)

Rex Brooks: @Bart: Not sure I would use those kinds of arguments to any audience other than other     (1O2AAAAAAAO)

ontologists or folks with an interest in ontology. For the end users I would focus on solving their     (1O2AAAAAAAP)

problems and only bring up HOW if asked.     (1O2AAAAAAAQ)

Simon Spero: It turns out that Data Quality has to have a case made for it too, alas. [     (1O2AAAAAAAR)

John Bateman: @BartGajderowicz: definitely, but only when the audience has got out of the elevator,     (1O2AAAAAAAT)

into the meeting room and then onto the details... so a question of granularity in what level of     (1O2AAAAAAAU)

pitch when I'd guess. Part of the methodology for engineering things properly (so it is a selling     (1O2AAAAAAAV)

point that there *is* a methodology).     (1O2AAAAAAAW)

Nicola Guarino: @Matthew: speaking of the role of ontology on data quality, it occurs to me that in     (1O2AAAAAAAX)

many cases just "ontology awareness" is enough to produce good data (e.g., choosing good,     (1O2AAAAAAAY)

non-ambiguous names for the entities we talk of), without necessarily using ontologies as artefacts.     (1O2AAAAAAAZ)

This means that a certain ontology education is necessary for building the controlled vocabularies     (1O2AAAAAAAAA)

Matthew West: @Nicola: Yes. You have relatively little chance of success without an ontological     (1O2AAAAAAAAC)

approach, even if that is not what it is called.     (1O2AAAAAAAAD)

Amanda Vizedom: @Bart - this touches another angle, of great interest to me, from which the framework     (1O2AAAAAAAAE)

can be used: the need to better understand ontology best practices and principles of good ontology     (1O2AAAAAAAAF)

design. There is very little work done that reflects or addresses the way good practices depend, in     (1O2AAAAAAAAG)

many ways, on the application context. Seeing how this framework might help us understand those     (1O2AAAAAAAAH)

dependencies is a direction of great promise, I think!     (1O2AAAAAAAAI)

Bart Gajderowicz: @AmandaVizedom: Yes. I've notices some work on analyzing adoption of Semantic Web     (1O2AAAAAAAAJ)

technologies, now that there is enough information. There's a few reports I ran across. I need to     (1O2AAAAAAAAK)

dig them up and can forward.     (1O2AAAAAAAAL)

Bart Gajderowicz: @MikeBennett: Thanks, I saw the slides on reuse. I was referring more to the size     (1O2AAAAAAAAM)

of the ontologies. For example, FOAF and Good Relations are relatively small but very specific in     (1O2AAAAAAAAN)

their scope, which (assuming) helped with their adoption.     (1O2AAAAAAAAO)

Mike Bennett: @Bart there is definitely a case to be made for a set of common, granular ontologies     (1O2AAAAAAAAP)

that people can refer to (time, geog, accounting, legal etc.).     (1O2AAAAAAAAQ)

Bart Gajderowicz: @RexBrooks: same answer. Smaller ontologies are specific to a particular problem,     (1O2AAAAAAAAR)

so more relatable to the end user.     (1O2AAAAAAAAS)

Mike Bennett: @Bart the audience to whom to make that case is the Linked Data folks I think     (1O2AAAAAAAAU)

Bart Gajderowicz: @MikeBennett: Agreed. But I view sub-ontologies as being used in analyzing data,     (1O2AAAAAAAAV)

not just linking it. When I look at the Dataset Publishing Language (DSPL) project, "Slices" look     (1O2AAAAAAAAW)

like different combinations of relationships between "Concepts". These "Slices" resemble     (1O2AAAAAAAAX)

Mike Bennett: @Bart interesting. thanks for the pointer. One thing we have done in the EDM Council     (1O2AAAAAAAAZ)

work is identify common terms and commit to trying to find the most appropriate standard for each     (1O2AAAAAAAAAA)

(e.g. ISO 3166 for countries).     (1O2AAAAAAAAAB)

Bart Gajderowicz: @MikeBennett: Thanks. I will take a look at this work.     (1O2AAAAAAAAAC)

Mike Bennett: MatthewWest's Slide 10 is a better list of the kinds of people we should make the case     (1O2AAAAAAAAAD)

to, than what I had in the Case Studies similar slide.     (1O2AAAAAAAAAE)

Matthew West: @MikeBennett: I notice there is considerable crosstalk between the tracks. Ours in     (1O2AAAAAAAAAF)

particular, since it is so general. You might want to pick up MDM as a case study too.     (1O2AAAAAAAAAG)

Peter P. Yim: [track change - track 5 - Grand Challenges]     (1O2AAAAAAAAAH)

Michael Uschold: I agree with @JohnSowa's voice comment that the grand challenge problems are more     (1O2AAAAAAAAAI)

general AI problems than ontology problems per se.     (1O2AAAAAAAAAJ)

Rex Brooks: @JohnSowa: Agreed. A Grand Challenge would be to "Make the Cases for Ontology"     (1O2AAAAAAAAAK)

highlighting the "Cases".     (1O2AAAAAAAAAL)

Michael Uschold: On the Grand Challenge track. While it is useful and interesting overall, I do not     (1O2AAAAAAAAAM)

see a clear connection to how to make a case for ontology. What has been learned in this track that     (1O2AAAAAAAAAN)

can be distilled into a tip, hint or guideline that helps make a case for ontology?     (1O2AAAAAAAAAO)

Steve Ray: @MikeUschold: I think this track simply provides a pointer to future opportunity areas     (1O2AAAAAAAAAP)

where one could apply the methods we are articulating.     (1O2AAAAAAAAAQ)

Peter P. Yim: @JohnSowa @MichaelUschold - as Matthew pointed out (slide#3) there is effective, NO CASE     (1O2AAAAAAAAAR)

for Ontology (as was pointed out analogously during the Track-4 session, that there is no case for     (1O2AAAAAAAAAS)

calculus) ... but the Grand Challenges will be able to focus our energy     (1O2AAAAAAAAAT)

John Bateman: @MichaelUschold: I guess this is along the lines: these applications are fantastic, to     (1O2AAAAAAAAAU)

do them ontologies are a must, therefore this is the case for ontology... But I wonder if we can     (1O2AAAAAAAAAV)

find applications which really are completely irresistable.     (1O2AAAAAAAAAW)

Nicola Guarino: John: +1     (1O2AAAAAAAAAX)

Matthew West: @JohnBateman: The things you are mentioning are research goals we need to identify.     (1O2AAAAAAAAAY)

Nicola Guarino: @RamSriram: Speaking of great challenges, I would like to point to     (1O2AAAAAAAAAZ) FuturICT is a proposal for a 10-years European "Flagship"     (1O2AAAAAAAAAAA)

project, which scored first in a recent call, aiming at world-wide simulation, data interpretation,     (1O2AAAAAAAAAAB)

crisis management, etc. Great opportunities for ontologies, especially for ontology of large scale     (1O2AAAAAAAAAAC)

socio-technical systems     (1O2AAAAAAAAAAD)

Matthew West: The thing about grand challenges is that they have some objective, you know when you     (1O2AAAAAAAAAAE)

have succeeded. I think an important prequel to grand challenges are research goals. What are the     (1O2AAAAAAAAAAF)

current gaps? A useful Grand Challenge would then depend on the achievement of some of those     (1O2AAAAAAAAAAG)

research goals.     (1O2AAAAAAAAAAH)

John Bateman: I doubt there is going to be a grand challenge for *ontology* that is of interest to     (1O2AAAAAAAAAAI)

outsiders; the only challenges will *have* to be specific problems where ontologies can be argued to     (1O2AAAAAAAAAAJ)

provide an important part of the work: as in FuturICT.     (1O2AAAAAAAAAAK)

Bart Gajderowicz: @JohnBateman: Yes. The granularity is much more relatable to end-users. You     (1O2AAAAAAAAAAL)

basically speak their language. The pitch woudl be something like " sub-ontology A is about geo,     (1O2AAAAAAAAAAM)

sub-ontology B is about time, etc. One of these may fit you domain.     (1O2AAAAAAAAAAN)

Alden Dima: @JohnBateman I would also agree with you. We are asking potential "customers" for grand     (1O2AAAAAAAAAAO)

challenges and they don't per se care about ontologies. So I think we are running the risk of asking     (1O2AAAAAAAAAAP)

for challenges and then saying "Sorry not what we were looking for". But perhaps we should look for     (1O2AAAAAAAAAAQ)

multidisciplinary challenges in which we can play a significant role and then partner with the other     (1O2AAAAAAAAAAR)

Ramdsriram: @John: The purpose of the track is to identify a few grand challenges computational     (1O2AAAAAAAAAAT)

problems and identify opportunities for ontologies. For example, can we achieve the "kind of things"     (1O2AAAAAAAAAAU)

that Eliot, Ramesh, and Nabil talked about without using any ontologies (or related technology).     (1O2AAAAAAAAAAV)

Simon Spero: Is there an elevator in the NIST building?     (1O2AAAAAAAAAAW)

Alden Dima: @Simon - we do have elevators in our buildings. I believe that the room for the Summit is     (1O2AAAAAAAAAAX)

on the ground floor.     (1O2AAAAAAAAAAY)

Simon Spero: Alden Dima: I think that testing an elevator speech in an NIST elevator is pretty good     (1O2AAAAAAAAAAZ)

Alden Dima: @Simon - we can start with the elevator in the tall admin building and work our way to     (1O2AAAAAAAAAAAB)

the shorter ones...     (1O2AAAAAAAAAAAC)

Rex Brooks: Bye Todd. You gave a fine presentation, Todd.     (1O2AAAAAAAAAAAE)

Peter P. Yim: [track change - Communique]     (1O2AAAAAAAAAAAF)

Michael Uschold: I'm getting on my cell, two seconds, hang on     (1O2AAAAAAAAAAAG)

Mike Bennett: @MichaelUschold (re slide 4) but does "the Ontology community" have one understanding     (1O2AAAAAAAAAAAH)

of what it means and what it's used for?     (1O2AAAAAAAAAAAI)

Rex Brooks: @MichaelUschold: I think this is a terrific way to go and I look forward to the interim     (1O2AAAAAAAAAAAJ)

and final versions.     (1O2AAAAAAAAAAAK)

Mike Bennett: @Matthew indeed. Master data management (as distinct from metadata management - had me     (1O2AAAAAAAAAAAL)

going!) is a feature of some of our case studies e.g. industry standard terms across an industry     (1O2AAAAAAAAAAAM)

gets deployed in a number of ways within firms including master data (golden source), metadata     (1O2AAAAAAAAAAAN)

repositories and other application areas.     (1O2AAAAAAAAAAAO)

Peter P. Yim: @MichaelUschold - just to make sure nothing falls through the crack, can you identify     (1O2AAAAAAAAAAAP)

exactly who has promised you text by end-of-day Monday, please?     (1O2AAAAAAAAAAAQ)

Nicola Guarino: MichaelUschold's scheme is GREAT, I am just a little bit concerned about its level of     (1O2AAAAAAAAAAAR)

Mike Bennett: I promised text my end of Monday     (1O2AAAAAAAAAAAT)

Ramdsriram: @Peter: We should have a rough draft (hopefully).     (1O2AAAAAAAAAAAV)

Rex Brooks: I'm pretty sure Todd has promised Track 3 by end of Monday. If not I will speak with him.     (1O2AAAAAAAAAAAW)

Terry Longstreth: Put the email address on the chat     (1O2AAAAAAAAAAAX)

Peter P. Yim: @Steve - ref. the dinner, the way you did it last year (a email to the list with a link     (1O2AAAAAAAAAAAY)

someone can click on to provide you the response, offline) that would be great!     (1O2AAAAAAAAAAAZ)

Peter P. Yim: great session ... very productive!     (1O2AAAAAAAAAAAAA)

Nicola Guarino: I agree, very productive and promising!     (1O2AAAAAAAAAAAAC)

Peter P. Yim: -- session ended: 11:36am PDT --     (1O2AAAAAAAAAAAAD)

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

Audio Recording of this Session     (1P)

Additional Resources     (1Q)

For the record ...     (1Q4)

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

Note that we will start promptly; if you are new to this setting, please dial-in to the conference call 5~10 minutes before the scheduled start time!     (1R1)

  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at:     (1R5E)
    • view-only password: "ontolog"     (1R5E1)
    • 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.     (1R5E2)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the slides above and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1R5E3)
  • Discussions and Q & A:     (1R5F)
    • (Unless the conference host has already muted everyone) Please mute your phone, by pressing "*2" on your phone keypad, when a presentation is in progress. To un-mute, press "*3"     (1R5F1)
    • You can type in your questions or comments through the browser based chat session by:     (1R5F2)
      • instructions: once you got access to the page, click on the "settings" button, and identify yourself (by modifying the Name field). 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.     (1R5F3A)
    • (when everyone is muted) If you want to speak or have questions or remarks to make, please "raise your hand (virtually)" by click on the "hand button" (lower right) on the chat session page. You may speak when acknowledged by the speaker or the session moderator (again, press "*3" on your phone to unmute). 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 "*2" on your phone to mute yourself after you are done speaking.)     (1R5F4)
    • 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!     (1R5F5)
  • Please note that this session will be recorded, and the audio archive is expected to be made available as open content to our community membership and the public at-large under our prevailing open IPR policy.     (1R5J)

Attendees     (1S)

  • Expecting:     (1S2)
    • ... if you are coming to the session, please add your name above (plus your affiliation, if you aren't already a member of the community) above; or e-mail <> so that we can reserve enough resources to support everyone's participation. ...     (1S3A)

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