From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2011: Panel Session-2 - Ontology Application Framework - I - Thu 2011_02_03     (1)

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

Session Title: Strawman for the Ontology Application Framework     (1B)

Session Co-chairs: Professor MichaelGruninger (U of Toronto) & Dr. MichaelUschold (Semantic Arts)     (1C)

Panelists:     (1D)

  • Dr. MichaelUschold (Semantic Arts) - "A Framework for Understanding and Classifying Ontology Applications" [ ref. ]     (1E)
  • Dr. LeoObrst (MITRE) - "Ontologies & Applications"     (1F)
  • Professor MichaelGruninger (U of Toronto) - "Notes for an Ontology Application Framework"     (1G)
  • Professor AlanRector (U of Manchester) - "Problems arising in applications: Background Knowledge Representation, Data modelling & Ontologies"     (1H)

Abstract     (1J)

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

  • Track-1 Focus: "Ontology Application Framework"     (1J2)
  • Session Title: Strawman for the Ontology Application Framework     (1J3)

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."     (1J4)

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.     (1J5)

In this kickoff meeting for Track 1: Ontology Application Framework, panelists will be presenting various ideas for a strawman proposal for the framework. The objectives of the meeting will be find enough agreement so that we can initiate online discussions to identify and classify applications of ontologies within business and industrial use cases. This classification will be used to organize the uses cases proposed by Track 2.     (1J6)

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

Agenda     (1K)

Ontology Summit 2011 - Panel Session-2     (1K1)

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

Proceedings     (1L)

Please refer to the above     (1L1)

IM Chat Transcript captured during the session    (1L2)

see raw transcript here.     (1L2A)

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

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

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

Welcome to the Ontology Summit 2011: Panel Session-2 - Ontology Application Framework - I - Thu 2011_02_03     (1L2F)

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

Session Title: Strawman for the Ontology Application Framework     (1L2H)

Session Co-chairs: Professor Michael Grüninger (U of Toronto) & Dr. Michael Uschold (Semantic Arts)     (1L2I)

Panelists:     (1L2J)

Applications"     (1L2L)

Representation, Data modelling & Ontologies"     (1L2P)

Please refer to session details (dial-in, agenda, slides, etc.) at:     (1L2R)

anonymous morphed into Pat Barkman     (1L2U)

anonymous morphed into Todd Schneider     (1L2V)

anonymous1 morphed into Bruce Bray     (1L2W)

anonymous2 morphed into Amanda Vizedom     (1L2X)

anonymous morphed into Ram D. Sriram     (1L2Y)

Susan Turnbull (GSA) morphed into Susan Turnbull     (1L2Z)

anonymous morphed into Antoinette Arsic     (1L2AA)

Alan Rector: Please put details of paper on chat show - the line looses some detail - thanks     (1L2AB)

Peter P. Yim: @MichaelUschold - it's slide#2 (not #1) now     (1L2AC)

Peter P. Yim: slide#15 (not #14)     (1L2AD)

Yu Lin: where is it now? I got lost     (1L2AE)

Peter P. Yim: For some reason, our speakers haven't been calling out their slide numbers very     (1L2AF)

accurately, therefore (especially asynchronous participants) please bear with the situation, and try     (1L2AG)

to sync up to the content as they are presented     (1L2AH)

Arturo Sanchez: @MichaelUschold: the main issue with all the approaches, as I understand them, is     (1L2AI)

that semantic information that drive the mapping is not explicitly represented, and therefore needs     (1L2AJ)

to be mediated by humans and properties that are supposed to be preserved by the mappings is not     (1L2AK)

explicitly exposed. If you get the chance, I'd like to hear your opinion (as well as Michael     (1L2AL)

Gruninger's, Leo's, and Professor Rector's) Thanks!     (1L2AM)

Arturo Sanchez: @MichaelUschold: Also, it is not clear to me how change management is represented in     (1L2AN)

all these approaches/architectures. That is to say, when the ontologies change, what happens?     (1L2AO)

Arturo Sanchez: @MichaelUschold and the rest of the team: to document architectural concerns, I would     (1L2AP)

suggest to use the notations proposed by the Software Engineering Institute (CMU). "Documenting     (1L2AQ)

Software Architectures", latest edition (Addison-Wesley)     (1L2AR)

Todd Schneider: Leo, there are apps that allow the generation of source code from an ontology (e.g.,     (1L2AV)

Top Quadrant)     (1L2AW)

Peter P. Yim: Michael Grüninger is presenting ... on slide#2 now     (1L2AX)

Arturo Sanchez: @ToddSchneider: it would be interesting to analyze--or come up with--software     (1L2AY)

development frameworks that support the lifecyle of ontologies, including automatic code generation     (1L2AZ)

injected into the application and directly derived from the ontology/ies.     (1L2AAA)

Todd Schneider: Instead of using application as the distinguishing criteria it may be more effective     (1L2AAB)

to use problem space.     (1L2AAC)

Steve Ray: @Todd: I agree that if the application is used for categorization, then we at least need a     (1L2AAD)

mapping provided from problem categories to application categories.     (1L2AAE)

anonymous morphed into Peter Bahnsen     (1L2AAF)

Todd Schneider: Arturo, I've been referring to this as ontologically driven development (with the     (1L2AAG)

subtext of displacing UML / SysML).     (1L2AAH)

Steve Ray: @Todd: ....keeping in mind that we want to provide information to people trying to make     (1L2AAI)

the case to stakeholders that know what problems they are facing. i.e. I'm agreeing with you.     (1L2AAJ)

Arturo Sanchez: @ToddSchneider: I think MichaelGruninger's characterization is with respect to the     (1L2AAK)

functionality that can be implemented by "ontology-based" or "ontology-driven" applications     (1L2AAL)

Arturo Sanchez: @ToddSchneider: ... and therefore, the characterization is domain-independent ...     (1L2AAM)

Todd Schneider: Problems resolved by applications realized by functionality     (1L2AAN)

Steve Ray: @Arturo: I think Todd's point is that if I were trying to make the case to someone, say in     (1L2AAO)

my company, I might know what problem I'm trying to solve, but may not be sure what functionality     (1L2AAP)

would be best to invoke. Or even if I knew what functionality was appropriate, my deciding vice     (1L2AAQ)

president might not recognize it in those terms.     (1L2AAR)

Todd Schneider: @Steve, exactly. Referring to what John Sowa suggested, you have to convince someone     (1L2AAS)

they have a problem (that your solution can solve).     (1L2AAT)

Steve Ray: We could provide guidance such as: Problem category --> Needed functionality -->     (1L2AAU)

Ontological approach --> Benefits     (1L2AAV)

Todd Schneider: @Steve, sounds good and make a simple graphic.     (1L2AAW)

Arturo Sanchez: @Todd & Steve: yes, your points are well taken, but that is why the summit has     (1L2AAX)

diffferent tracks. This track is about "A Framework for Understanding and Classifying Ontology     (1L2AAY)

Applications". There are other tracks that address the concern you are expressing. Now, it would     (1L2AAZ)

also make sense to document the architecture of well-known exemplars of ontology-driven/based     (1L2AAAA)

applications, for specific domains, which CIOs and CEOs associated with these domains can relate to.     (1L2AAAB)

Antoinette Arsic: It would be awesome to have instances of the ontologies for these in KM and     (1L2AAAC)

Decision Support.     (1L2AAAD)

Steve Ray: @Arturo: Agreed.     (1L2AAAE)

Todd Schneider: @Arturo, I think 'Framework' is the important part, 'application' may not be the best     (1L2AAAF)

qualifier/criteria for categorization (relative to the larger goals of the summit).     (1L2AAAG)

Peter P. Yim: = Alan Rector presenting now =     (1L2AAAH)

Arturo Sanchez: Very good presentations ... sorry I must leave now. I'll catch up through the Wiki.     (1L2AAAI)

Peter P. Yim: @Peter Bahnsen - Hello, would you let us know which organization are you affiliated with,     (1L2AAAJ)

Peter Bahnsen: @ Peter P. Yim I'm contracting with the GSA and am here on invite of Susan Turnbull     (1L2AAAL)

Peter P. Yim: @Peter Bahnsen - welcome! we are glad you can join us today     (1L2AAAM)

Peter P. Yim: @SusanTurnbull - Hi Susan!     (1L2AAAN)

Peter Bahnsen: Thanks for the welcome! I am new to the ontology community     (1L2AAAO)

Peter P. Yim: @Peter Bahnsen - hope you like what you see here!     (1L2AAAP)

Antoinette Arsic: on slide 5     (1L2AAAQ)

Peter P. Yim: @Antoinette - thank you     (1L2AAAR)

Michael Grüninger: I agree with Arturo -- the purpose of this track is to provide the frame of     (1L2AAAS)

reference for discussing how ontologies are used and how to demonstrate benefits.     (1L2AAAT)

Amanda Vizedom: @Steve and all: I think we do need a multi-dimensional categorization. As suggested,     (1L2AAAU)

there are things we'd normally think of as "application"-oriented, such as the functional     (1L2AAAV)

requirements and technology context. There are also user characterizations, subject matter     (1L2AAAW)

considerations (single-domain/cross domain), process considerations, organizational goals (things     (1L2AAAX)

down the road for which ontos should be reusable? mandates? legal, policy, other issues?), and on.     (1L2AAAY)

Michael Grüninger: If we tell someone that ontologies provide the technology that they need to solve     (1L2AAAZ)

their problems, we need to ensure that they understand exactly what is being delivered.     (1L2AAAAA)

Steve Ray: @Michael: Agreed, but someone should provide a mapping from problem categories to     (1L2AAAAB)

application categories. Seems like that would either be this track, or possibly Track 4 - Strategies     (1L2AAAAC)

for making the case.     (1L2AAAAD)

Michael Grüninger: @Steve: What are examples of problem categories?     (1L2AAAAE)

Peter P. Yim: @AmandaVizedom, Michael Grüninger and All - "multi-dimensional" is the key challenge ...     (1L2AAAAF)

how can we effectively document and present it     (1L2AAAAG)

Steve Ray: @Michael: Let's see... "We don't know how to assign the right expert to a customer     (1L2AAAAH)

account", or "I'm trying to optimize the load balancing in my electrical grid". These are off the     (1L2AAAAI)

top of my head. Some answers may be obvious, some not. Kind of gets into systems design.     (1L2AAAAJ)

Steve Ray: @Michael: I just realized you asked for categories, not examples. I'll have to think     (1L2AAAAK)

Amanda Vizedom: I don't think is news as an idea, but I've had a great opportunity to experience and     (1L2AAAAM)

observe the factors recently. I've been working on Ontology Design Pattern & Best Practice     (1L2AAAAN)

documentation for ontology developers within our project, translating general ontology best     (1L2AAAAO)

practices and ODPs to specifically what to do in our context. Because target audience is (a) often     (1L2AAAAP)

only lightly trained, learning on the job, and (b) not necessarily interested in more general level,     (1L2AAAAQ)

except where understanding it will help them again later, and (c) mixed in desire/ability/tendency     (1L2AAAAR)

to find related external resources and try to understand and integrate them, I need to be able to     (1L2AAAAS)

articulate, in complementary guidance, in what ways these docs are tailored. Meantime, I'm thinking     (1L2AAAAT)

about how the tailored docs could be part of a larger body of guidance docs in which context one     (1L2AAAAU)

could find the bits that apply to ones own cases. I've not gotten to the point of listing such     (1L2AAAAV)

factors (not part of client task, of course), but the variety is very salient.     (1L2AAAAW)

Yu Lin: @MichaelGruninger: I don't think gene sequencing is using ontology technology. Could you     (1L2AAAAX)

please give an example?     (1L2AAAAY)

Bruce Bray: sequence ontology is an evolving example of use of ontology for representing gene     (1L2AAAAZ)

Michael Grüninger: @Yu Lin: I was referring to ontologies (such as the Sequence Ontology) that are     (1L2AAAAAB)

used to support the analysis of gene sequence data e.g. query all databases for all genes whose     (1L2AAAAAC)

transcripts are edited, or trans-spliced, or are bound by a particular protein.     (1L2AAAAAD)

Yu Lin: @Bruce Thank you very much. I think it rather a tool for data integration than for the     (1L2AAAAAE)

sequencing analyzing.     (1L2AAAAAF)

Yu Lin: Thank you Michael, I got what you meant     (1L2AAAAAG)

Todd Schneider: Thank you to all the speakers. Have to go.     (1L2AAAAAH)

Alden Dima: @PeterYim,@SteveRay - For me, a high-level way of presenting the categories revolves     (1L2AAAAAI)

around saying that ontologies enable efficient 1) coordination 2) cooperation and 3) coherence     (1L2AAAAAJ)

between sofware systems and their users. I'm sure that there are other high-level categories as     (1L2AAAAAK)

Fabian Neuhaus: @Alan: about integrity constraints: it might be of interest to you that there is a     (1L2AAAAAM)

W3C Member Submission called "Validating Semantic Web Data with OWL Integrity Constraints" on its     (1L2AAAAAN)

Alan Rector: Glad to hear it - I have been concerned that this stream was critical but not getting     (1L2AAAAAP)

the attention we require.     (1L2AAAAAQ)

Ram D. Sriram: @MichaelGruninger: I believe the track's title is "Application Framework." I presume you     (1L2AAAAAR)

are going to synthesize the presentations into a "framework" perspective. Such a framework should     (1L2AAAAAS)

help us to resolve various views for ontologies and applications.     (1L2AAAAAT)

Alan Rector: One important difference is uses of ontologies as payload or "coding" or a common     (1L2AAAAAU)

structured vocabulary - e.g. the Gene Ontology or SNOMED - and use of ontologies as structure for     (1L2AAAAAV)

software or standards.     (1L2AAAAAW)

Pat Barkman: Search Engine Optimization. Were looking for a way to use an ontology for SEO because we     (1L2AAAAAX)

have a dataset that blends and makes really no distinction between a broad selection of knowledge     (1L2AAAAAY)

domains (for example: biology, physics, cosmology ...) In the vast number of data sources these     (1L2AAAAAZ)

subjects are considered separate disciplines -- segmented. Our dataset defines commonalities and     (1L2AAAAAAA)

treats everything as one subject. Well, you might think that sounds great ... but it kinda sucks for     (1L2AAAAAAB)

SEO because our web content is semantically very different than the rest of the web so we score     (1L2AAAAAAC)

poorly based on the existing Search Engine algorithms. So, were looking at creating Topic Pages     (1L2AAAAAAD)

based on our data. Then when those Topic Pages get crawled we believe we will begin to educate     (1L2AAAAAAE)

Search Engines about the commonalties between various disciplines and that will enhance our search     (1L2AAAAAAF)

engine scores. Then we also need to make our data (which is in English) searchable in multiple     (1L2AAAAAAG)

languages. And frankly, we also need an ontology to search our data more effectively ourselves.     (1L2AAAAAAH)

Pat Barkman: so, those are our use cases: SEO, multi-lingual & enhancing our own search capabilities     (1L2AAAAAAI)

of a dataset that's likely unprecedented in it's cross-disciplinarily nature     (1L2AAAAAAJ)

Pat Barkman: wouldn't the use cases be the set of system requirements for developing the ap     (1L2AAAAAAK)

Steve Ray: @Pat: What is your dataset? Could you expand on this?     (1L2AAAAAAM)

Pat Barkman: @steve our data is in the form of text, video & audio, discusses all aspects of science     (1L2AAAAAAN)

as one subject     (1L2AAAAAAO)

Pat Barkman: ...kinda hard to describe other than as a "complete" dataset     (1L2AAAAAAP)

Steve Ray: @Pat: Could you say what purpose your are trying to fulfill? Education? Consumer service     (1L2AAAAAAQ)

provision? ....     (1L2AAAAAAR)

Pat Barkman: OK ... thanks for that clarification ... Ap FW summit/community     (1L2AAAAAAS)

Pat Barkman: @Steve - education, primarily     (1L2AAAAAAT)

Steve Ray: @Pat: So perhaps educational curriculum material might be an ontology. In this forum we     (1L2AAAAAAU)

have talked about an ontology for curricula (last year in fact).     (1L2AAAAAAV)

Pat Barkman: @Steve, so I can probably find something in the archived discussion threads on that,     (1L2AAAAAAW)

Steve Ray: Yes, I'll try to dig up some links.     (1L2AAAAAAZ)

Jim Disbrow: The Ontology Case Study I tried to put together (on an Energy-Water-Climate nexus) has     (1L2AAAAAAAA)

failed so far. The lack of funding may be the single largest factor. The lack of volunteers (and not     (1L2AAAAAAAB)

getting done what was needed) was also a factor.     (1L2AAAAAAAC)

Peter P. Yim: @AmandaVizedom - please capture you point here ... it's great!     (1L2AAAAAAAD)

Amanda Vizedom: Here's the point I just made on the call: In addition to looking at and collecting     (1L2AAAAAAAE)

use cases, there is tremendous value in looking at them comparatively and *specifically* looking at     (1L2AAAAAAAF)

what worked and didn't work in each case. Doing this kind of collection and comparison of LL in many     (1L2AAAAAAAG)

use cases is also valuable, as discussed a bit last year, for identifying Best Practices and     (1L2AAAAAAAH)

building that body of shared knowledge we don't yet have. But comparing what worked and didn't in     (1L2AAAAAAAI)

different use cases is often just the light one needs to bring out the dimensions (and important     (1L2AAAAAAAJ)

points along those dimensions) we're looking to understand. Comparing use cases with LL, we can ask     (1L2AAAAAAAK)

What are the differences between those cases, such that one thing worked here and another thing worked there?     (1L2AAAAAAAL)

Amanda Vizedom: In follow-up, Michael, Alan, and others noted the difficulty in getting people to     (1L2AAAAAAAM)

talk about their failures, and that these haven't been solicited as part of the summit use case     (1L2AAAAAAAN)

call. Michael added this to that call. I agree, and having been aiming to get a workshop set up at     (1L2AAAAAAAO)

one of the major conferences to talk about use cases and LL, collaborating to identify both     (1L2AAAAAAAP)

meaningful differences between the use cases and best practices.     (1L2AAAAAAAQ)

Peter P. Yim: Great session ... fantastic presentations from all the panelists! Thanks you All! Bye!     (1L2AAAAAAAR)

Steve Ray: Logging out. Thanks Michael and team for another great session.     (1L2AAAAAAAV)

Peter P. Yim: I will keep the chat board going until 11:30am PST (i.e. for another 8 minutes or so) ...     (1L2AAAAAAAW)

past that, what goes into the chat-board will not get captured into the session proceedings.     (1L2AAAAAAAX)

Peter P. Yim: - session ended 11:21am PST --     (1L2AAAAAAAY)

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

  • Further Question & Remarks - please post them to the [ ontology-summit ] listserv     (1L2AAAAAAAAA)
    • all subscribers to the previous summit discussion, and all who responded to today's call will automatically be subscribed to the [ ontology-summit ] listserv     (1L2AAAAAAAAA1)
    • if you are already subscribed, post to <ontology-summit [at]>     (1L2AAAAAAAAA2)
    • (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.     (1L2AAAAAAAAA3)

Audio Recording of this Session     (1M)

Additional Resources     (1N)

For the record ...     (1N4)

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

  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at:     (1O4E)
    • view-only password: "ontolog"     (1O4E1)
    • 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.     (1O4E2)
    • 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.     (1O4E3)
  • Discussions and Q & A:     (1O4F)
    • (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"     (1O4F1)
    • You can type in your questions or comments through the browser based chat session by:     (1O4F2)
      • 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.     (1O4F3A)
    • (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.)     (1O4F4)
    • 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!     (1O4F5)
  • 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.     (1O4J)

Attendees     (1P)

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