From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2016: Semantic Integration for Geographically Distributed Sensor and Control Systems - Thu 2016-03-31     (1)

Abstract     (1B)

  • Context: A general belief that there is a convergence on standards for interoperability components, including catalogs, vocabularies, services and information models. The application of ontologies to provide semantics for this interoperability has been an active area of research in several disciplines including the GeoSciences where it now plays a central role in tackling the problems of semantic heterogeneity.     (1B1)
  • Perception: In an era of Big Data and Big Science diverse GeoScience data are increasingly being collected across many domain areas and wide spatial scales.     (1B2)
    • Increasingly interdisciplinary work requires some way of efficiently handling system, service and data heterogeneity. Valid and formal semantics is perceived to be a way of addressing these challenges.     (1B2A)
    • The GeoSciences are broadly defined to include not only the Earth Sciences but also geographically distributed sensor networks, such as air traffic control and power grids.     (1B2B)
  • Motivation: Report on activities such as NSF’s EarthCube that feature different GeoScience domains working on semantic interoperability issues to promote understanding of the state of the art across different approaches and what challenges remain:     (1B3)
    • What are the ranges of GeoScience ontologies used across the domain?     (1B3A)
    • How have ontologies been enhanced and expanded for use and reuse?     (1B3B)
    • What issues of knowledge building and reuse have been noted?     (1B3C)
    • What new standards might be     (1B3D)

Agenda     (1C)

Introduction     (1C1)

Speakers     (1C2)

  • Steve Ray (Carnegie Mellon Silicon Valley) Semantic Interoperability Issues for the Smart Grid slides     (1C2A)
  • [Marshall Ma] (RPI) SEM+: a tool for concept mapping in geoscience slides     (1C2B)
  • Shirly Stephen and Torsten Hahmann (University of Maine) "Semantic Alignment of the Groundwater Markup Language with the Emerging Reference Hydro Ontology HyFO" slides     (1C2C)
    • Abstract: A set of different ontologies and data models, including a number of standards, exist for the hydrology domain. While these have achieved some level of technical interoperability for water data integration and exchange, semantic integration of water data remains a challenge, for a number of reasons. The ontologies and data models (1) are mostly fragmented and disconnected, (2) lack foundational grounding, and (3) semantically differ in how hydrological and hydrogeological terms are used. We investigate the use of an emerging, rigorously axiomatized reference ontology for the hydro domain, the Hydro Foundational Ontology (HyFO), to overcome these heterogeneities by integrating the existing hydro ontologies and data models with HyFO. HyFO formalizes general concepts that are central to water storage below and above the ground surface through rigorous and detailed axiomatization in first-order logic. This work presents first results of integrating the Ground Water Markup Language (GWML2), a conceptual model specific to groundwater monitoring, with HyFO by grounding GWML2 concepts logically in HyFO’s concepts and relations. More generally, this work demonstrates how to effectively utilize formal ontological analysis and rigorous axiomatizations in the development and integration of geoscience ontologies.     (1C2C1)

Synthesis Page     (1C3)

More coming soon.....Please contribute to the synthesis page at Talk:ConferenceCall_2016_03_31.     (1C3A)

  • 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").     (1D5A)
    • 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.     (1D5B)
    • 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!     (1D5C)
  • Discussions and Q & A:     (1D6)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1D6A)
    • 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.)     (1D6B)
    • 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.)     (1D6C)
    • 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.)     (1D6D)
  • RSVP to 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.)     (1D8)
  • This session, like all other Ontolog events, is open to the public. Information relating to this session is shared on this wiki page.     (1D9)
  • 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.     (1D10)

Proceedings     (1E)

[12:29] gary berg-cross: Mike will be late but Ken is doing it all today.     (1E1)

[12:31] Donna Fritzsche: its spring break for many in the US     (1E2)

[12:35] MarshallMa: join.conference is working on skype     (1E3)

[12:35] MarshallMa: when prompted enter Conference ID: 843758#     (1E4)

[12:40] Donna Fritzsche: Note: Important Concept - Bridging concepts even in the same domain (Ken B)     (1E5)

[12:43] ToddSchneider: Mark, started on the synthesis?     (1E6)

[12:47] gary berg-cross: @Todd, Yes we have started on a Synthesis. We have notes at     (1E7)

[12:49] ToddSchneider: Standards represent closed domains. Interoperability is about crossing domain boundaries.     (1E8)

[12:51] Donna Fritzsche: great interface Steve - we need more transitional UIs like this. (slide 6)     (1E9)

[12:52] ToddSchneider: Has this been applied to the UML specification?     (1E10)

[12:52] Donna Fritzsche: UIs - to take advantage of the power of OWL/Sparql queries w/o learning the nuances of syntax/etc     (1E11)

[12:53] Ruth: This is exactly what I've been calling for web service specifications (e.g., OGC W*S, OPeNDAP, OAI-PMH, etc.)     (1E12)

[12:53] Donna Fritzsche: Ruth - I don't understand your acronyms - can you explain (briefly)     (1E13)

[12:53] Ruth: that way we might some day get the same type of web service implemented the same way by two different repositories     (1E14)

[12:54] Donna Fritzsche: +1 @ruth     (1E15)

[12:54] Ruth: those were all web service names common in the Earth sciences     (1E16)

[12:54] Donna Fritzsche: thank-you     (1E17)

[12:57] Mark Underwood: "Explaining" can be important. @TayAndYou could have used that.     (1E18)

[13:02] ToddSchneider: Steve, did the process of representing the 'rules' require changes to the ontology (to facilitate rule representation)?     (1E19)

[13:04] ChristopherSpottiswoode: Steve, what would need to be added to the OWL model to enable a simulation of a real system?     (1E20)

[13:06] LeoObrst: @Steve: did you use a NL->formal rule translator, e.g., a controlled English? Were these SPIN rules? How do you like SPIN rules?     (1E21)

[13:06] ToddSchneider: Steve, this is a great use of semantic technologies and particularly reasoning.     (1E22)

[13:10] Donna Fritzsche: Maybe need rule-driven State Machine for running rules (SPIN)     (1E23)

[13:13] SteveRay: @Leo: These were SPIN rules. No controlled English. They work OK. I do find that many of the rules require condition checking to make sure they don't redundantly fire. But generally they are tractable.     (1E24)

[13:14] SteveRay: @Christopher: To simulate a real system, you would need to think about constantly changing values. In our current work, we are basically testing a static snapshot. With changing values, one possibility is to start using things like "Magic properties" which are computed on the fly.     (1E25)

[13:17] SteveRay: @Donna: I agree. One thing I'm stumbling on is how to know when the reasoning engine is finished, so that I can change state. In the TopBraid environment, the only thing I can think of right now is to embed the system inside a SPARQLMotion script. I'd rather not add that complexity, but I may have to go there.     (1E26)

[13:20] Donna Fritzsche: @Marshall - have you looked at Ross Quinlan's work on ID3?     (1E27)

[13:22] ChristopherSpottiswoode: Steve and Donna: By calculating timesliced value-sets for successive moments in time, you get a series of states that together are in effect equivalent to a state machine's behavior. Or so it seems to me, in a rather off-the-cuff way.     (1E28)

[13:24] Donna Fritzsche: @christopher - I am pointing to more of a context-driven control of the rule processing. To Todds point- this could become an ontology of its own.     (1E29)

[13:27] ChristopherSpottiswoode: Donna, yes indeed. The context would provide the initial values for a simulation, the model would provide rates-of-change, in their turn according to the context allowing the calculation using the model of next consistent set of values.     (1E30)

[13:29] BobbinTeegarden: An ontology that includes/is based on process (and the dependent information modeled around the process) would enable a single view of process and data. If one could then use something (like SPARQL with an 'execute' extension) one could create 'executable' ontologies. Referring back to Steve's problem, if the processes were composed of sub-processes, one could get to modeling process in the large, not just sequences of rules (process in the small).     (1E31)

[13:30] Donna Fritzsche: @Marshall - great work - you might also look for old papers by Craig Stanfill/David Waltz for similar ideas (Towards memory-based reasoning).     (1E32)

[13:31] ChristopherSpottiswoode: Bobbin - yes!     (1E33)

[13:31] Donna Fritzsche: Agreed Bobbin.     (1E34)

[13:32] ToddSchneider: Marshall, what is the source of 'vocabularies' used for your testing?     (1E35)

[13:32] Donna Fritzsche: Christopher - are you solving the simulation problem as opposed to the process problem - while similar - I think they are different.     (1E36)

[13:33] ToddSchneider: Marshall, how sensitive is your process to the representation of the vocabularies (into an ontology language)?     (1E37)

[13:34] gary berg-cross: Marshall, thanks for a clear presentation. Can you provide a link to the article?     (1E38)

[13:35] ChristopherSpottiswoode: Donna, good question. But sorry I have to log off now. I'll follow up in another way - Thanks!     (1E39)

[13:36] Donna Fritzsche: Thanks!     (1E40)

[13:39] MarshallMa: @DonnaFritzsche: ID3 is very relevant. Thanks for the information!     (1E41)

[13:39] MarshallMa: @DonnaFritzsche: and the papers of Craig and David     (1E42)

[13:40] MarshallMa: @ToddSchneider: We tested the method with vocabulary terms from IOOS Platform Vocabulary, IOOS Parameter Vocabulary, MMI Platform Ontology, Climate and Forecast (CF) Standard Names Parameter Vocabulary and DRDC Atlantic NADAS Parameter Codes     (1E43)

[13:44] MarshallMa: @ToddSchneider:"how sensitive is your process to the representation of the vocabularies" <-- Do you mean the properties used in encoding vocabularies and the property mapping in the computation? Some property mapping between OWL, SKOS, and RDFS is pre-assigned in the process. But for some user defined properties there could be an extra step to first identify the property mapping (actually you can also call it ontology mapping).     (1E44)

[13:45] MarshallMa: @Gary: Details of the paper: Zheng, J., Fu, L., Ma, X., Fox, P., 2015. SEM+: tool for discovering concept mapping in Earth science related domain. Earth Science Informatics 8 (1), 95-102.     (1E45)

[13:49] ToddSchneider: Marshall, yes (i.e., properties used in 'encoding' (aka representation) ...).     (1E46)

[13:53] Donna Fritzsche: Shirly - can you comment on what your next steps might be?     (1E47)

[13:55] Donna Fritzsche: Thank-you     (1E48)

[13:56] MarshallMa: @ToddSchneider: A property mapping step is necessary. Some properties can be pre-matched such as rdfs:label and rdfs:comments. But use-defined properties always need some extra attention.     (1E49)

[13:58] ToddSchneider: Marshall, have you compared results using different encodings/representations to try to identify biases?     (1E50)

[13:58] gary berg-cross: @Shirly & Torsten Just an observation that you have interesting, specific relations such as inter-granular constituent.     (1E51)

[14:00] MarshallMa: Some properties can be pre-matched such as rdfs:label and rdfs:comments <- I mean to match s-p-o triples of rdfs:label of two concepts, not to match rdfs:label to rdfs:comments     (1E52)

[14:00] Mark Underwood: Shirly / Torsten - Are there issues that arise b/c the ontologies model fluids vs. static objects, e.g, "contamination" as applies to groundwater     (1E53)

[14:00] Mark Underwood: I think you answered it     (1E54)

[14:00] Donna Fritzsche: good question michael     (1E55)

[14:01] MichaelGruninger: @Shirly: What were the benefits of using an upper ontology (in your case DOLCE)? Did it help to alleviate problems with semantic integration, or did it actually lead to additional problems because you had to integrate all of the other ontologies with DOLCE?     (1E56)

[14:01] ToddSchneider: Shirly & Torsten, did you import DOLCE or just use it for alignment?     (1E57)

[14:03] gary berg-cross: @Torsten Are you aware of other "Reference" ontologies in the GeoSciences or SensorNet domains?     (1E58)

[14:05] gary berg-cross: @Torsten Do you find DUL useful?     (1E59)

[14:09] Mark Underwood: Discussion begun by Michael re: role of upper ontologies; @SteveRaySteve senses cultural challenges ("just now acclimating to XML") . . .     (1E60)

[14:09] ToddSchneider: Michael, is your question more about use/application of ontological analysis to disambiguate notions?     (1E61)

[14:10] Donna Fritzsche: Or a toolkit to base the design on moving forward.     (1E62)

[14:10] TorstenHahmann1: @Gary: we haven't used it at all and didn't so far find a need for it since we are only talking about static physical space. That may change in the future with the integration of flow patterns     (1E63)

[14:11] Donna Fritzsche: @Steve - would it make sense that you need a lego-like tool kit of common reusable memes (actor, role,device..).     (1E64)

[14:11] Donna Fritzsche: It seems that everyone reinvents that set of wheels     (1E65)

[14:12] Mark Underwood: Topic is highly relevant in IoT integration. Talk earlier today included detailed challenges of integrating geospatial data from devices bus / consumers buy @ HomeDepot, then integrate w/ enterprise apps     (1E66)

[14:13] gary berg-cross: @Steve As I recall in a previous presentation of an earlier Summit, you talked about Bridge Ontologies.     (1E67)

[14:14] TorstenHahmann1: @Gary: I agree with the need for documenting the benefits of using a reference ontology and/or a upper ontology. So far, we have primarily kept track of proposed revisions to GWML that are much better justified because of reasonable foundational distinctions in DOLCE/HyFO     (1E68)

[14:14] ToddSchneider: Donna, No. Providing a set of pre-defined notions (e.g., UML) only prolongs the use of a cookie cutter mentality and avoids the types of analyses that provide long term value.     (1E69)

[14:15] Donna Fritzsche: What it they were part of an ontology Todd - that was my intent     (1E70)

[14:15] Donna Fritzsche: Not sure what you meant     (1E71)

[14:15] ToddSchneider: The value of using upper ontologies has already been described in previous summits.     (1E72)

[14:16] Donna Fritzsche: But - then why are the questions still there. It does not seem to be solved.     (1E73)

[14:16] Donna Fritzsche: And also - please allow for alternate opinions.     (1E74)

[14:17] ToddSchneider: Donna, any ontology has a scope, assumptions, and possibly embedded biases. If these 'constraints' were made explicit so that potential users are aware of them, then I would agree. Otherwise, no.     (1E75)

[14:18] Donna Fritzsche: That was my intent Todd - do not know why you were so quick to jump on the no band-wagon.     (1E76)

[14:18] Mark Underwood: Rete? Really? :)     (1E77)

[14:18] TorstenHahmann1: I think within our community the benefits are known, but not beyond our community. I do think that concrete examples (as opposed to benefits at a general level) would really help make a more tangible case     (1E78)

[14:18] gary berg-cross: A topic for next year's Summit "Reasoning over Ontologies."     (1E79)

[14:19] Donna Fritzsche: This seems to be part of Semantic Interoperability to me - but a specific case     (1E80)

[14:20] Donna Fritzsche: Agreed that it would be a good topic for future thought/summit     (1E81)

[14:23] gary berg-cross: John Sowa like Riple Down rules for AI Richards, Debbie. "Two decades of ripple down rules research." The Knowledge Engineering Review 24.02 (2009): 159-184.     (1E82)

[14:24] Mark Underwood: @Steve - despite your reservations, that catalog/agenda of issues & tradeoffs is where many of (us) practitioners are struggling to find a way to steady the ontology role in SDLC     (1E83)

[14:24] TorstenHahmann1: We also employ the reference ontology HyFO as a bridge ontology (bridging more focussed hydro ontologies)     (1E84)

[14:25] SteveRay: SDLC?     (1E85)

[14:25] ToddSchneider: Donna, I continually run into situations where people have expectations of interpretations of natural language terms that are not consistent nor complete for the application in which they want to use them - they have not analyzed the situation sufficiently (also I get stuck trying to fit things into UML constructs that really don't fit).     (1E86)

[14:25] ToddSchneider: Thank you all. have to go. Cheers.     (1E87)

[14:26] Donna Fritzsche: Thanks for your input Todd - and the follow-up.     (1E88)

[14:28] gary berg-cross: Ontohub is one such repository     (1E89)

[14:28] SteveRay: @Donna: To your comment at :11, that is exactly what the architecture committee in the smart grid world is seeking. At present, the four core concepts are Actor, Service, Contract, and "ServiceComposition". That last one is something I'm not very fond of, since it can be achieved with normal mereological relations.     (1E90)

[14:29] TorstenHahmann1: We plan on putting the formalized version of GWML into COLORE, another repository from the OOR initiative. HyFO is mostly available from there already.     (1E91)

[14:29] Donna Fritzsche: @Steve - thanks for additional info! I think its useful work.     (1E92)

[14:30] SteveRay: Thanks!     (1E93)

[14:30] Donna Fritzsche: Thank you all! Have a great week.     (1E94)

[14:31] TorstenHahmann1: Thanks Gary and Ken for organizing the track!     (1E95)

[14:37] Mark Underwood: Software Development Life Cycle SDLC     (1E96)

Attendees     (1F)

Audio Recording     (1G)