From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2012: Session-12 - Thu 2012-03-29     (1)

Summit Theme: OntologySummit2012: "Ontology for Big Systems"     (1A)

Session Topic: Organizing the 'Big' Communique     (1B)

OntologySummit2012_Communique co-Lead Editors & Session co-Chairs:     (1C)

Panelists:     (1E)

  • Dial-in:     (1I7D)
    • Phone (US): +1 (206) 402-0100 ... (long distance cost may apply)     (1I7D1)
    • when prompted enter PIN: 141184#     (1I7D2)
    • Skype: " joinconference " (use the PIN above) ... (generally free-of-charge, when connecting from your computer)     (1I7D3)
      • for skype users who have trouble with finding the Skype Dial pad ... it's under the "Call" dropdown menu as "Show Dial pad"     (1I7D3A)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at:     (1I7E)
    • view-only password: "ontolog"     (1I7E1)
    • 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.     (1I7E2)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the slides & material above (where applicable) and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1I7E3)
    • 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").     (1I7F1)
    • 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.     (1I7F2)
    • 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!     (1I7F3)
  • Discussions and Q & A:     (1I7G)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1I7G1)
    • 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.)     (1I7G2)
    • 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.)     (1I7G3)
    • 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.)     (1I7G4)
  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1I7I)
  • 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.     (1I7K)

Attendees     (1J)

Abstract     (1K)

Session Topic: Organizing the 'Big' Communique     (1K1)

This is our 7th Ontology Summit, a joint initiative by NIST, Ontolog, NCOR, NCBO, IAOA & NCO_NITRD with the support of our co-sponsors. The theme adopted for this Ontology Summit is: "Ontology for Big Systems." The event today is our 12th virtual session.     (1K2)

The principal goal of the summit is to bring together and foster collaboration between the ontology community, systems community, and stakeholders of some of "big systems." Together, the summit participants will exchange ideas on how ontological analysis and ontology engineering might make a difference, when applied in these "big systems." We will aim towards producing a series of recommendations describing how ontologies can create an impact; as well as providing illustrations where these techniques have been, or could be, applied in domains such as bioinformatics, electronic health records, intelligence, the smart electrical grid, manufacturing and supply chains, earth and environmental, e-science, cyberphysical systems and e-government.     (1K3)

As is traditional with the Ontology Summit series, the collective results of this extended discourse will be captured in the form of a communiqu��, with expanded supporting material provided on the web. Towards that end, our communique lead editors will conduct this session, where we will, as a community, review how we would want to frame the message we would want to deliver in the communique, review the input from each of the tracks, as synthesized from the focused discourse over the last couple of months or so. Our target is to get to an 'almost final' communique draft available for community review/comment between April-4 and April-8, which will then allow us to have a final draft before the OntologySummit2012_Symposium on Thursday 12-April-2012, where the communique will be finally reviewed and adopted.     (1K4)

The goal of the meeting is to come up with an initial draft, albeit possible very coarse, of the summit's communique. Due to the time constraint, discussions will need to be focused and succinct.     (1K5)

More details about this Summit at: OntologySummit2012 (home page for the summit)     (1K6)

Agenda     (1L)

Ontology Summit 2012 - Panel Session-12     (1L1)

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

Proceedings     (1M)

Please refer to the above     (1M1)

IM Chat Transcript captured during the session    (1M2)

see raw transcript here.     (1M2A)

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

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

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

Ontology Summit 2012: Session-12 - Thu 2012-03-29     (1M2F)

Summit Theme: Ontology Summit 2012: "Ontology for Big Systems"     (1M2G)

Session Topic: Organizing the 'Big' Communique     (1M2H)

Panelists - Track Champions and Co-editors of the Communique:     (1M2J)

Mute control: *7 to un-mute ... *6 to mute     (1M2S)

Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1M2T)

Proceedings:     (1M2U)

anonymous morphed into Elizabeth Florescu     (1M2V)

anonymous morphed into Ernie Lucier     (1M2W)

Todd Schneider: Good afternoon/morning everyone.     (1M2X)

Todd Schneider: Will be with you shortly.     (1M2Y)

anonymous morphed into Tom Tinsley     (1M2Z)

Mike Bennett: I have to jump off just before 2 Eastern / 11 Pacific.     (1M2AA)

anonymous morphed into Doug Foxvog     (1M2AB)

Matthew West: I've had my head down in our own track, so do not have a broad view of this summit.     (1M2AC)

Mike Bennett: One possible theme is the different applications of ontologies, as a technical artifact     (1M2AD)

in its own right, and as a means to capture common semantics across some large engineering system. I     (1M2AE)

don't know if that fits with what you are looking for here though.     (1M2AF)

Ali Hashemi: Steve Ray points out that many systems: software, enterprises are based around "Model     (1M2AG)

Driven Systems"     (1M2AH)

Matthew West: Model driven is closely associated with semantics of course.     (1M2AI)

Nicola Guarino: Modelling is much more general than ontological modelling     (1M2AJ)

Mike Bennett: @Nicola agreed. And ontology has broader applications than model driven engineering     (1M2AK)

(indeed, the latter has been a minority case in the Semantic Web world but has been shown to be     (1M2AL)

important in the big systems context)     (1M2AM)

Nicola Guarino: @Mike agreed     (1M2AN)

Terry Longstreth: Lemma: Ontological methods can be applied to engineering models to improve depth     (1M2AO)

and breadth of modeling semantics     (1M2AP)

Nicola Guarino: @Terry: I agree very much. Ontological analysis and actual engineered ontologies just     (1M2AQ)

complement (in a very useful way) model driven engineering (for instance model driven engineering     (1M2AR)

based on systems of differential equations)     (1M2AS)

Bobbin Teegarden: @Steve Are you implying, perhaps, that the (ontology)Model IS the System (as in     (1M2AT)

Model Driven Architecture (MDA))?     (1M2AU)

Steve Ray: @Bobbin: Yes I am.     (1M2AV)

Henson Graves: agree that we are in a model driven age. Also our modeling language are not as good as     (1M2AW)

we need. Ontology is the value proposition to make the models work.     (1M2AX)

Steve Ray: I suppose my point is that ontological modeling is a better, more rigorous way of modeling     (1M2AZ)

in general.     (1M2AAA)

Matthew West: Engineering models are more often mathematical than logical, but there are none the     (1M2AAB)

less ontological elements.     (1M2AAC)

Matthew West: @Steve: does that mean you propose replacing mathematics with logic?     (1M2AAD)

Steve Ray: @Matthew: Not really. Logic is just a part of mathematics, right? Where it makes sense,     (1M2AAE)

use logic. Where a differential equation makes sense, by all means use that.     (1M2AAF)

Matthew West: @Steve: Yes, but most people see ontology as being limited to expression in logic, and     (1M2AAG)

not to include broader mathematical models.     (1M2AAH)

Steve Ray: @Matthew: Fair enough. For inherently numerical problems, I would agree that mathematics     (1M2AAI)

as traditionally understood is best (such as a control system for example). But for symbolic     (1M2AAJ)

problems, ontology models are best.     (1M2AAK)

Steve Ray: @Matthew: So, both are models, and in fact I would submit that an ontological model     (1M2AAL)

provides the contextual framework in which a mathematical model operates.     (1M2AAM)

Jim Kirby: Where are the slides?     (1M2AAO)

Ernie Lucier: @Jim if you do not have access to hopper (the vnc server) then     (1M2AAQ)

Jim Kirby: @Ernie Thanks!     (1M2AAS)

Anatoly Levenchuk: We may at least tell that ontology is about meta-modeling part of modeling. There     (1M2AAT)

are many levels of meta-models and models, therefore we have difficulties in differentiating     (1M2AAU)

ontologizing and modeling (and programming too). Model transformations, compilation and mapping is     (1M2AAV)

about the same activity.     (1M2AAW)

anonymous morphed into Mary Brady     (1M2AAX)

Rex Brooks: While I haven't come to any overarching conclusion, I am now using UML Modeling in     (1M2AAY)

Enterprise Architect and Owl Ontology / Ontologies in Protege, and they are quite useful when     (1M2AAZ)

working back and forth from one to the other for specific classes, terms, systems-programs, etc. Of     (1M2AAAA)

course having a coordinated set of ontologies and models as the end products is very handy as     (1M2AAAB)

resources and references for getting specific kinds of information about these things as needed.     (1M2AAAC)

Rex Brooks: I haven't gotten to the point where using these with inferencing engines or open data     (1M2AAAD)

sources with SPARQL but I expect that to become even more useful.     (1M2AAAE)

Mike Bennett: @Rex have you considered using the Ontology Definition Metamodel (ODM) so as to have     (1M2AAAF)

your ontologies and logical UML models in the same tool? Mail me off list if you need to know     (1M2AAAG)

Bobbin Teegarden: @Rex Enterprise Architect is just coming out with an OWL Plugin, very formative     (1M2AAAI)

stage; and Elisa Kendall's VOM Plugin is more mature (and does follow ODM, ref by Bennett).     (1M2AAAJ)

Bobbin Teegarden: @Rex VOM Plugin is in MagicDraw, just fyi.     (1M2AAAK)

Mike Bennett: @Bobbin agreed. Also lets one generate OWL for use in Protege tools.     (1M2AAAL)

Rex Brooks: @Bobbin-Mary-Matthew: Thanks very much. Wish I could afford MagicDraw,     (1M2AAAM)

but I'm glad to hear that there is a plugin on the way for EA. However, I will probably continue to     (1M2AAAN)

use them as springboards back and forth, creating a kind of synergy I haven't had before.     (1M2AAAO)

Rex Brooks: @Mike: I had your email on another machine that failed recently. I would like to contact     (1M2AAAP)

you about the ODM. I was aware of it, but not this capability. My email is rexb[at]     (1M2AAAQ)

Ali Hashemi: Ernie Lucier suggests that the distinction between Current Problems and Uses is unclear.     (1M2AAAR)

Ali Hashemi: Nicola Guarino suggests that section headings should convey more meaning.     (1M2AAAS)

Ernie Lucier: I have to leave now.     (1M2AAAT)

Mary Brady: @Ernie: I can stay for just a bit longer...about 1:15     (1M2AAAU)

anonymous morphed into Giancarlo Guizzardi     (1M2AAAV)

Ali Hashemi: google-doc of the developing communique draft is at:     (1M2AAAW)

Ali Hashemi: Please note - anyone with this link can edit the document (while we are in-session now)     (1M2AAAY)

Peter P. Yim: @Henson, @Matthew - the figures are now in - see:     (1M2AAAZ)

Trish Whetzel: Regrets, I need to leave the call now.     (1M2AAAAB)

Nicola Guarino: Ontological analysis as enabler of good modeling. I endorse this very much. Very     (1M2AAAAC)

crisp statement.     (1M2AAAAD)

Nicola Guarino: (who said that?) ... [it was Henson Graves and Matthew West citing that as being among     (1M2AAAAE)

the track-1&2 key conclusions; the statement was reiterated by session co-chair Todd Schneider just     (1M2AAAAF)

Steve Ray: +1 on Nicola's statement     (1M2AAAAI)

Cory Casanave: We should not differentiate modeling and ontological analysis, ontological analysis     (1M2AAAAJ)

should be positioned as part of modeling and one that is emerging as best practice. The precise     (1M2AAAAK)

modeling encompassing ontological analysis is a key enabler to the model driven approach Steve     (1M2AAAAL)

identified.     (1M2AAAAM)

Mary Brady: Regrets...I too have to leave.     (1M2AAAAN)

Peter P. Yim: I just want to emphasize that some statements (or recommendations) made (say, by panelists     (1M2AAAAO)

or even in the syntheses) are context sensitive. If we don't have the luxury (say, limited by     (1M2AAAAP)

document length constraints) in the synthesis write-ups and/or the communique to provide those     (1M2AAAAQ)

context, we should avoid citing them out of context.     (1M2AAAAR)

Mike Bennett: Cross Track X1 (Ontology Quality), the Google Doc seems to incorporate our community     (1M2AAAAS)

input page and not our track champions' synthesis page.     (1M2AAAAT)

Henson Graves: @amanda, there are well developed methods for validating models, e.g., but test.     (1M2AAAAU)

Presumably these methods could be used to test ontologies. also you could build on Nicola's notion     (1M2AAAAV)

of ontology correctness     (1M2AAAAW)

Amanda Vizedom: @henson, yes, and there are even techniques for unit testing, and various researchers     (1M2AAAAX)

have been developing more quantitative measures of other ontology characteristics that may or may     (1M2AAAAY)

not be applicable to particular cases... and there are many techniques for in-use testing and domain     (1M2AAAAZ)

expert validation that are not well documented. That's one step; finding more ways to streamline     (1M2AAAAAA)

and/or automate is another.     (1M2AAAAAB)

Doug Foxvog: @Amanda: Could you provide a link to methods/tools for validating ontology quality that     (1M2AAAAAC)

you were referring to? Are you referring to tools such as OntoClean?     (1M2AAAAAD)

Ali Hashemi: @Doug - this probably isn't the same as what Amanda suggests, but this is also relevant:     (1M2AAAAAE)

Amanda Vizedom: @Doug, I was mostly talking about the need to document approaches to evaluation, so     (1M2AAAAAG)

naturally I cannot provide links. But the reference library has a good start for discovery of some     (1M2AAAAAH)

of what is documented.     (1M2AAAAAI)

Bobbin Teegarden: Something about quality and requirements sometimes missed: if the goal is to tune     (1M2AAAAAJ)

the current system, quality/requirements are important; but if the goal is to use modeling to do     (1M2AAAAAK)

possibility' thinking, integrate newness, or get out of the box and design a future system or     (1M2AAAAAL)

enhancement, it's more a creative sketching activity and 'quality' is more of an inhibitor,     (1M2AAAAAM)

requirements are highly conceptual... Is this worth saying?     (1M2AAAAAN)

Amanda Vizedom: @Bobbin- Conceptual requirements are still requirements! But more generally, I'd say     (1M2AAAAAO)

that this is part of the way that requirements vary with usage. And as a reminder, by "quality" here     (1M2AAAAAP)

we are limiting ourselves to the engineering sense: the quality of something is the degree to which     (1M2AAAAAQ)

it meets requirements. So, if some characteristic (computational properties, reusability,     (1M2AAAAAR)

consistency with X,....) isn't a requirement of the usage, it shouldn't be part of the quality     (1M2AAAAAS)

measurement for this usage. What we need is better, explicit, and well-grounded understanding of     (1M2AAAAAT)

what requirements go with what usages!     (1M2AAAAAU)

Cory Casanave: don't know why my call dropped!     (1M2AAAAAV)

Henson Graves: [ref. Anatoly's point about "metamodelling = ontologizing"] @anatoly, I agree with you     (1M2AAAAAW)

Mike Bennett: Nicola is making a very important point here: metamodels and ontologies are not in any     (1M2AAAAAX)

way the same thing.     (1M2AAAAAY)

Steve Ray: Agree with Nicola. Metamodelling would refer to M2. Modeling would be M1.     (1M2AAAAAZ)

Henson Graves: @steve, an auto is M0, the model is M1, and the metamodel for autos can be at M2     (1M2AAAAAAA)

Steve Ray: [ref. Anatoly's remark that Nicola's rejection of "metamodels=ontologies" is possibly     (1M2AAAAAAC)

related to "presentation versus representation"] Nicola is not talking about presentation versus     (1M2AAAAAAD)

representation.     (1M2AAAAAAE)

Henson Graves: @nicola, the conceptualizations and patterns can be represented within metamodel. the     (1M2AAAAAAF)

model of a system is an instance of the metamodel of a system as a pattern     (1M2AAAAAAG)

Matthew West: Ontology is useful at each (meta) level, and in distinguishing between the levels.     (1M2AAAAAAH)

Nicola Guarino: At every modeling level there is a corresponding (often implicit) ontology. Ontology     (1M2AAAAAAI)

does not just belong to the meta level     (1M2AAAAAAJ)

Ali Hashemi: +1 to Nicola's point     (1M2AAAAAAK)

Steve Ray: @Nicola: Also agreed. I don't think ontology is better suited for one metal level or     (1M2AAAAAAL)

another. It is orthogonal to the metal level. It's just a better way to model.     (1M2AAAAAAM)

Cory Casanave: @Steve +1 - semantic modeling at all levels!!     (1M2AAAAAAN)

Matthew West: @Ali and Todd: [ref. Todd suggesting to do some real time cut-and-paste into the     (1M2AAAAAAO)

developing communique draft] Please do not do that. We have provided input that was roughly in the     (1M2AAAAAAP)

order of the outline, just take it offline.     (1M2AAAAAAQ)

Peter P. Yim: +1 on what Matthew West is suggesting - that the lead editors should just make the calls     (1M2AAAAAAR)

and come up with a first draft based on what the champions have turned in     (1M2AAAAAAS)

Matthew West: It looks like you already have our stuff in there.     (1M2AAAAAAT)

Peter P. Yim: +1 on Steve's remark about clarifying "Current State" as being "Current state of the     (1M2AAAAAAU)

practice" vs. "state of the art"     (1M2AAAAAAV)

Steve Ray: Absolutely agree with what Henson is saying     (1M2AAAAAAW)

Peter P. Yim: @Henson - well said - can you document that on the chat, please     (1M2AAAAAAX)

Ali Hashemi: [documenting what Henson just said ...] Shift towards explicit semantics ... from     (1M2AAAAAAY)

informal modeling to modeling in formal languages ... to underpin modeling languages w/ explicit     (1M2AAAAAAZ)

semantics ... to understand the underlying ontology of the elements of the languages     (1M2AAAAAAAA)

Steve Ray: Well defined semantics without knowing what the context is?     (1M2AAAAAAAD)

Nicola Guarino: ... and there is also a shift from just using *ontologies* (as useful engineering     (1M2AAAAAAAE)

artefacts) toward using *ontological analysis* (as a methodology which helps understanding and     (1M2AAAAAAAF)

disentangling the complexity of big systems)     (1M2AAAAAAAG)

Giancarlo Guizzardi: @HensonGraves: Yes. I agree with that point. Formal characterization should     (1M2AAAAAAAI)

reflect ontological distinctions. Formal semantics cannot guarantee quality per se. Logics (or any     (1M2AAAAAAAJ)

piece of mathematics for that matter) does not care what we do with it and, thus, cannot itself     (1M2AAAAAAAK)

fully constrain the possible interpretations of a model (and a metamodel) to the intended ones     (1M2AAAAAAAL)

Giancarlo Guizzardi: @Nicola: Fully agree with that.     (1M2AAAAAAAM)

Anatoly Levenchuk: @Nicola not ontological analysis but ontology engineering (like requirement     (1M2AAAAAAAN)

engineering and systems architecture engineering along with requirement analyses etc. as small part     (1M2AAAAAAAO)

of engineering thing)     (1M2AAAAAAAP)

Mike Bennett: Apologies, I have to drop off now.     (1M2AAAAAAAQ)

Peter P. Yim: "inferencing" helps make sense of "big data"     (1M2AAAAAAAR)

Peter P. Yim: ontological engineering helps augment humans in dealing with "big data" by off-loading a     (1M2AAAAAAAS)

lot of the work to machines     (1M2AAAAAAAT)

Matthew West: @Peter: Yes, seeing how ontology can help to automate mundane but necessary activity.     (1M2AAAAAAAU)

Terry Longstreth: Ontological analysis requires a canonical methodology, which may equate to     (1M2AAAAAAAV)

ontological engineering, but I think should be broader     (1M2AAAAAAAW)

Anatoly Levenchuk: @peter better ontology engineering (not ontological). We then have ontology as     (1M2AAAAAAAX)

explicit engineering artifact with life cycle, practices (like analysis, management etc.).     (1M2AAAAAAAY)

Nicola Guarino: Thank for you efforts, Todd & Ali!     (1M2AAAAAAAZ)

Ali Hashemi: re. "Reference List" see -     (1M2AAAAAAAAB)

Amanda Vizedom: re. "Reference List" content page on the wiki is at -     (1M2AAAAAAAAD)

Cory Casanave: How wide or narrow do we consider "inferencing", production of derivative information     (1M2AAAAAAAAF)

from models is done a lot, inference is more identified with FOL     (1M2AAAAAAAAG)

Peter P. Yim: @Cory - not necessarily, even simple inferences (say, applying modus ponens) can prove to     (1M2AAAAAAAAH)

Cory Casanave: @Peter - I agree but that may not be the interpretation of readers     (1M2AAAAAAAAJ)

Peter P. Yim: @Cory - guess we (the lead editors) will just have to word it properly to make sure that     (1M2AAAAAAAAK)

we are looking at a spectrum of possibilities     (1M2AAAAAAAAL)

Cory Casanave: @Peter - good, but not easy!     (1M2AAAAAAAAM)

Giancarlo Guizzardi: Folks. I have to drop off now. thanks for all the effort. bye     (1M2AAAAAAAAN)

Peter P. Yim: Bye, Giancarlo ... thanks for joining us today!     (1M2AAAAAAAAO)

Nicola Guarino: I have to go as well. Bye bye folks, good session!     (1M2AAAAAAAAP)

Peter P. Yim: great session ... lots discussed and done!     (1M2AAAAAAAAQ)

Peter P. Yim: Ali says: we will be publishing a draft of the communique the day before our session next     (1M2AAAAAAAAR)

Peter P. Yim: -- session ended: 11:23am PDT --     (1M2AAAAAAAAT)

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

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

Audio Recording of this Session     (1N)

Additional Resources     (1O)

For the record ...     (1O7)

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

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