From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2014 session-12: Synthesis-II: Technical Tracks and Hackathon - Thu 2014-04-03     (1)

  • Summit Theme: OntologySummit2014: "Big Data and Semantic Web Meet Applied Ontology"     (1A)
  • Session Topic: OntologySummit2014 Synthesis-II on the Technical Tracks and the Hackathon     (1B)

Program:     (1D)

Abstract     (1M)

OntologySummit2014 Session-12: "Synthesis-II" - overview slides     (1M1)

This is our 9th Ontology Summit, a joint initiative by Ontolog, NIST, NCOR, NCBO, IAOA & NCO_NITRD with the support of our co-sponsors.     (1M2)

Since the beginnings of the Semantic Web, ontologies have played key roles in the design and deployment of new semantic technologies. Yet over the years, the level of collaboration between the Semantic Web and Applied Ontology communities has been much less than expected. Within Big Data applications, ontologies appear to have had little impact.     (1M3)

This year's Ontology Summit is an opportunity for building bridges between the Semantic Web, Linked Data, Big Data, and Applied Ontology communities. On the one hand, the Semantic Web, Linked Data, and Big Data communities can bring a wide array of real problems (such as performance and scalability challenges and the variety problem in Big Data) and technologies (automated reasoning tools) that can make use of ontologies. On the other hand, the Applied Ontology community can bring a large body of common reusable content (ontologies) and ontological analysis techniques. Identifying and overcoming ontology engineering bottlenecks is critical for all communities.     (1M4)

Ontology Summit 2014 will pose and address the primary challenges in these areas of interaction among the different communities. The Summit activities will bring together insights and methods from these different communities, synthesize new insights, and disseminate knowledge across field boundaries.     (1M5)

At the Launch Event on 16 Jan 2014, the organizing team has provided an overview of the program, and how we will be framing the discourse - namely, to pursue that along four different content tracks that address different aspects of the issue at hand.     (1M6)

In today's session, we will roll up what has transpired in the Ontology Summit 2014 proceedings so far, after two rounds of technical panel sessions that revolved around the four aspects, as designated in the foci for Tracks A, B, C & D, as well as the delivery of Six (6) Hackathon Projects (our Track E effort). Track champions will present the syntheses of the discourse of each of the four content tracks and a summary of the Hackathon effort. Write-ups of the syntheses will contribute to what will go into this year's Communique.     (1M7)

One of our co-lead Editors will then moderate an open discussion, among the Track Champions and All Participants, on how we can optimally fit the syntheses material into the adopted Communique outline, and aim towards arriving at consensus positions that we would want to assume in this year's communique, as a community.     (1M8)

More details about this Ontology Summit is available at: OntologySummit2014 (homepage for this summit)     (1M9)

Track Syntheses Material     (1M10)

Agenda     (1N)

OntologySummit2014 - Panel Session-12     (1N1)

  • Session Format: this is a virtual session conducted over an augmented conference call     (1N2)
  • 1. Opening and General assessment and what's next (co-chairs: Michael Grüninger, LeoObrst) [5 min.] ... [ slides ]     (1N3)
  • 2. Track Synthesis II (presentation of the interim deliverables by one of the co-champions of each track) [10 min/track]     (1N4)
    • 2.1 Track A: Common Reusable Semantic Content Synthesis-1 (GaryBergCross*, Andrea Westerinen, MikeBennett)     (1N4A)
    • 2.2 Track B: Making use of Ontologies: Tools, Services, and Techniques Synthesis-1 (ChristophLange*, AlanRector)     (1N4B)
    • 2.3 Track C: Overcoming Ontology Engineering Bottlenecks Synthesis-1 (MatthewWest*, Pascal Hitzler, KrzysztofJanowicz)     (1N4C)
    • 2.4 Track D: Tackling the Variety Problem in Big Data - Synthesis-I Synthesis-1 (AnneThessen*, KenBaclawski)     (1N4D)
  • 3. Summary Report from the (Track-E) Hackathon Projects (AnatolyLevenchuk*, DanBrickley) [10 min.]     (1N5)
  • 4. Q&A and Open Discussion: developing and building consensus on our Communique (moderators: Leo Obrst, MichaelGruninger) [~45 min.] ... please refer to process above     (1N6)
  • 5. Summary/wrap-up/announcements [5 min.]     (1N7)

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)

Chat transcript from room: summit_20140403     (1O2E)

2014-04-03 GMT-08:00 [PDT]     (1O2F)

[9:12] Peter P. Yim: Welcome to the     (1O2G)

Ontology Summit 2014 session-12: Synthesis-II: Technical Tracks and Hackathon - Thu 2014-04-03     (1O2H)

Summit Theme: Ontology Summit 2014: "Big Data and Semantic Web Meet Applied Ontology"     (1O2I)

Session Topic: Ontology Summit 2014 Synthesis-II on the Technical Tracks and the Hackathon     (1O2J)

Session Co-chairs: Dr. Leo Obrst and Professor Michael Grüninger     (1O2K)

- Track A: Common Reusable Semantic Content - Synthesis-II     (1O2O)

- Track B: Making use of Ontologies: Tools, Services, and Techniques - Synthesis-II     (1O2Q)

- Track C: Overcoming Ontology Engineering Bottlenecks - Synthesis-II     (1O2S)

- Track D: Tackling the Variety Problem in Big Data - Synthesis-II     (1O2U)

- Track E: A Summary Report on the Hackathon Projects, especially on what's pertinent to the Communique     (1O2W)

  • Dr. Leo Obrst (moderator) - Open Discussion on ideas to optimally fit the above material into the adopted     (1O2X)

Communique outline, and the positions we want to assume in this year's communique     (1O2Y)

Logistics:     (1O2Z)

  • (if you haven't already done so) please click on "settings" (top center) and morph from "anonymous" to your RealName;     (1O2AB)

also please enable "Show timestamps" while there.     (1O2AC)

(i.e. even if it says it is "offline," you should still be able to connect to it.)     (1O2AG)

VoIP line, etc.) either your phone, skype-out or google-voice and call the US dial-in number: +1 (206) 402-0100     (1O2AI)

... when prompted enter Conference ID: 141184#     (1O2AJ)

  • when posting in this Chat-room, kindly observe the following ...     (1O2AN)
    • whenever a name is used, please use the full WikiWord name format (every time you don't, some volunteer will have to make an edit afterwards)     (1O2AO1)
    • always provide context (like: "[ref. JaneDoe's slide#12], I think the point about context is great" ... rather than "that's great!"     (1O2AP1)

as the latter would mean very little in the archives.)     (1O2AQ)

the timestamp (in PST) of his/her post that you are responding to (e.g. "@JaneDoe [11:09] - I agree, but, ...")     (1O2AS)

    • use fully qualified url's (include http:// ) without symbols (like punctuations or parentheses, etc.) right before of after that URL     (1O2AT1)

[9:29] anonymous morphed into Carmen Chui     (1O2AAC)

[9:29] anonymous1 morphed into Siew Lam     (1O2AAE)

[9:32] Ed Bernot: Good day/night!     (1O2AAF)

[9:32] GaryBergCross: Hello, Track A is here...     (1O2AAG)

[9:33] anonymous1 morphed into Conrad Beaulieu     (1O2AAH)

[9:33] anonymous morphed into Les Morgan     (1O2AAI)

[9:34] anonymous morphed into Francesca Quattri     (1O2AAJ)

[9:36] anonymous morphed into Mark Linehan     (1O2AAK)

[9:37] anonymous1 morphed into Lamar Henderson     (1O2AAL)

[9:37] Peter P. Yim: == Michael Grüninger starts session on behalf of the co-chairs ... see slides under:     (1O2AAM)

[9:46] Alex Shkotin: If we split ontology to theory and model. Theory can't be Big. Model can.     (1O2AAO)

[9:48] anonymous morphed into Bobbin Teegarden     (1O2AAP)

[9:49] Frank Olken: Do we need to register for the face to face meeting of Ontology Summit 2014?     (1O2AAQ)

[9:59] Leo Obrst: @FrankOlken [12:49]: yes, see:     (1O2AAS)

[9:49] anonymous morphed into Joanne Luciano     (1O2AAU)

[9:51] Matthew West: Communique Outline: Barriers and Bottlenecks: I suggest adding opportunities for     (1O2AAV)

automation (a way of overcoming bottlenecks).     (1O2AAW)

[9:52] Michael Grüninger: @MatthewWest [9:51] yes, we should have a subsection on overcoming the bottlenecks     (1O2AAX)

[9:51] Peter P. Yim: == GaryBergCross presenting on "Common Reusable Semantic Content: Synthesis-II" on behalf of the Track-A co-champions ...     (1O2AAY)

[9:58] anonymous morphed into Dominique Mariko     (1O2AAZ)

[9:58] anonymous1 morphed into Calvin Liu     (1O2AAAA)

[10:00] Amanda Vizedom: Slide #9 Condition 2: that "standard metadata for reuse be defined" -- is     (1O2AAAB)

precisely the condition that the VOCREF hackathon aimed to address, by getting the foundations in     (1O2AAAC)

place of an open-source, collaboratively developed ontology of the wide range of metadata that     (1O2AAAD)

people may need in order to determine whether a given ontology (or other semantic resource) is     (1O2AAAE)

reusable for their purpose.     (1O2AAAF)

[10:02] GaryBergCross: @Amanda [10:00] comment - Great to know the hackathon will help contribute to     (1O2AAAG)

understanding on the ontology metadata.     (1O2AAAH)

[10:03] Amanda Vizedom: @Gary [10:02] We hope so!     (1O2AAAI)

[10:07] Andrea Westerinen: @AmandaVizedom [10:00] That is why I added the slide about VOCREF. Sorry     (1O2AAAJ)

that I was not online at the time. Blame Comcast :-)     (1O2AAAK)

[10:09] Amanda Vizedom: Andrea Westerinen [10:07] Gary was necessarily going very quickly & touched     (1O2AAAL)

really only on the meta-characteristics of the hackathon approach, not so much the content; I added     (1O2AAAM)

the comment at [10:00] just to supplement. :-)     (1O2AAAN)

[10:00] Peter P. Yim: == Christoph Lange presenting on "Making use of Ontologies: Tools, Services, and     (1O2AAAO)

Techniques: Synthesis-II" on behalf of the Track-B co-champions ...     (1O2AAAP)

[10:03] Peter P. Yim: @ChristophLange - [re: slide#2] I don't think we can equate "heavyweight     (1O2AAAQ)

approaches to semantic web services have failed" with "heavyweight approaches will fail ... " (as     (1O2AAAR)

you verbally pronounced)     (1O2AAAS)

[10:07] Torsten Hahmann: Regarding ChristophLange's "heavyweight" comment and PeterYim's correction,     (1O2AAAT)

I would go even further: does the observation that heavyweight ontologies are currently not used     (1O2AAAU)

really means they have failed? Maybe we just haven't found the right way of using them yet?     (1O2AAAV)

[10:11] Christoph Lange: Re @PeterYim, @TorstenHahmann about "heavyweight": OntoIOp (about     (1O2AAAW)

which I'm biased of course because I'm involved) hopes to strike a balance between "lightweight"     (1O2AAAX)

and "heavyweight" in that it adopts lightweight linked data principles but also enables translations     (1O2AAAY)

across heavyweight ontology languages.     (1O2AAAZ)

[10:12] Leo Obrst: @[10:07] Torsten Hahmann: I think richer (heavyweight) ontologies are very useful     (1O2AAAAA)

for certain kinds of applications, but in general not for online linked-data uses, because of many     (1O2AAAAB)

issues, including the temporal cost of computing/reasoning on the fly, etc.     (1O2AAAAC)

[10:19] Torsten Hahmann: @ChristophLange and @LeoOrbst: I certainly agree: rich ontologies will not     (1O2AAAAD)

solve all linked data problems, e.g., rich ontologies are not suitable for on-the-fly reasoning (as     (1O2AAAAE)

you mentioned). But they may still have their place in the larger setting of big & linked data. For     (1O2AAAAF)

example, they can be useful as tools to integrate & generate appropriate lightweight schemas (from     (1O2AAAAG)

rich ontologies).     (1O2AAAAH)

[10:19] Torsten Hahmann: As Christoph mentioned, striking the right balance is important.     (1O2AAAAI)

[10:09] GaryBergCross: I didn't use the phrase lightweight ontologies in the track A synthesis, but we should.     (1O2AAAAJ)

[10:06] ... Andrea Westerinen: Sorry to be late. Finally got my cable modem to work for more than 5 mins.     (1O2AAAAK)

[10:08] ... Marcela Vegetti: Sorry for my late join. Is there any problem with skype joinconference?     (1O2AAAAL)

I can't connect to the audio session     (1O2AAAAM)

[10:09] ... Peter P. Yim: @MarcelaVegetti - skype issues may be more local ... we've got plenty of skype     (1O2AAAAN)

[10:11] ... Marcela Vegetti: thanks @Peter. Problem solved. I'm now connected     (1O2AAAAP)

[10:09] Peter P. Yim: == Matthew West presenting on "Overcoming Ontology Engineering Bottlenecks: Synthesis-II" on behalf of the Track-C co-champions ...     (1O2AAAAQ)

[10:12] anonymous morphed into Lamar Henderson     (1O2AAAAR)

[10:16] Jack Ring: Has anyone devised an ontology regarding 'about ontologies' wherein we might find     (1O2AAAAS)

factors such as purpose, reuse, lattice, perspectives (designer, user, reused, etc.), size, degree     (1O2AAAAT)

of complexness, modularity, etc.?     (1O2AAAAU)

[10:20] Andrea Westerinen: @JackRing [10:16] I would like to evolve VOCREF into such an ontology.     (1O2AAAAV)

[10:23] Amanda Vizedom: Yes, Jack [10:16], VOCREF of course doesn't cover all of this YET, after 1     (1O2AAAAW)

weekend hackathon, but it does already cover some, and others are identified as to-do in the issue     (1O2AAAAX)

tracker, and more should be added. That's precisely where we want it to go, as Andrea said [13:20].     (1O2AAAAY)

It is now stood up for continuing, collaborative, open-source-style development.     (1O2AAAAZ)

[10:17] Jack Ring: Slide 8, Test, test, test is grossly inadequate, c.f., the dismal results of software test.     (1O2AAAAAA)

[10:23] GaryBergCross: @MatthewWest [re. slide#9] On this "The first priority is identity (same name     (1O2AAAAAB)

same thing) not semantics" Do we have the same things without semantics?     (1O2AAAAAC)

[10:30] Matthew West: @GaryBergCross - Some of my friends talk about "a list of famous names". At the     (1O2AAAAAD)

base level, you don't even have definitions of terms, which can lead to ambiguity. So a set of terms     (1O2AAAAAE)

with text definitions (intended interpretations) is actually quite useful.     (1O2AAAAAF)

[10:34] GaryBergCross: @MatthewWest, the term with text discussion sound like something to establish     (1O2AAAAAG)

an informal conceptual space, but people involved in this exchange have some interpretation using     (1O2AAAAAH)

their internal semantics. What I take it you mean is no attempt at formal semantics.     (1O2AAAAAI)

[10:25] Francesca Quattri: "why are ontologies in English?" (from Matthew's slide#12). This opens up     (1O2AAAAAJ)

a huge market / demand for reusability of ontologies as developed into other languages other than     (1O2AAAAAK)

English, and highlights the point of translation reliability / bottlenecks in translation of     (1O2AAAAAL)

ontologies. Should we maybe also present the topic as a "challenge"?     (1O2AAAAAM)

[10:28] Alex Shkotin: We have ontology in English and Russian with equivalentClasses for terms - it works:-)     (1O2AAAAAN)

[10:29] GaryBergCross: On this english term issue, it is worth noting that Wikipedia has separate     (1O2AAAAAO)

versions by language and they are not translations, but populated by native speakers. Hence DBpedias     (1O2AAAAAP)

from these may vary...     (1O2AAAAAQ)

[10:31] Amanda Vizedom: @GaryBergCross [10:29] One of Wikidata's goals is to create more content     (1O2AAAAAR)

reusability across the language-specific Wikipedias by adding ontology-like conceptual structures     (1O2AAAAAS)

with multilingual lexification.     (1O2AAAAAT)

[10:32] Matthew West: @FrancescaQuattri: Actually I think there is an opportunity for an ontology     (1O2AAAAAU)

module that supports name/language pair sets for IDs.     (1O2AAAAAV)

[10:34] Andrea Westerinen: @MatthewWest [10:32] +1     (1O2AAAAAW)

[10:34] Andrea Westerinen: @AlexShkotin and @FrancescaQuattri [10:25] Is it necessary to have 2     (1O2AAAAAX)

ontologies or 1 ontology with labels, comments, etc. in different xml:langs? I would prefer the     (1O2AAAAAY)

latter since you don't want disconnects.     (1O2AAAAAZ)

[10:36] Francesca Quattri: @AndreaWesterinen and @MatthewWest: Andrea, I agree, the second options     (1O2AAAAAAA)

sounds definitely more appealing. Then a big issue to highlight in our Summary also relates to     (1O2AAAAAAB)

translation reliability.     (1O2AAAAAAC)

[10:39] Alex Shkotin: @AndreaWesterinen labels are not a part of logic. We use terms native for     (1O2AAAAAAD)

natural language and use OWL2 operations to describe relationships. It's good for us as we have     (1O2AAAAAAE)

bilingual dictionary.     (1O2AAAAAAF)

[10:39] Leo Obrst: @FrancescaQuattri and others: I think you will always need vocabularies linked to     (1O2AAAAAAG)

ontologies, with the vocabularies in possibly distinct languages (locally, these can be distinct     (1O2AAAAAAH)

labels in the ontologies), but we must take care not to introduce another source of     (1O2AAAAAAI)

discrepancy/non-reusability by focusing on the natural languages of ontologies, since really it is     (1O2AAAAAAJ)

the logic of the latter that is important.     (1O2AAAAAAK)

[10:40] Andrea Westerinen: @FrancescaQuattri [10:36] Yes, I have some experience with this ... adding     (1O2AAAAAAL)

a Spanish translation to an ontology. So, had translations only in an ontology file that built on     (1O2AAAAAAM)

the original definitions. All triples were loaded into the database and queries assumed that a     (1O2AAAAAAN)

language was set and passed this as input in each query. So, it really didn't matter what language     (1O2AAAAAAO)

was used to define the original as long as you had a native speaker to do the translation. Similar     (1O2AAAAAAP)

to any localization project.     (1O2AAAAAAQ)

[10:41] Amanda Vizedom: Francesca & all: I think there are two issues which should be separated,     (1O2AAAAAAR)

here. (1) is the language, if any, in which the concepts in the ontology are lexified and annotated.     (1O2AAAAAAS)

This is the easy part, really, because any concept can have annotations and lexificiation in     (1O2AAAAAAT)

arbitrarily many languages, and languages can be selected for view/use. (2) is the language, if any,     (1O2AAAAAAU)

in which concepts in the ontology are *named*. If developers rely on concept *names* for human     (1O2AAAAAAV)

readable (perhaps because of tool limitations), then one language will dominate, and it is harder to     (1O2AAAAAAW)

make the ontology as usable in another language.     (1O2AAAAAAX)

[10:41] Andrea Westerinen: The problem then comes down to MT.     (1O2AAAAAAY)

[10:42] Andrea Westerinen: @AmandaVizedom [10:41] I am not sure that I agree. The issue is tooling     (1O2AAAAAAZ)

and MT. If everything comes down to documentation and metadata, the original ontology language does     (1O2AAAAAAAA)

not matter. SMOT (simple matter of tooling) :-)     (1O2AAAAAAAB)

[10:42] Simon Spero: SKOS mapping relations arrived via many decades of prior art, not all of which     (1O2AAAAAAAC)

{{{ [10:44] Amanda Vizedom: {continuing my [10:41])... I have worked with one project that very successfully used a very large ontology with developers / users in multiple languages & localizations. This was successful and made original language not so relevant, because the project also used hexadec concept IDs (making it impossible to rely on names, rather than labels) and had in-house built tools, for devs and users, that showed ID with label in lang-loc of choice. }}}     (1O2AAAAAAAE)

[10:47] Amanda Vizedom: @AndreaWesterinen [10:42] I agree about tools. The tools mentioned in my     (1O2AAAAAAAF)

[10:44] enabled making issue (2) [10:41], the original language, irrelevant. That's not so easy to     (1O2AAAAAAAG)

do with standard tools/methods.     (1O2AAAAAAAH)

[10:54] Francesca Quattri: @AmandaVizedom: any chance to know more about the project mentioned above?     (1O2AAAAAAAI)

[10:58] Amanda Vizedom: @FrancescaQuattri, Yes and No. It was proprietary, though some aspects are     (1O2AAAAAAAJ)

not unique to them and are more publicly known within the relevant technology communities. It was     (1O2AAAAAAAK)

for Convera, which no longer exists. The core tech and team are now part of Vertical Search Works.     (1O2AAAAAAAL)

They have published some descriptions of the approach, with most depth in the areas where they have     (1O2AAAAAAAM)

patented their particular take on (part of) the process.     (1O2AAAAAAAN)

[11:00] Francesca Quattri: @AmandaVizedom: thank you for the info     (1O2AAAAAAAO)

[10:49] Alex Shkotin: @AmandaVizedom, have a look at our bi-lingual ontology     (1O2AAAAAAAP)

[10:22] Peter P. Yim: == Anne Thessen presenting on "Tackling the Variety Problem in Big Data:     (1O2AAAAAAAR)

Synthesis-II" on behalf of the Track-D co-champions ...     (1O2AAAAAAAS)

[10:33] Jack Ring: Slide 4. More than pattern matching, pattern discovery (even if not looking for     (1O2AAAAAAAT)

on behalf of the Track-E co-champions and the Hackathon Project Leads ...     (1O2AAAAAAAW)

[10:51] Till Mossakowski: Ontohub hackathon: we did mainly different bugfixes     (1O2AAAAAAAX)

[10:51] Till Mossakowski: These bugfixes were mainly related to the integration of git repositories     (1O2AAAAAAAY)

and the web portal     (1O2AAAAAAAZ)

[10:53] Peter P. Yim: see links to Hackathon details under:     (1O2AAAAAAAAA)

[11:00] Peter P. Yim: @ALL Hackathon Leads - if you are planning to do a demo during the     (1O2AAAAAAAAC)

OntologySummit2014_Symposium, please let the symposium organizers know, and make sure you take a     (1O2AAAAAAAAD)

[10:57] Peter P. Yim: == Open Discussion on ideas to optimally fit the above material into the adopted     (1O2AAAAAAAAF)

Communique outline, and the positions we want to assume in this year's communique ...     (1O2AAAAAAAAG)

[10:59] anonymous1 morphed into Lamar Henderson     (1O2AAAAAAAAH)

[10:59] GaryBergCross: [re. the Communique Outline] Under 'Sharable and Reusable Ontologies' we     (1O2AAAAAAAAI)

might include some examples of Best Practices.     (1O2AAAAAAAAJ)

[11:13] Andrea Westerinen: @GaryBergCross [10:59] We have some (very few) examples of suggestions     (1O2AAAAAAAAK)

and best practices in our Track A synthesis, but we certainly could do more. Also, we could make     (1O2AAAAAAAAL)

this a work item in the IAOA SIG.     (1O2AAAAAAAAM)

[11:01] GaryBergCross: The outline has no sub-topic of things like use of ODPs or lightweight     (1O2AAAAAAAAN)

[11:02] GaryBergCross: (to MichaelGruninger's verbal response on the above remark, that we will be     (1O2AAAAAAAAP)

getting to that next level of detail when we start seeing a draft of the Communique next week)     (1O2AAAAAAAAQ)

[11:03] Terry Longstreth: @AmandaVizedom - follow-up on your dialogue with Francesca at [10:54] - Did     (1O2AAAAAAAAS)

you discover developers memorizing the x' labels, expecting their referents to be invariant?     (1O2AAAAAAAAT)

[11:15] Amanda Vizedom: @TerryLongstreth, no. But even the normal way of viewing the ontology while     (1O2AAAAAAAAU)

coding would show you both hex ID and label (in selected language) and sometimes the label in that     (1O2AAAAAAAAV)

language for an appropriate parent, where the label is also a label for other concepts in that     (1O2AAAAAAAAW)

language. So, for example, in en-us, you might see a node as "gen.00BT7(Dog(Mammal))" <-- made up     (1O2AAAAAAAAX)

example, I have no idea what the ID is for that concept in that ontology.     (1O2AAAAAAAAY)

[11:10] Peter P. Yim: I have a feeling we are not addressing current "Big Data" practitioners, who could     (1O2AAAAAAAAZ)

be data analytics people, adequately ... we almost haven't had a chance to see, for example, any     (1O2AAAAAAAAAA)

case where an application that applied both mathematical models and semantic models, or the former     (1O2AAAAAAAAAB)

taking advantage of the latter     (1O2AAAAAAAAAC)

[11:14] Martin Davtyan: @PeterYim, absolutely agree! There are some cases in Big Data practice which     (1O2AAAAAAAAAD)

LOOK like ontology engineering, for example Graphical Models for genes, which are reused and shared     (1O2AAAAAAAAAE)

and collaboratively created just like ontologies. I've spent a lot of time trying to research this     (1O2AAAAAAAAAF)

exact problem and still searching.     (1O2AAAAAAAAAG)

[11:15] GaryBergCross: @PeterYim [14:10] I agree that we haven't addressed Big Data issues directly     (1O2AAAAAAAAAH)

enough with enough examples.     (1O2AAAAAAAAAI)

[11:11] Terry Longstreth: @AndreaWesterinen - how do we validate the equivalence of semantics     (1O2AAAAAAAAAJ)

captured by different syntaxes?     (1O2AAAAAAAAAK)

[11:14] Alex Shkotin: @TerryLongstreth, It may be something like translation     (1O2AAAAAAAAAL)

[11:15] Andrea Westerinen: @TerryLongstreth [11:11] I think that this is another function of tooling     (1O2AAAAAAAAAN)

and testing. But, today, it is manual and just like guaranteeing that you have the right language     (1O2AAAAAAAAAO)

translation. However, this would be a great topic to explore further. Could you do similarity     (1O2AAAAAAAAAP)

analysis, etc.? I think so ... kind of like concept mapping.     (1O2AAAAAAAAAQ)

[11:13] GaryBergCross: In terms of things I heard today to include in the communique I would suggest     (1O2AAAAAAAAAR)

we include the point that Track C (@MatthewWest) made about addressing the level of semantics needed     (1O2AAAAAAAAAS)

by various types of Application Domains.     (1O2AAAAAAAAAT)

[11:15] Anne Thessen: [responding to the verbal discussion of @PeterYim [11:10], and the request that     (1O2AAAAAAAAAU)

Track-D might develop more in their write-up to address that, and for AnneThessen's comment (since     (1O2AAAAAAAAAV)

Ken Baclawski is not present)] I am still here     (1O2AAAAAAAAAW)

[11:15] Anne Thessen: Please capture that in the chat. I had to leave to get some water and I missed     (1O2AAAAAAAAAX)

some of that. .... [ see: @PeterYim [11:10] ]     (1O2AAAAAAAAAY)

[11:15] Anne Thessen: I need to not talk anymore. My voice is about gone.     (1O2AAAAAAAAAZ)

[11:17] Leo Obrst: There is an emerging "buzz" term called "deep learning" which addresses the     (1O2AAAAAAAAAAA)

interpretations behind big data, i.e., correlations and patterns, and these must include     (1O2AAAAAAAAAAB)

knowledge-based methods and ontologies, because of causal and explanation needs. Maybe Track D would     (1O2AAAAAAAAAAC)

contribute some input on this, if they consider it important.     (1O2AAAAAAAAAAD)

[11:20] Dominique Mariko: @PeterYim [11:10] I started reading this today, don't know if it could be     (1O2AAAAAAAAAAE)

of any help : logistic regression model for predicting the singleton/coreferent distinction, drawing     (1O2AAAAAAAAAAF)

on linguistic insights about how discourse entity lifespans are affected by syntactic and semantic     (1O2AAAAAAAAAAG)

[11:21] Dominique Mariko: Don't have the audio plug-sorry     (1O2AAAAAAAAAAI)

[11:26] Peter P. Yim: @DominiqueMariko - thank you for the input ... would be great if you can capture     (1O2AAAAAAAAAAJ)

that (if appropriate) and/or additional thoughts to the page at:     (1O2AAAAAAAAAAK)

[11:19] GaryBergCross: Hackathons can illustrate practices, tools and how one uses ontologies.     (1O2AAAAAAAAAAN)

[11:21] Anatoly Levenchuk: @GaryBergCross: many Hackathon project not finished yet! Not only final     (1O2AAAAAAAAAAO)

reporting but actual work! But we already have valuable observation in Hackathon project content.     (1O2AAAAAAAAAAP)

[11:23] Andrea Westerinen: I would encourage everyone to read the Track A synthesis and suggest where     (1O2AAAAAAAAAAQ)

we should expand the topics and examples. I will update to bring in the dialog on the "reuseful"     (1O2AAAAAAAAAAR)

email which is getting lots of good discussion.     (1O2AAAAAAAAAAS)

[11:24] GaryBergCross: Track A synthesis at     (1O2AAAAAAAAAAT)

[11:17] Peter P. Yim: @ALL: as announced by our Symposium co-chairs, Dr. Ram Sriram & Professor Tim Finin     (1O2AAAAAAAAAAV)

our Apr 28~29 Symposium (at NSF in Greater Washington DC) is now open for registration. Please     (1O2AAAAAAAAAAW)

register yourself ASAP, as capacity is limited - see OntologySummit2014_Symposium details at:     (1O2AAAAAAAAAAX)

deadline for reserving blocked hotel rooms for the Ontology Summit Symposium at the group pricing     (1O2AAAAAAAAAAZ)

- ref. details under:     (1O2AAAAAAAAAAAA)

for the Symposium NOW, if you haven't already!     (1O2AAAAAAAAAAAC)

[11:26] Peter P. Yim: @ALL: Please mark your calendars and reserve this same time for the next two     (1O2AAAAAAAAAAAE)

Thursdays, when we will be working on getting the OntologySummit2014_Communique reviewed and     (1O2AAAAAAAAAAAF)

finalized during those two virtual sessions. In particular ... Session-13 will be up next Thursday -     (1O2AAAAAAAAAAAG)

2014_04_10 - Thursday: Ontology Summit 2014: session-13: Communique Review - Session Co-chairs:     (1O2AAAAAAAAAAAH)

Michael Grüninger & Leo Obrst - Panelists: All Contributing Editors - ref. developing details at:     (1O2AAAAAAAAAAAI)

[11:27] Peter P. Yim: @org-comm members, Reminder to those in the organizing committee, our next meeting     (1O2AAAAAAAAAAAL)

(n.10) is coming up tomorrow - Fri 2014.04.04 - see:     (1O2AAAAAAAAAAAM)

[11:27] Peter P. Yim: Very productive session ... thank you ALL!     (1O2AAAAAAAAAAAO)

[11:27] Ed Bernot: Great session, thanks!     (1O2AAAAAAAAAAAP)

[11:28] Leo Obrst: Thanks, all!     (1O2AAAAAAAAAAAQ)

[11:27] Peter P. Yim: -- session ended: 11:24 am PDT --     (1O2AAAAAAAAAAAS)

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

Additional Resources     (1P)

For the record ...     (1P7)

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

*** Please pay special attention to the start-time - of 9:30am PDT / 12:30pm EDT / 6:30pm CEST / 5:30pm BST / 16:30 UTC - as in this week, both N. America and Europe will be in Summer time, but there are still other regions that don't do daylight saving time at all! ***     (1Q4)

  • Dial-in:     (1Q5D)
    • Phone (US): +1 (206) 402-0100 ... when prompted enter Conference ID: 141184# ... (long distance cost may apply)     (1Q5D1)
    • Skype: joinconference (i.e. make a skype call to the contact with skypeID="joinconference") ... (generally free-of-charge, when connecting from your computer ... ref.)     (1Q5D2)
      • when prompted enter Conference ID: 141184#     (1Q5D2A)
      • Unfamiliar with how to do this on Skype? ...     (1Q5D2B)
        • Add the contact "joinconference" to your skype contact list first. To participate in the teleconference, make a skype call to "joinconference", then open the dial pad (see platform-specific instructions below) and enter the Conference ID: 141184# when prompted.     (1Q5D2B1)
        • you may connect to (the skypeID) "joinconference" whether or not it indicates that it is online (i.e. even if it says it is "offline," you should still be able to connect to it.)     (1Q5D2B2)
      • Can't find Skype Dial pad? ...     (1Q5D2C)
        • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1Q5D2C1)
        • 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.)     (1Q5D2C2)
  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at: ... view-only password: "ontolog"     (1Q5E)
    • 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.     (1Q5E1)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the slides above (where applicable) and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1Q5E2)
    • 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").     (1Q5F1)
    • 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.     (1Q5F2)
    • thanks to the folks, one can now use a jabber/xmpp client (e.g. Digsby or Adium) to join this chatroom. Just add the room as a buddy - (in our case here) ... Handy for mobile devices!     (1Q5F3)
  • Discussions and Q & A:     (1Q5G)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1Q5G1)
    • 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.)     (1Q5G2)
    • 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.)     (1Q5G3)
    • 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.)     (1Q5G4)
  • RSVP to with your affiliation, ... or simply just by adding yourself to the "Expected Attendees" list below (if you are already a member of the community.)     (1Q5I)
  • 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.     (1Q5K)

Attendees     (1R)

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

This is a cached copy of the requested page, and may not be up to date.

Sorry! This site is experiencing technical difficulties.

Try waiting a few minutes and reloading.

(Can't contact the database server: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) (localhost))

You can try searching via Google in the meantime.
Note that their indexes of our content may be out of date.