From OntologPSMW

Revision as of 16:27, 18 December 2012 by PeterYim (Talk | contribs)

Jump to: navigation, search
[ ]


This is a workspace collecting suggestions on how to better organize, coordinate and facilitate OntologySummit2012 activities. While mainly intended for the use by the organizing committee, this is an open page, and contributions from other summit participants who are not on the organizing committee are welcome.     (1A)

OntologySummit2012: Ontology for Big Systems     (1B)

7th in the series of a 3-month open annual event by and for the Ontology Community. This Summit is co-organized by Ontolog, NIST, NCOR, NCBO, IAOA & NCO_NITRD     (1B1)

ref. OntologySummit     (1B2)

Ideas on How to Frame the Discussion     (1C)

From the 2011_12_08 Pre-launch Community Session prep work:     (1C1)

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.     (1C1B)
o Software engineering     (1C1B1)
o Business rules and enterprise issues     (1C1B2)
o Socio-technical environment     (1C1B3)
o Big Data     (1C1B4)
o Ontology Quality in Context     (1C1B5)
"Big Data" to include several dimensions:     (1C1C)
o Complexity of collections     (1C1C1)
o Large quantities of data     (1C1C2)
o Heterogeneity of data (e.g. 600 different representations of patient records)     (1C1C3)
o Federation of distributed data sources     (1C1C4)
o Extracting (useful) knowledge out of big data (using ontology to UNDERSTAND data)     (1C1C5)
  • formulate recommendations for the application of ontological techniques to specific key problems we are facing in the subject area.     (1C1D)

From the 2011_12_08 community brainstorm input - items to note for action:     (1C2)

  • TimWilson: I have to leave the call soon, but I am very interested in     (1C2B)

the System Engineering aspects of Ontology as well as Ontology Acquisition, including text analytics.     (1C2C)

Systems Engineering and International Society for Systems Sciences is pursuing the development of a Unified Ontology for Systems Engineering. This effort is mostly practitioners getting ready for interaction with ontologists.     (1C2E)

(fitness for purpose, evaluation, metrics and metrics) under whichever theme.     (1C2G)

I'm suggesting is the theme-focused variant of the topic Joanne and I suggested here: A better title might be "Ontology Quality in Big System applications" or something like that. Or, "Evaluating Ontologies for Use in Big [X] Systems Applications"     (1C2I)

  • KenAllgood: I will volunteer for Ontology in electronic health     (1C2J)

record/bioinformatics     (1C2K)

Big Data and Cloud systems     (1C2M)

engineering systems, I'm happy to contribute.     (1C2O)

  • PatCassidy: I would be willing to champion a track on exploring the     (1C2Q)

use of a common foundation ontology as a translation mechanism (interlingua) among multiple databases or multiple systems - large or small. But if there are no others to make a "track" out of this, I can just present a paper with my views.     (1C2R)

the bandwidth to head this up.     (1C2T)

  • Eric Chan: + for aligning dots to tracks, I have Data, Process,     (1C2V)

Engineered, Multi-displinary,     (1C2W)

  • KenAllgood: I'd recommend "information interoperability across federated data"     (1C2Y)
  • AliHashemi: @Steve -- at the end of the last summit, there was a     (1C2Z)

consideration to alongside a Communique, explicitly commit to creating a website for the summit?     (1C2AA)

focusing down or presenting some branches/subtopics.     (1C2AD)

Ontologies in Big Systems"     (1C2AF)

track under which we bring in some folks in various domains and/or projects to describe particular cases where ontologies are being brought in to support big systems.     (1C2AH)

possibility.     (1C2AJ)

and decisions.     (1C2AL)