From OntologPSMW

Jump to: navigation, search
[ ]


Ontology Summit 2012 (Pre-launch) Community Input and Planning Session - Thu 2011-12-08     (1)

  • Topic: Refining the ideas around the theme and program for OntologySummit2012     (1A)
  • Co-chairs: Dr. SteveRay (CMU) & Mr. PeterYim (Ontolog)     (1B)
  • Agenda: This is a (pre-launch) communitywide brainstorming and planning session for OntologySummit2012     (1C)

Abstract     (1E)

The upcoming Ontology Summit is co-organized by Ontolog, NIST, NCOR, NCBO, IAOA, NCO_NITRD.     (1E1)

This is the 7th year we are organizing this annual, international, open Ontology Summit event. The general format of the event comprises a series of both virtual and face-to-face activities that span about 3 months (January through March or April each year). These activities include a vigorous three-month online discourse on the theme of the Summit, virtual panel discussions, research activities, and so on, which will culminate in a two-day face-to-face workshop and symposium at NIST in Gaithersburg, Maryland, USA. Each year, we publish a Summit Communiqu�� to offer a message from the Summit participants to the world-at-large as a signature activity of the Ontology Summit series.     (1E2)

This is a (pre-launch) communitywide brainstorming and planning session for those who are passionate about the subject and would like to influence and help drive the outcome by helping refine the ideas, organization and process, around our challenge of OntologySummit2012.     (1E3)

During this session the Ontology Summit community will get together to distill the theme, brainstorm on ideas, candidate program, candidate key players we need to engage, solicit commitments, and make attempt to get organized for this upcoming Ontology Summit.     (1E4)

At this point, two themes are presented as alternatives:     (1E5)

Systems engineering focuses on the interactions of people with their systems, so includes information technology, data and metadata, socio-technical and cultural aspects including institutional, legal, economic, and human-centered design requirements.     (1E8)
o Software engineering     (1E8A)
o Business rules and enterprise issues     (1E8B)
o Socio-technical environment     (1E8C)
o Big Data     (1E8D)
o Ontology Quality in Context     (1E8E)
"Big Data" to include several dimensions:     (1E10)
o Complexity of collections     (1E10A)
o Large quantities of data     (1E10B)
o Heterogeneity of data (e.g. 600 different representations of patient records)     (1E10C)
o Federation of distributed data sources     (1E10D)
o Extracting (useful) knowledge out of big data (using ontology to UNDERSTAND data)     (1E10E)
  • 1+2. Maybe a combination of both - under something like: Ontology in "Complex Systems"     (1E11)

This summit will formulate recommendations for the application of ontological techniques to specific key problems we are facing in the subject area.     (1E13)

Our developing 2012 Ontology Summit home page is at: OntologySummit2012     (1E15)

Agenda & Proceedings     (1F)

0. Participant self-introduction (if size of participants is manageable) (15~30 seconds each)     (1F1)

1. Introduction and ideas �� co-chairs - [ slides ]     (1F2)

2. Open floor for ideas on developing and executing the program (All) -- please refer to process above     (1F3)

2.1 Refining the theme     (1F4)
o the selected theme is: OntologySummit2012: "Ontology for Big Systems"     (1F4A)
2.2 Brainstorming on ideas that support the theme     (1F5)
o who (organizations, individuals) should we really try to engaging     (1F5A)
o Tracks, Topics, Speakers, Invitees, Sponsors, Publicity ... and more     (1F5B)
o Crafting a program that will allow us to make the best out of this next Ontology Summit     (1F5C)
o Approach and Execution     (1F5D)

3. A call for volunteers and champions ... and, getting ourselves organized - note: first organizing committee meeting date: Friday, 6-Jan-2012 10:00am EST / 4:00pm CET (tentative! ... note that this has been updated after the end of the session)     (1F6)

4. Summary and wrap-up (co-chairs) - please mark Ontology Summit 2012 Launch date: Thursday, 12-Jan-2012 12:30pm EST / 6:30pm CET - see details on developing session page at: ConferenceCall_2012_01_12     (1F7)

Proceedings     (1G)

Please refer to the above     (1G1)

IM Chat Transcript captured during the session    (1G2)

see raw transcript here.     (1G2A)

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

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

-- begin of chat session --     (1G2D)

= Ontology Summit 2012 (Pre-launch) Community Input and Planning Session - Thu 2011-12-08 =     (1G2F)

Topic: Refining the ideas around the theme and program for Ontology Summit 2012     (1G2G)

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

Can't find Skype Dial pad? ... it's under the "Call" dropdown menu, select "Show Dial Pad" there     (1G2K)

== Proceedings: ==     (1G2L)

anonymous morphed into Tim Wilson     (1G2M)

anonymous morphed into Pat Cassidy     (1G2O)

Ali Hashemi: Is there someone in charge of the Skype "joinconference" id? It appears offline for me.     (1G2P)

Steve Ray: Did you type in the PIN? 141184#     (1G2Q)

Ali Hashemi: I'm restarting Skype, but i didn't have an option of connecting to joinconference     (1G2R)

because the contact appeared offline.     (1G2S)

Ali Hashemi: Contact appeared online after restart     (1G2T)

Steve Ray: Good news. Hope to hear your voice.     (1G2U)

Peter P. Yim [added subsequently]: one can actually skype "joinconference" even when it appears to be     (1G2V)

off-line; at least that works for me every time     (1G2W)

Ali Hashemi: 1) Click on the "Call" dropdown menu; 2) Click on "Show Dial Pad"; 3) Enter the pin from     (1G2X)

the "dial pad"     (1G2Y)

Mike Bennett: By the way on the joiconference Skype, at least in one version of Skype it does not     (1G2Z)

display a numeric keypad, thereby making it impossible to type in the conference ID!     (1G2AA)

Mike Bennett: Yes, I also failed to read Peter's instructions above.     (1G2AB)

anonymous morphed into Amanda Vizedom     (1G2AD)

anonymous morphed into Elisa Kendall     (1G2AE)

anonymous morphed into Bo Newman     (1G2AF)

anonymous1 morphed into Martin Serrano     (1G2AG)

anonymous morphed into Ken Allgood     (1G2AH)

anonymous morphed into Michael Riben     (1G2AI)

anonymous morphed into Nikolay Borgest     (1G2AJ)

anonymous morphed into Michael Riben     (1G2AK)

Joanne Luciano: Should I be looking/downloading some slides - or is that later. Please post the link     (1G2AL)

Peter P. Yim: when in doubt, check the session page -     (1G2AQ)

Jack Ring: Six facets of ontology - system engineering.     (1G2AT)

Joanne Luciano: So, how can you know if ontology is helping if there are no metrics in place to     (1G2AU)

evaluate that?     (1G2AV)

Joanne Luciano: by "you" I mean "we"     (1G2AW)

Mike Bennett: @Joanne we looked at that for last year's Summit.     (1G2AX)

Joanne Luciano: @Mike -- and? (BTW, I do like addressing Big Data)     (1G2AY)

Jack Ring: 10X Better, Faster Systems Engineering.     (1G2AZ)

Tim Wilson: I have to leave the call soon, but I am very interested in the System Engineering aspects     (1G2AAC)

of Ontology as well as Ontology Acquisition, including text analytics.     (1G2AAD)

Jack Ring: Ontology --- Relief from complexity     (1G2AAE)

Matthew West: Sorry I'm late. Struggled to get Skype working.     (1G2AAF)

Amanda Vizedom: Can someone address how the proposed "Big Data" theme relates to other items on the     (1G2AAG)

suggestions page? E.g., is it approximate to Cory's suggestion?     (1G2AAH)

Bo Newman: as part of either topic I would like to see something that focuses on working with     (1G2AAI)

multi-perspective semantics     (1G2AAJ)

Pat Cassidy: Ontology in complex systems fits in with my interest in the ability of ontology to     (1G2AAK)

support interoperability. Perhaps we may somehow mention the "cloud" as being a place where complex     (1G2AAL)

systems may reside or interact?     (1G2AAM)

Ali Hashemi: I think Amanda means this:     (1G2AAO)

Joanne Luciano: @Ali -- thanks for the link!     (1G2AAQ)

Amanda Vizedom: I'm trying to get a better sense of what is meant by this theme.     (1G2AAR)

Christopher Spottiswoode: @Steve: I would like to congratulate you on both the themes chosen. Each is     (1G2AAS)

good, the combination excellent.     (1G2AAT)

Steve Ray: @Christopher: Thank you.     (1G2AAU)

anonymous morphed into Hasan Sayani     (1G2AAV)

Bo Newman: Unifying topic - pros and cons of multi-perspective semantics     (1G2AAW)

Bo Newman: Or simply multi-perspective semantics     (1G2AAX)

Bo Newman: Background on multi-perspective semantics: Dealing with differences in meaning (semantics)     (1G2AAY)

based on individual perspectives can be addressed by either moving to a single shared perspective     (1G2AAZ)

(ontology) or by expanding the collective ontology to encompass the full richness of the concept.     (1G2AAAA)

Each has challenges: Developing a shared ontology needs to avoid the pitfalls of reductionism.     (1G2AAAB)

Expanded or collective ontologies face the challenge of incorporating implicit/tacit aspects that     (1G2AAAC)

define the individual perspectives.     (1G2AAAD)

Amanda Vizedom: +1 for BoNewman's suggestion. Addressing multiple perspectives is essential for     (1G2AAAE)

large-scale federation, applications with localization, and anything that involves sharing     (1G2AAAF)

information across user communities, over time, etc.     (1G2AAAG)

Mike Bennett: +1 here also for multiple perspective semantics. We've been looking at some of this     (1G2AAAH)

within our efforts but would like to see a broader effort and consensus. Defines archetypal of     (1G2AAAI)

"simplest possible" concepts which by definition are not local to most of our individual industries.     (1G2AAAJ)

Lots of good ontologies to leverage for such an effort, just show consensus way of using these     (1G2AAAK)

together e.g. in linked data.     (1G2AAAL)

Ken Allgood: Agree with Bo's topic. The work I'm doing right now in the electronic health record     (1G2AAAM)

arena is directly dependent upon multiple perspective harmonization within big data federation.     (1G2AAAN)

Amanda Vizedom: What Bo is talking about is critical to federation and to web-like environments - you     (1G2AAAO)

need to capture rich contextual elements and provenance info also, to be able to preserve meaning of     (1G2AAAP)

data when crossing context lines.     (1G2AAAQ)

Bo Newman: Multi-perspective semantics track application: (1) Big Data, especially when working with     (1G2AAAR)

aggregates of, and usability across multiple domains is logically subject to the issues associated     (1G2AAAS)

with multi-perspective semantics. (2) System engineering, especially when dealing a broad spectrum     (1G2AAAT)

of customers, developers, and stakeholders each with their own perspective, has also experienced     (1G2AAAU)

problems that could be directly related to issues generated by misaligned multi-perspective     (1G2AAAV)

Jack Ring: A joint Working Group of the International Council on Systems Engineering and     (1G2AAAX)

International Society for Systems Sciences is pursuing the development of a Unified Ontology for     (1G2AAAY)

Systems Engineering. This effort is mostly practitioners getting ready for interaction with     (1G2AAAZ)

ontologists.     (1G2AAAAA)

Leo Obrst: Per Jack's note: see     (1G2AAAAB)

Pat Cassidy: Jack - are the online references to these efforts toward a "unified ontology"     (1G2AAAAD)

Pat Cassidy: The ability to have a common unifying ontology and multiple perspectives are not mutually     (1G2AAAAE)

exclusive. My conclusions from the past 15 years of ontology discussions is that a common basic     (1G2AAAAF)

ontology can be used to **translate** among all the diverse terminologies, perspectives, belief     (1G2AAAAG)

systems, and applications. The basic ontology should be able to be small enough to be mastered by at     (1G2AAAAH)

least one data developer in each group, who can then serve as the bilingual translator between the     (1G2AAAAI)

local system and the broader group.     (1G2AAAAJ)

Ken Allgood: @Pat, excellent point, and one which is often missed in discussions around "big, scary,     (1G2AAAAK)

ontologies" in actual system design and engineering.     (1G2AAAAL)

Eric Chan: I suggest to reach out to "The Society for Design and process Science"     (1G2AAAAM) as a "partnering community" for the theme on "application of ontology"     (1G2AAAAN)

... "in transdisciplinary system engineering."     (1G2AAAAO)

Michael Grüninger: do we want to distinguish "systems engineering" from "software engineering"?     (1G2AAAAP)

Ken Allgood: How Ontology can address big data issues in federation, harmonization, etc??     (1G2AAAAQ)

Amanda Vizedom: I'm still not sure what the two main themes are supposed to be; they are so open to     (1G2AAAAR)

multiple interpretations.     (1G2AAAAS)

Amanda Vizedom: Depending on how the themes are defined, I can easily see both "semantics from, and     (1G2AAAAU)

across multiple perspectives" and "ontology quality in context" (which we mean specifically to     (1G2AAAAV)

indicate metrics and methods for evaluating fitness for purpose) as tracks under either of the two     (1G2AAAAW)

major themes. But again, each still feels too underspecified for shared understanding and intention,     (1G2AAAAX)

Ali Hashemi: I concur with Amanda. A lot of the "content" items we're discussing could easily fit     (1G2AAAAZ)

into both of the themes. Big data _requires_ systems engineering, and the major focus of many system     (1G2AAAAAA)

engineering projects these days will be Big Data. The latter (i.e. "Big Data") will have greater     (1G2AAAAAB)

cachet with a broader audience though.     (1G2AAAAAC)

Steve Ray: If we went with "systems engineering", we could break it down into the major components,     (1G2AAAAAD)

to include design, validation, testing... and how ontology plays a role in each.     (1G2AAAAAE)

Jack Ring: Ontology, the missing link in systems engineering.     (1G2AAAAAF)

Matthew West: Systems Engineering and big data meet in big engineering systems. Think of the quantity     (1G2AAAAAH)

and complexity of data for e.g. an offshore oilrig, or an aircraft carrier.     (1G2AAAAAI)

Matthew West: @Ali. [@Michael ?] I'm assuming Systems Engineering means hardware systems, or systems     (1G2AAAAAJ)

with embedded software. What do you mean?     (1G2AAAAAK)

Ali Hashemi: @Matthew, that's one source of confusion for me. Is it restricted to hardware systems,     (1G2AAAAAL)

or the more general systems which would encompass applications that will rely on Big Data (say     (1G2AAAAAM)

sensor fields), or epidemic tracking etc... It's unclear to me from the theme names.     (1G2AAAAAN)

Peter P. Yim: @MatthewWest - I trust we are *not* equating Systems Engineering with hardware systems or     (1G2AAAAAO)

embedded system, but rather taking the broader "Systems" definition ... which should include     (1G2AAAAAP)

man-machine systems, system-of-systems, etc.     (1G2AAAAAQ)

Elisa Kendall: At the OMG, there have been a number of discussions and some work in the past year for     (1G2AAAAAR)

aligning ontology with SysML, which is a UML profile for systems engineering modeling support in     (1G2AAAAAS)

UML. JPL, for example, has developed an ontology that allows transformation of SysML models such     (1G2AAAAAT)

that they can be reasoned over to identify problems in those models. Given that JPL gets "one shot"     (1G2AAAAAU)

at sending systems into space, any capability that can assist in eliminating problems in systems     (1G2AAAAAV)

models is incredibly important. If we are talking about ontological support for systems engineering,     (1G2AAAAAW)

rather than the engineering of systems supported by ontologies, this is one area we could piggyback     (1G2AAAAAX)

on and we could reach out to that community to get their input.     (1G2AAAAAY)

Pat Cassidy: I'm somewhat reluctant to match "systems engineering" with "ontology". Either term may     (1G2AAAAAZ)

be mysterious to a lot of people, and the combination of specialized terms in a title might well     (1G2AAAAAAA)

convince all but a few hard-core ontolog participants that it is not relevant to their purposes.     (1G2AAAAAAB)

Jack Ring: Ontology enables big data + big function = big valuable societal benefits.     (1G2AAAAAAC)

Peter P. Yim: personally, I am in favor of using this summit to team ontologists up with system     (1G2AAAAAAE)

engineers, so "together" this team will be in a much better position to address "big data" problems     (1G2AAAAAAF)

Ali Hashemi: +1 to PeterYim's point. On its own, the use of the term Big Data entails greater     (1G2AAAAAAG)

relevance to the broader technology conversation.     (1G2AAAAAAH)

Ken Allgood: @Peter.. Agree.. That's exactly the direction we might wish to consider to increase the     (1G2AAAAAAI)

recognition and perceived benefit of an ontology-driven solution     (1G2AAAAAAJ)

Bo Newman: I agree with Peter: Ontology as a component of a solution is a much more extendable     (1G2AAAAAAK)

position than ontology as the solution.     (1G2AAAAAAL)

Ken Allgood: Big Data opportunities are dependent upon the contextual clarity ontologies provide.     (1G2AAAAAAM)

Todd Schneider: I concur with Peter's approach - Systems Engineering first, then use this to     (1G2AAAAAAN)

understand how to work with big data.     (1G2AAAAAAO)

Steve Ray: My own personal concerns and opinions: Big Data is a bit more focused, and thus possibly     (1G2AAAAAAP)

amenable to yield some concrete contribution. One other potential pitfall is that systems     (1G2AAAAAAQ)

engineering as a field of study might come across as an overly academic discussion (although, of     (1G2AAAAAAR)

course, many industries use systems engineering regularly).     (1G2AAAAAAS)

Jack Ring: Ontologies unify general systems thinking and general semantics thereby bridging a     (1G2AAAAAAT)

long-standing, deep divide in human endeavors.     (1G2AAAAAAU)

Matthew West: @Ali My understanding is that those who consider themselves systems engineers in the     (1G2AAAAAAV)

broadest sense are concerned with the integration of multiple components where those components may     (1G2AAAAAAW)

include but are not restricted to hardware, software, and people. The main restriction in Systems     (1G2AAAAAAX)

Engineering is that it is man made. There is an even broader view of systems that would include e.g.     (1G2AAAAAAY)

ecosystems, but these are not engineered, but are naturally occurring.     (1G2AAAAAAZ)

Ali Hashemi: One vote for the broader Systems Engineering -- I think a lot of people don't quite     (1G2AAAAAAAA)

wholly understand how ontologies fit into the bigger picture of the actual applications that people     (1G2AAAAAAAB)

are developing. It would be tremendously useful to demonstrate what roles ontologies can play in     (1G2AAAAAAAC)

bigger systems.     (1G2AAAAAAAD)

Matthew West: We could go for big data with Systems Engineering as a thread, since there is often big     (1G2AAAAAAAE)

data involved in big systems.     (1G2AAAAAAAF)

Amanda Vizedom: Following @MatthewWest's comment: Given that understanding of systems engineering,     (1G2AAAAAAAG)

I'm more comfortable that we actually have a focused topic. I also think the inclusion of human     (1G2AAAAAAAH)

components (and therefore factors) is worth emphasizing.     (1G2AAAAAAAI)

Christopher Spottiswoode: @Leo: But the basis of managing and exploiting Big Data has to reside in     (1G2AAAAAAAJ)

system and data architecture, organization and management - all Systems Engineering!     (1G2AAAAAAAK)

Christopher Spottiswoode: @Leo: ... and Systems Engineering has to cater for Big Data.     (1G2AAAAAAAL)

Jack Ring: We need a track, if not a theme, on the impact of forthcoming massively parallel hardware     (1G2AAAAAAAM)

on the design of ontologies. The era of full duplex semantic data management is here.     (1G2AAAAAAAN)

Todd Schneider: Fabian, Have you ever had to try to develop a 'big' system? There many problems.     (1G2AAAAAAAO)

Todd Schneider: Fabian, your argument would suggest that there's a bigger payoff for addressing     (1G2AAAAAAAP)

systems engineering.     (1G2AAAAAAAQ)

Amanda Vizedom: @ToddSchneider -- I think we need more along that line; it wasn't clear to me until     (1G2AAAAAAAR)

Steve's earlier comment that Systems Engineering was being positioned as a problem space here.     (1G2AAAAAAAS)

Fabian Neuhaus: @Todd. Hmmm? I tried to argue that a problem driven Summit is more interesting than a     (1G2AAAAAAAT)

discussion about technology     (1G2AAAAAAAU)

Todd Schneider: Fabian, how about the problem of requirements elicitation?     (1G2AAAAAAAV)

Jack Ring: How about just Big, Evolving Systems     (1G2AAAAAAAW)

Eric Chan: One caveat: "systems engineering" may not be inclusive enough for scientific disciplines     (1G2AAAAAAAX)

which are not engineering the system but understanding natural phenomenon     (1G2AAAAAAAY)

Matthew West: There is also the role of ontologies in the engineering of systems.     (1G2AAAAAAAZ)

Jack Ring: The problem of requirements elicitation is the presumption of requirements elicitation.     (1G2AAAAAAAAA)

Fabian Neuhaus: @Todd. Do you suggest "The problem of requirements elicitation" as a subject for the     (1G2AAAAAAAAB)

Todd Schneider: Fabian, it could be. It's part of systems engineering.     (1G2AAAAAAAAD)

Fabian Neuhaus: @ Todd. The majority of the organizing committee likes bigger themes. But I     (1G2AAAAAAAAE)

personally would have liked a problem on that scale.     (1G2AAAAAAAAF)

Amanda Vizedom: Following @FabianNeuhaus's comment: I can see "Systems Engineering" as either tool     (1G2AAAAAAAAG)

kit or problem space, in contrast to Fabian's view of it as a tool. But I think that the theme isn't     (1G2AAAAAAAAH)

focused enough, and is confusing, unless we get very clear on whether we mean SE as tool kit, SE as     (1G2AAAAAAAAI)

problem space, or SE as both, possibly paired with ontology as both in a variety of mutually     (1G2AAAAAAAAJ)

supportive relationships. I think the latter is what Peter is suggesting. But can we scope and focus     (1G2AAAAAAAAK)

that well enough?     (1G2AAAAAAAAL)

Jack Ring: let's do "Big Systems" or "Big Intelligent Systems"     (1G2AAAAAAAAM)

Ali Hashemi: @Jack -- do we have the wherewithal to push this term? I agree with the ambiguity around     (1G2AAAAAAAAN)

Systems Engineering... It seems like these novel phrases would suffer from the same problem,     (1G2AAAAAAAAO)

especially since this summit doesn't exactly have the highest profile.     (1G2AAAAAAAAP)

Todd Schneider: +1 for 'Big Systems' (it has a good spin)     (1G2AAAAAAAAQ)

Eric Chan: +1 Big Data Systems     (1G2AAAAAAAAR)

Peter P. Yim: +1 for "Big Intelligent Systems" ... (and we do BOTH "System Engineering" and "Big Data"     (1G2AAAAAAAAS)

under that umbrella)     (1G2AAAAAAAAT)

Bo Newman: One of the strengths of the ontology domain is that its meaning has not been diluted by an     (1G2AAAAAAAAU)

array of alternate terms. The way we name our themes and topics needs to re-enforce who we are     (1G2AAAAAAAAV)

rather than dilute the concept     (1G2AAAAAAAAW)

Amanda Vizedom: Same point about Big data, though -- we would need to focus in more than that. Big     (1G2AAAAAAAAX)

data usability? Big data management? It's Big!     (1G2AAAAAAAAY)

Martin Serrano: what about as theme Proposal --> Applied Ontologies: Towards bridging the gap between     (1G2AAAAAAAAZ)

Big Data Services and Systems Engineering     (1G2AAAAAAAAAA)

Barry Smith: Ontology is already making serious contributions to Big Data on many fronts -- above all     (1G2AAAAAAAAAB)

genomics, intelligence analysis, ...     (1G2AAAAAAAAAC)

Barry Smith: Suggested titles: Ontology and Big Data; Ontology and Big Data Systems; Ontology and Big     (1G2AAAAAAAAAD)

Intelligent Systems     (1G2AAAAAAAAAE)

Ali Hashemi: +1 - Ontology and Big Data Systems     (1G2AAAAAAAAAF)

Amanda Vizedom: Please give the choices before asking for votes on each.     (1G2AAAAAAAAAG)

Fabian Neuhaus: @ Amanda Vizedom: I agree that scoping would help a lot     (1G2AAAAAAAAAH)

Bo Newman: Suggest those with their "hand up" clear that first before the vote (click on the hand     (1G2AAAAAAAAAI)

Jack Ring: Intelllgent, scalable systems vs. Big Data vs. Systems Engineering     (1G2AAAAAAAAAK)

Steve Ray: == Please vote for: #1 Systems engineering ... #2 Big systems ... #3 Big data     (1G2AAAAAAAAAL)

Amanda Vizedom: @SteveRay: are these all "Ontology & ## ?"     (1G2AAAAAAAAAM)

Ali Hashemi: it show the number beside the Queue     (1G2AAAAAAAAAO)

Todd Schneider: Current thinking would suggest that solutions to 'big data' requires intelligent     (1G2AAAAAAAAAP)

systems. Intelligent systems need to be develop in an intelligent fashion.     (1G2AAAAAAAAAQ)

Amanda Vizedom: I still am not sure what it ("Big Data") means! I might have voted for it, otherwise.     (1G2AAAAAAAAAR)

Mike Bennett: I'm sort of assuming that the stuff we talked about re semantics sharing comes under     (1G2AAAAAAAAAV)

Big Data but not sure.     (1G2AAAAAAAAAW)

Ali Hashemi: can we vote twice? ... [ to which Steve verbally answered: "No" ]     (1G2AAAAAAAAAY)

Amanda Vizedom: But again, my choice between 2 and 3 might flip if I understood them better.     (1G2AAAAAAAAAZ)

Martin Serrano: I can't see a big difference between 2 and 3     (1G2AAAAAAAAAAA)

Peter P. Yim: == straw votes received: #1 Systems engineering - 3 ... #2 Big systems - 12 ... #3 Big     (1G2AAAAAAAAAAB)

Jack Ring: Please do not use complex. Intelligent or autonomous will attract more attention.     (1G2AAAAAAAAAAD)

Christopher Spottiswoode: Yes, autonomous - "intelligent" is easily misconstrued.     (1G2AAAAAAAAAAE)

Martin Serrano: I support the idea of Open Linked Data (Big Data) however Does Big systems come up as     (1G2AAAAAAAAAAF)

a bridging gap ?     (1G2AAAAAAAAAAG)

Ali Hashemi: That was my understanding for #2... (Big Data Systems)     (1G2AAAAAAAAAAH)

Jack Ring: Society needs big decisions not just more data     (1G2AAAAAAAAAAI)

Matthew West: Big Systems is supposed to be something more than just software.     (1G2AAAAAAAAAAJ)

Martin Serrano: I understood same, I hope that is the common and general agreement     (1G2AAAAAAAAAAK)

Barry Smith: how about something like "Big Data Systems" or "Ontology-based Systems for Big Data"     (1G2AAAAAAAAAAL)

Ali Hashemi: +1 to Barry's suggestion.     (1G2AAAAAAAAAAM)

Michael Riben: I like Barry's Suggestion +1     (1G2AAAAAAAAAAN)

Amanda Vizedom: Some of the ambiguity, in either case, will probably turn into tracks addressing the     (1G2AAAAAAAAAAO)

variant interpretations. But that increases the risk of being to big/unfocused.     (1G2AAAAAAAAAAP)

Jack Ring: Are you selecting themes for what needs to be said or what you all want to say?     (1G2AAAAAAAAAAR)

Amanda Vizedom: Big Data -> Big Information     (1G2AAAAAAAAAAS)

Amanda Vizedom: Semantically-enabled Big Data Systems     (1G2AAAAAAAAAAT)

Fabian Neuhaus: We are now just juggling words. This is not helping to get a focused topic.     (1G2AAAAAAAAAAU)

Matthew West: In big systems a major use of ontology is in data quality. That is not particularly     (1G2AAAAAAAAAAV)

Amanda Vizedom: A little bird is telling me that "exascale" is the buzzword for "big" now.     (1G2AAAAAAAAAAX)

Amanda Vizedom: Semantically-Enabled Exascale Data Systems --> SEEDS     (1G2AAAAAAAAAAY)

Martin Serrano: yeah in +1 in that comment     (1G2AAAAAAAAAAZ)

Todd Schneider: There are (too) many examples of 'big' systems that failed to be realized (i.e., that     (1G2AAAAAAAAAAAA)

were canceled after too much waste and intermediate failures) due to the complexity involved. The     (1G2AAAAAAAAAAAB)

use of ontological practices and ontologies may have helped avoid some of these failures.     (1G2AAAAAAAAAAAC)

Jack Ring: @Todd, quite so. And what made them complex, therefore not viable, was the use of     (1G2AAAAAAAAAAAD)

taxonomies, schema and data modeling.     (1G2AAAAAAAAAAAE)

Matthew West: Just stick with Ontology for Big Systems     (1G2AAAAAAAAAAAF)

Steve Ray: == Please vote now for: #1 Ontology for big ___ systems ... #2 No, to the above     (1G2AAAAAAAAAAAG)

Martin Serrano: Ontologies more make sense     (1G2AAAAAAAAAAAH)

Amanda Vizedom: too undefined for me to vote for either.     (1G2AAAAAAAAAAAI)

Amanda Vizedom: @Peter: sure, but what's in the "___"?     (1G2AAAAAAAAAAAJ)

Peter P. Yim: == straw votes received: #1 Ontology for big ___ systems - 17 ... #2 No, to the above - 0     (1G2AAAAAAAAAAAK)

(no serious objections)     (1G2AAAAAAAAAAAL)

Bo Newman: Good discussion .... need to drop off for another call ... thanks.     (1G2AAAAAAAAAAAM)

Jack Ring: Big Responsive Systems     (1G2AAAAAAAAAAAO)

Jack Ring: Can we address the point of forthcoming, massively parallel hardware?     (1G2AAAAAAAAAAAP)

Todd Schneider: Amanda, how about a simple ontology for the possible tracks discussed today? That     (1G2AAAAAAAAAAAQ)

would then suggest what should be addressed.     (1G2AAAAAAAAAAAR)

Steve Ray: == Please vote now for: #1: Ontology for Big Systems; #2 Ontology for Big ... Systems     (1G2AAAAAAAAAAAS)

Steve Ray: #2 Ontology for Big ... Systems reads: "Ontology for Big ..(something).. Systems" - we     (1G2AAAAAAAAAAAT)

will have to deal with the "something" in the organizing committee (if this is voted in.)     (1G2AAAAAAAAAAAU)

Amanda Vizedom: Sounds like a job for Survey Monkey or a Doodle Poll with rapid iterations.     (1G2AAAAAAAAAAAV)

Jack Ring: The Vote button above does that.     (1G2AAAAAAAAAAAW)

Amanda Vizedom: Ooh, vote button does multiple or order votes. Could do quick paste of all     (1G2AAAAAAAAAAAX)

suggestions and vote.     (1G2AAAAAAAAAAAY)

Peter P. Yim: we've tried the "vote" button mechanism before, and were a bit challenged, let's just     (1G2AAAAAAAAAAAZ)

(continue to) use a show of hands (with the "hand" button.)     (1G2AAAAAAAAAAAAA)

Peter P. Yim: == straw votes received: #1 Ontology for big systems - 10 ... #2 Ontology for Big     (1G2AAAAAAAAAAAAB)

..(something).. Systems - 5     (1G2AAAAAAAAAAAAC)

Peter P. Yim: == We have a Theme for Ontology Summit 2012 - "Ontology for Big Systems"     (1G2AAAAAAAAAAAAD)

Jack Ring: There will be a track for each 'dot"     (1G2AAAAAAAAAAAAE)

Mike Bennett: Hard to get an idea of what goes in among the dots though.     (1G2AAAAAAAAAAAAF)

Jack Ring: Let the tracks nominate the dots     (1G2AAAAAAAAAAAAG)

Matthew West: Please suggest something for the dots if you think we should go that way.     (1G2AAAAAAAAAAAAH)

Ali Hashemi: "Ontology for Big Data Systems"     (1G2AAAAAAAAAAAAI)

Matthew West: @Ali, well that could easily be a thread anyway.     (1G2AAAAAAAAAAAAK)

Peter P. Yim: == Please volunteer: name and facet under the theme that you want to help tackle ==     (1G2AAAAAAAAAAAAL)

Jack Ring: Track: Implications of forthcoming massively parallel hardware.     (1G2AAAAAAAAAAAAM)

Peter P. Yim: == please suggest track titles and make any other pertinent suggestions ==     (1G2AAAAAAAAAAAAN)

Amanda Vizedom: I will volunteer for a Quality in Context Track (fitness for purpose, evaluation,     (1G2AAAAAAAAAAAAO)

metrics and metrics) under whichever theme.     (1G2AAAAAAAAAAAAP)

Jack Ring: @Amanda, are you including the quality of an ontology?     (1G2AAAAAAAAAAAAQ)

Amanda Vizedom: Yes, that's what I mean, thanks for asking. The track I'm suggesting is the     (1G2AAAAAAAAAAAAR)

theme-focused variant of the topic Joanne and I suggested     (1G2AAAAAAAAAAAAS)

might be "Ontology Quality in Big System applications" or something like that. Or, "Evaluating     (1G2AAAAAAAAAAAAU)

Ontologies for Use in Big [X] Systems Applications"     (1G2AAAAAAAAAAAAV)

Ken Allgood: I will volunteer for Ontology in electronic health record/bioinformatics     (1G2AAAAAAAAAAAAW)

Michael Riben: idea for track- NoSQL infrastructure and Ontology for Big Data and Cloud systems     (1G2AAAAAAAAAAAAX)

Pat Cassidy: I would be willing to champion a track on exploring the use of a common foundation     (1G2AAAAAAAAAAAAY)

ontology as a translation mechanism (interlingua) among multiple databases or multiple systems -     (1G2AAAAAAAAAAAAZ)

large or small. But if there are no others to make a "track" out of this, I can just present a paper     (1G2AAAAAAAAAAAAAA)

Mike Bennett: I'd like to suggest ontology sharing etc. but don't have the bandwidth to head this up.     (1G2AAAAAAAAAAAAAC)

Matthew West: If there is interest in a thread on ontology of big engineering systems, I'm happy to     (1G2AAAAAAAAAAAAAD)

Todd Schneider: How about 'Ontological Analysis in Systems Engineering'?     (1G2AAAAAAAAAAAAAF)

Matthew West: @Todd That sounds close to what I was suggesting. Happy to merge.     (1G2AAAAAAAAAAAAAG)

Todd Schneider: Matthew, sound good to merge.     (1G2AAAAAAAAAAAAAH)

Jack Ring: I was volunteering to organize a track on the hardware implications.     (1G2AAAAAAAAAAAAAI)

Eric Chan: + for aligning dots to tracks, I have Data, Process, Engineered, Multi-disciplinary,     (1G2AAAAAAAAAAAAAJ)

Michael Riben: tract title: Enhancing Big Data Analytics with Ontologies     (1G2AAAAAAAAAAAAAK)

Ken Allgood: I'd recommend "information interoperability across federated data"     (1G2AAAAAAAAAAAAAL)

Peter P. Yim: == please suggest: what do we want to see as an outcome of this Summit ... (in particular,     (1G2AAAAAAAAAAAAAM)

what can we say on the Communique)? ==     (1G2AAAAAAAAAAAAAN)

Jack Ring: @Peter, I hope the outcome will be an ontology!!     (1G2AAAAAAAAAAAAAO)

Todd Schneider: Jack, Excellent thought, but an ontology of what?     (1G2AAAAAAAAAAAAAP)

Matthew West: @Todd - an ontology of systems (broad sense) might be a possibility.     (1G2AAAAAAAAAAAAAQ)

Jack Ring: @Todd, An ontology of benefits of ontology-based systems and decisions.     (1G2AAAAAAAAAAAAAR)

Jack Ring: Ralph Hodgson produced an ontology-based user interface for Semantic Technology Conference     (1G2AAAAAAAAAAAAAT)

in 2008 or thereabouts.     (1G2AAAAAAAAAAAAAU)

Ken Allgood: @Jack.. we could certainly leverage Ralph's work.     (1G2AAAAAAAAAAAAAV)

Jack Ring: @Ken, suggest you contact him at     (1G2AAAAAAAAAAAAAW)

Ken Allgood: @Jack.. Already on it. Might also catch him at the next DC Semantic meetup     (1G2AAAAAAAAAAAAAX)

Ken Allgood: "Ontology-driven user experience in big data"     (1G2AAAAAAAAAAAAAY)

Ali Hashemi: @Steve -- at the end of the last summit, there was a consideration to alongside a     (1G2AAAAAAAAAAAAAZ)

Communique, explicitly commit to creating a website for the summit?     (1G2AAAAAAAAAAAAAAA)

Ali Hashemi: I can volunteer, but I definitely won't be able to do it alone.     (1G2AAAAAAAAAAAAAAB)

Ken Allgood: I could assist Ali in the website     (1G2AAAAAAAAAAAAAAC)

Amanda Vizedom: I'd like to see a track refining "Big Systems," either focusing down or presenting     (1G2AAAAAAAAAAAAAAD)

some branches/subtopics.     (1G2AAAAAAAAAAAAAAE)

Amanda Vizedom: Track proposal: Use cases / examples? "Use Cases for Ontologies in Big Systems"     (1G2AAAAAAAAAAAAAAF)

Amanda Vizedom: For that use cases suggestion, I'd imagine that as a track under which we bring in     (1G2AAAAAAAAAAAAAAG)

some folks in various domains and/or projects to describe particular cases where ontologies are     (1G2AAAAAAAAAAAAAAH)

being brought in to support big systems.     (1G2AAAAAAAAAAAAAAI)

Peter P. Yim: @JackRing & Ali Hashemi ... good point! -- the "tradition" so far is to have a Communique     (1G2AAAAAAAAAAAAAAJ)

... therefore additional outcomes (a survey/study; a website; an ontology, etc.) need, first and     (1G2AAAAAAAAAAAAAAK)

foremost, leadership and volunteered resources (i.e. people's time and effort)     (1G2AAAAAAAAAAAAAAL)

Peter P. Yim: I am in favor of adding "a website" or "an ontology" as the deliverable ... please step up     (1G2AAAAAAAAAAAAAAM)

to the plate - we need leadership and volunteers!     (1G2AAAAAAAAAAAAAAN)

Jack Ring: FWIW, I am greatly encouraged by all this. Thank you all for your ideas and energy. Gotta go.     (1G2AAAAAAAAAAAAAAP)

Tim Darr: I have to go as well ...     (1G2AAAAAAAAAAAAAAQ)

Peter P. Yim: == Please suggest who else (communities / individuals) we should engage ==     (1G2AAAAAAAAAAAAAAR)

Mike Bennett: I'm also working with the OMG though not as much of an expert as Elisa. Happy to make     (1G2AAAAAAAAAAAAAAS)

Matthew West: There is a well known international institute of Systems Engineering INCOSE     (1G2AAAAAAAAAAAAAAU)

Peter P. Yim: @Matthew or anyone - can you help engage INCOSE?     (1G2AAAAAAAAAAAAAAV)

Steve Ray: I could approach some of the NIST folks for an INCOSE connection - no guarantees.     (1G2AAAAAAAAAAAAAAW)

Ken Allgood: Peter & Steve.. Thanks for bringing this together.     (1G2AAAAAAAAAAAAAAX)

Peter P. Yim: great session ... thanks everyone!     (1G2AAAAAAAAAAAAAAZ)

Steve Ray: Take care all, and happy holidays.     (1G2AAAAAAAAAAAAAAAB)

Peter P. Yim: -- session ended: 11:10am PST --     (1G2AAAAAAAAAAAAAAAC)

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

Resources     (1H)

  • To participate:     (1H2)
    • please post further thoughts to the [ ontology-summit ] listserv     (1H2A)
    • all subscribers to the previous summit discussion, and all who responded to today's call will automatically be subscribed to the [ ontology-summit ] listserv     (1H2B)
    • if you are already subscribed, post to <ontology-summit [at]>     (1H2C)
      • all previous subscribers on the list from the past year will be retained. (If you want to be removed, please by sending a blank email to <ontology-summit-leave [at]> from your subscribing email address, or send a note to <> to request that be done for you.)     (1H2C1)
    • (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.     (1H2D)

Audio Recording of this Session     (1I)

For the record ...     (1I6)

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

  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at:     (1J4E)
    • view-only password: "ontolog"     (1J4E1)
    • 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.     (1J4E2)
    • 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.     (1J4E3)
    • 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").     (1J4F1)
    • 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.     (1J4F2)
    • 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!     (1J4F3)
  • Discussions and Q & A:     (1J4G)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1J4G1)
    • 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.)     (1J4G2)
    • 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.)     (1J4G3)
    • 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.)     (1J4G4)
  • RSVP to appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1J4I)
  • 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.     (1J4K)

Attendees     (1K)

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