From OntologPSMW

Jump to: navigation, search
[ ]


Contents

Overview of Semantic Integration - Thu 2016-02-18     (1)

Abstract     (1B)

Our goal is to build a common framework which will facilitate discussions regarding the role of ontologies within semantic interoperability ecosystems.     (1B1)

We will discuss themes, models, processes, functionality, considerations and measures which shed light on or help to communicate the Semantic Interoperability Ecosystem to a broader audience.     (1B2)

We will purposely focus on the role of ontologies within these frameworks. Examples will be used to illustrate our points.     (1B3)

It is hoped that the results of this session will help to frame and target the discussion in the domain-specific tracks to follow in the coming weeks. Together with findings from previous summits, this framework will provide a foundation and help direct conversation.     (1B4)

Agenda     (1C)

  • Dial-in:     (1D4)
    • Phone (US): +1 (425) 440-5100 ... (long distance cost may apply)     (1D4A)
    • Skype: join.conference (i.e. make a skype call to the contact with skypeID="join.conference") ... (generally free-of-charge, when connecting from your computer ... ref.)     (1D4B)
      • when prompted enter Conference ID: 843758#     (1D4B1)
      • Unfamiliar with how to do this on Skype? ...     (1D4B2)
        • Add the contact "join.conference" to your skype contact list first. To participate in the teleconference, make a skype call to "join.conference", then open the dial pad (see platform-specific instructions below) and enter the Conference ID: 843758# when prompted.     (1D4B2A)
      • Can't find Skype Dial pad? ...     (1D4B3)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1D4B3A)
        • 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.)     (1D4B3B)
    • 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").     (1D6A)
    • 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.     (1D6B)
    • thanks to the soaphub.org 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) summit_20160218@soaphub.org ... Handy for mobile devices!     (1D6C)
  • Discussions and Q & A:     (1D7)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1D7A)
    • 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.)     (1D7B)
    • 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.)     (1D7C)
    • 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.)     (1D7D)
  • RSVP to gruninger@mie.utoronto.ca with your affiliation appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the community already.)     (1D9)
  • This session, like all other Ontolog events, is open to the public. Information relating to this session is shared on this wiki page.     (1D10)
  • 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.     (1D11)

Proceedings     (1E)

[12:26] Mark Underwood: Hi All. Correction from last week: Hashtag (it's shorter) is #ontolog; use Tweetchat or equivalent to save rekeying it     (1E2)

[12:29] ToddSchneider: Agenda     (1E6)

[12:31] BrandonWhitehead: Hello all     (1E9)

[12:32] Donna Fritzsche: we will start in a few minutes     (1E10)

[12:36] Krzysztof Janowicz: Sorry, I assumed we do this in a panel style this time and only provided the 5-7 slides we were asked to. Thus, I will talk for like 5-10min not 20.     (1E12)

[12:36] ToddSchneider: Krzysztof, no problem.     (1E13)

[12:40] Donna Fritzsche: Connection Machine languages ---> not unlike map reduce/hadoop     (1E14)

[12:45] Donna Fritzsche: John - the venn diagram you shared is very similar to the IA venn diagram - created from a User Experience Design point of view. (Rosenfeld and Morville)     (1E15)

[12:54] MikeBennett: Interoperable Knowledge Representation for Intelligence Support (IKRIS)     (1E16)

[12:54] Gary Berg-Cross: Interoperable Knowledge Representation for Intelligence Support (IKRIS) as on John's slide.     (1E17)

[12:56] Gary Berg-Cross: @John What tools exist for modeling with and using IKL?     (1E18)

[12:57] Donna Fritzsche: IKRIS reference     (1E20)

[13:05] ToddSchneider: The NCOIC SCOPE Model for Interoperability provides a more nuanced examination of interoperability: ncoic.org/images/technology/SCOPE_MODEL_VER1.0.pdf     (1E21)

[13:10] Donna Fritzsche: "graceful degradation of services"     (1E22)

[13:10] LeoObrst: Just joining. Sorry for being late.     (1E23)

[13:12] Donna Fritzsche: @todd - service level agreements - context and semantic explicit     (1E24)

[13:15] ToddSchneider: Operational contexts need to be examined and made explicit during design time, not after the fact.     (1E26)

[13:15] ChristiKapp: Difficult to hear for some reason     (1E27)

[13:16] Donna Fritzsche: @todd - whose design time - which project's design time?     (1E28)

[13:17] ToddSchneider: Donna, that's part of the examination process.     (1E29)

[13:17] ChristiKapp: Can it also scale to other types of vehicles other than automobiles and trucks?     (1E30)

[13:21] LeoObrst: IKRIS: see Pat Hayes' site at http://www.ihmc.us/users/phayes/ikl/guide/guide.html.     (1E31)

[13:23] ToddSchneider: Lalit, 'Number of decision points should go down', why?     (1E32)

[13:26] ToddSchneider: The notion of 'intelligent information' goes beyond the current understanding of semantic interoperability. But semantic interoperability is a necessary prerequisite.     (1E33)

[13:28] Donna Fritzsche: less, but more useful decisions overall     (1E34)

[13:28] Donna Fritzsche: data mapping decisions would go down     (1E35)

[13:29] Donna Fritzsche: leave more room for engineering design decisions     (1E36)

[13:29] Mark Underwood: BOMS are a great use case - I think this needs more study as it is highly rule-governed and should be more amenable that is suggested by this talk     (1E38)

[13:29] JackRing: Frank Lillehagen's method of 'semantic zoom' and perspective views addresses many of Ford's concerns.     (1E39)

[13:30] Mark Underwood: (having coded a lot of BOM logic in the 90's by 'hand')     (1E40)

[13:30] ToddSchneider: Hans is on slide 2     (1E41)

[13:36] JackRing: Can engineers promote and facilitate human convergence?     (1E42)

[13:36] Mark Underwood: {My Earlier typo *than is suggested}     (1E43)

[13:37] Mark Underwood: Polzer: Embrace diversity "Silo Lives Matter"     (1E44)

[13:38] John Sowa: Diversity and heterogeneity are two of the major requirements by Hendler and Tim B-L.     (1E45)

[13:39] Donna Fritzsche: great full circle points     (1E46)

[13:39] John Sowa: The definition of silo: no tolerance for diversity.     (1E47)

[13:46] BobbinTeegarden: Is 'scope' the same as 'context'?     (1E48)

[13:46] ToddSchneider: Not exactly. Scope has context. Context has scope.     (1E49)

[13:47] MikeBennett: @Bobbin Context is where you start from and Scope is how far you go.     (1E50)

[13:48] BobbinTeegarden: How does the concept of scope handle dynamics (morphing environments)?     (1E51)

[13:50] MikeBennett: The audible scope of this call has increased again.     (1E52)

[13:50] Krzysztof Janowicz: (The expected call duration was set to 90min; thus I have to leave in like 5-10min; sorry for that)     (1E53)

[13:51] ToddSchneider: Krzysztof, have any questions for Hans?     (1E54)

[13:51] Donna Fritzsche: Thank-you Krzysztof!     (1E55)

[13:53] Krzysztof Janowicz: In the context of human bodies, the scope of 'size' is mm to meters (not miles).     (1E56)

[13:54] Gary Berg-Cross: At times this way of talking about "context" seems like the role of an item.     (1E57)

[13:55] BobbinTeegarden: So is perspective related to context, then?     (1E58)

[13:57] ToddSchneider: Is there a definition of 'context'?     (1E59)

[13:57] Donna Fritzsche: The syntax and construction rules for documents - has context embedded     (1E60)

[13:58] MikeBennett: A possible perspective: in human use of words, every use of every word has its own unique context (language games). For engineering purposes we want to constrain symbols in the model, to represent something within a defined context, to have a reusable meaning. To the extent we can capture the context as part of that model (e.g. Leg in transport versus derivatives trading), then the meaning is more clearly understood and can be referred to more widely. Does that make sense?     (1E61)

[14:00] LeoObrst: At Boeing, circa 1996-7, our BOM was realized in terms of CAD-CAM, and vast correlated databases, on top of which we made some strides towards ontologizing the design engineering process, as part of the MADESmart program. NIST folks will recall this.     (1E62)

[14:02] Mark Underwood: Leo- I wonder what the current state is . . . Will the BOMs be stuck in a noSQL or HDFS-like unstructured thing? Seems like a step back, eh?     (1E63)

[14:04] BobbinTeegarden: Maybe it's not a semantic problem with interoperability, but a syntactic (scope, context, perspective) based problem...     (1E64)

[14:06] LeoObrst: @Todd: International Classification of Diseases (ICD)-9 and ICD-10: http://www.cdc.gov/nchs/icd/icd9.htm, http://www.cdc.gov/nchs/icd/icd10cm.htm.     (1E65)

[14:07] ToddSchneider: Leo, thank you.     (1E66)

[14:07] Mark Underwood: It troubles me that the conversation occurs completely independent of the domain-specific software engineering initiatives, e.g, Microsoft's Domain Specific Modeling http://bit.ly/1RRuD6V     (1E67)

[14:07] LeoObrst: @Mark: good question. I've not been involved in manufacturing systems for quite some time.     (1E68)

[14:08] Mark Underwood: No ICD, no pay     (1E69)

[14:09] John Sowa: The words scope, context, and perspective belong to an ontology for classifying ways that people relate to the world and to each other.     (1E70)

[14:09] MikeBennett: @John +1     (1E71)

[14:10] MikeBennett: Gary you're unmuted again - very noisy line     (1E72)

[14:10] Gary Berg-Cross: i would just add some context for ontologies can be set by using Competency Questions that discuss the types of things the ontology knows about and its domain and range.     (1E73)

[14:10] Mark Underwood: John: "Scope" is heavily overloaded in s/w engineering, sort of an unforunate invocation     (1E74)

[14:11] MikeBennett: To some extend scope and context (along with granularity etc.) relate to the ontological commitment of a given ontology.     (1E75)

[14:12] Mark Underwood: @Donna I suspect developers would say usability is poor, i.e., not "API-first"     (1E76)

[14:12] BobbinTeegarden: @Donna the visual gets to the real 'context', the right brain conceptual graph that encompasses the whole context. SMEs immediately grok the visual ontology, and start to make it theirs, modify it according to their scope and context. The visual part is key.     (1E77)

[14:13] MikeBennett: Presumably the extent to which different ontologies have similar ontological commitments, scope, context etc. (or explicit inclusion of context information), will determine the extent to which they can be used together?     (1E78)

[14:13] Donna Fritzsche: yes - Bobbin! visuals are key for many stakeholders. I think it has been a problem in the past.     (1E79)

[14:15] Donna Fritzsche: meaning that I think a lack of visual representations for context has been a problem. SME's need the birds-eye view. Some of them will naturally be visual thinkers.     (1E81)

[14:15] LeoObrst: Open Ontology Repository (OOR) effort, which was subject of Ontology Summit 2008. Still a few such: COLORES, OntoHub, etc. Also: BioPortal is another repository.     (1E82)

[14:15] Mark Underwood: In some prelim outreach by Elsevier who has surveyed me on this topic, there's movement to develop ontology-based classifications to accompany academic pubs     (1E83)

[14:16] Mark Underwood: Such as what Watson is doing after-the-fact for the ACM digital lib     (1E85)

[14:18] Mark Underwood: Recalling my complaint about "scope," the same applies to "context" - Take a Windows dump and you get one such meaning     (1E86)

[14:19] Gary Berg-Cross: Ontologies may have implicit scope but still may be understood by different people based on their role relations to the domain being formalized.     (1E87)

[14:19] ToddSchneider: Ravi, yes does help constrain interpretation.     (1E88)

[14:19] MikeBennett: To Ravi's point, Sign Language (e.g. ASL) also makes extensive use of context, I believe.     (1E89)

[14:20] RaviSharma: context notions are as John said language dependent it also provides brevity     (1E90)

[14:20] ToddSchneider: Oops left out the subject of last post: yes conetxt does help constrain interpretation.     (1E91)

[14:21] BobbinTeegarden: In terms of contexts in scope, does the context change with level of perspective abstraction, the observed 'reality' change as it does in fractal levels of abstraction? Implications for ontologies?     (1E92)

[14:22] Donna Fritzsche: context notions are also culturally dependent     (1E93)

[14:22] TerryLongstreth:     (1E94)

He drew a circle that shut me out-     (1E95)

Heretic , rebel, a thing to flout.     (1E96)

But love and I had the wit to win:     (1E97)

We drew a circle and took him In !     (1E98)

[14:23] Mark Underwood: *** To those of you on Twitter, if you follow @OntologySummit, we will follow you back and this will help promote our work here     (1E99)

[14:24] MikeBennett: I think there are 2 approaches to context: Making context available to a human reader - which is only useful for a human reader; and context embedded in the ontology in some way such that other systems can appropriately consume that data (and know when not to). In reality there will be a trade-off between the two I think.     (1E100)

[14:24] BobbinTeegarden: @Terry heart!     (1E102)

[14:26] TerryLongstreth: @Bobbin, thanks. I was trying to emphasize Hans' notion that scopes are bounded, but much of our work in NCOIC is finding where those boundaries can be moved.     (1E103)

[14:27] LeoObrst: One can have "ontological views", which act as perspectives/contexts into an ontology. These can also be linked to specific vocabularies (lexical resources). Also, one can attempt to model "situations" as complex contexts, then compose them.     (1E104)

[14:27] LeoObrst: Thanks, all.     (1E105)

[14:28] Mark Underwood: +1 See you next week- socialize as you can     (1E107)

[14:29] ToddSchneider: Session ends 14:29 ET     (1E108)

[14:29] Donna Fritzsche: Thank-you all! Have a great week.     (1E109)

[14:29] KenBaclawski: The meeting page for the next session is http://ontologforum.org/index.php/ConferenceCall_2016_02_25     (1E110)

Session Recording     (1F)

Attendees     (1G)