OpenOntologyRepository: "OOR Funding" Workshop-II - Tue 2012_08_21    (3DXR)

Topic: "Rethinking our Funding Strategy" - Brainstorm Session    (3DXS)

Session Chair: KenBaclawski (Northeastern University)    (3DXT)

Archives:    (3E9C)

Conference Call Details:    (3E9J)

Attendees    (3EA9)

Agenda Ideas:    (3EAJ)

please insert any additional items below (along with your name for follow-up purposes)    (3EAK)

Abstract:    (3EAM)

Topic: "Rethinking our Funding Strategy" - Brainstorm Session    (3EAN)

While the core OOR team has kept the momentum on the Open Ontology Repository Initiative going ever since it begun in early 2008 (Big THANKS, Everyone!), the overall OOR initiative, has not had any funding even up to now, and had relied totally on volunteered effort. The progress on OOR could have been more expedient and predictable, if the entire initiative, and some of the core work, has some sort of funding to allow it to engage resources for getting things done when needed.    (3EAO)

This is a renewed effort on getting OOR funded. KenBaclawski, who co-lead an earlier proposal effort (our response to NSF solicitation 07-601) will continue to provide leadership and help facilitate the process.    (3EAP)

We will use this workshop to strategize and brainstorm on how we should approach this very important question going forward. We will not confine ourselves to seeking research grants (as we had, predominantly, before) but will try to look at any and all opportunity or possibility that would help fund and make the OOR Initiative deliver the mission it had set out to accomplish.    (3EAQ)

The plan for this session is to use the time of this session as fairly open discussion on the issue. There will not be formal presentations. The chair will try to help focus our discussion.    (3EAR)

Resources:    (3EBA)

Agenda:    (3EAS)

Session Format: this is a virtual session conducted over an augmented conference call    (3EAU)

Proceedings:    (3EAZ)

Please refer to the above    (3EB0)

IM Chat Transcript captured during the session:    (3EB1)

 (for better clarity, the version below is a re-organized and lightly edited chat-transcript.)
 Participants are welcome to make light edits to their own contributions as they see fit.    (3EB3)
 -- begin in-session chat-transcript --    (3EB4)
	[08:25] PeterYim: Welcome to the    (3EDZ)
	 = "OOR Funding" Workshop-II - Tue 2012_08_21 =    (3EE0)
	Topic: "Rethinking our Funding Strategy" - Brainstorm Session    (3EE1)
	Session Chair: KenBaclawski (Northeastern University)    (3EE2)
	Session page:    (3EE3)
	Mute control: *7 to un-mute ... *6 to mute    (3EE4)
	Can't find Skype Dial pad? 
	* for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad" 
	* for Linux Skype users: please stay with (or downgrade to) Skype version 2.x for now 
	  (as a Dial pad seems to be missing on Linux-based Skype v4.x for skype-calls.)    (3EE5)
	Attendees: KenBaclawski (chair), BobSmith, MichaelGruninger, MikeBennett, MikeDean, PeterYim 
	(scribe), ShannonCopeland, TerryLongstreth, ToddSchneider    (3EE6)
	 == Proceedings: ==    (3EE7)
	[08:25] PeterYim: Hi Terry!    (3EE8)
	[08:27] TerryLongstreth: Hi Peter. Don't know what I can contribute today, but I'm curious.    (3EE9)
	[08:33] anonymous morphed into ShannonCopeland    (3EEA)
	[08:34] BobSmith : Hi Shannon    (3EEB)
	[08:35] MikeBennett: Hi Shannon, glad you could make it.    (3EEC)
	[08:35] PeterYim: -- session started: 8:35am PDT --    (3EED)
	[08:36] PeterYim: == KenBaclawski starts with the slides    (3EEE)
	[08:38] PeterYim: slides are at:    (3EEF)
	[08:50] PeterYim: see a listing of the various OOR instances, and who's on the OOR.NET network, at:    (3EEG)
	[08:58] PeterYim: == open discussion begins ...    (3EEH)
	[08:59] TerryLongstreth: Project Goals (Larger scope) : 
	1-Show capability for fostering reuse of cataloged concepts
	2-Show methodology for fusing conceptual models (i.e. Ontology interoperability - OntoIOp) and managing the evolution of fused models
	3-Demonstrate feasibility of managing heterogeneous concept description languages    (3EEI)
	Unsaid - a fused ontology, derived from heterogeneous sources is (cheaper, faster, better) solution than inventing new ontology 'by hand'    (3EEJ)
	[09:11] TerryLongstreth: Business Case:
	Value Proposition - 
	Advantages of an OOR for management of concept relationships across a specific application domain
	Resource requirements / Costs
	 - Define business entity to manage work (foundation/consortium)
	 - Define transition from development to Ontology management role
	 - Different from open source software 
	 - the goal is to have a sharable, manageable, evolvable knowledge base, in perpetuity.
	 - as concepts evolve, users are impacted    (3EEK)
	[09:23] BobSmith : An OASIS TC has recently developed a White Paper that relates to Terry's 
	Management point - Transforming Government Framework (TGF) and a Pattern Language for implementing 
	that Framework. summarizes the business case for TGF.    (3EEL)
	[09:24] BobSmith :    (3EEM)
	[09:22] ToddSchneider: Terry, go you explain your point about 'management' further?    (3EEN)
	[09:27] ToddSchneider: We should distinguish between operating an instance of OOR and 'active' 
	management of the content residing in an instance.    (3EEO)
	[09:10] PeterYim: role models: Apache Foundation; Linux;    (3EEP)
	[09:11] PeterYim: my opinion, ideally: A Foundation with an endowment would be a great model to pursue    (3EEQ)
	[09:12] ToddSchneider: What organization funded the Semantic Media Wiki work?    (3EER)
	[09:13] ToddSchneider: Vulcan, wasn't it?    (3EES)
	[09:13] MikeDean: Todd: yes    (3EET)
	[09:16] ToddSchneider: So would Vulcan be an option? I don't anything about them.    (3EEU)
	[09:13] MikeBennett / PeterYim: EDMCouncil, OMG, OASIS ... all work on a "Membership" model, where 
	they get their operating funding from member subscription fees    (3EEV)
	[09:18] MikeBennett: see: - is a 501(c)(6) "business league" organization    (3EEW)
	[09:18] MikeDean: EDM Council is a 501(c)(6) Business League - see link -,,id=96107,00.html    (3EEX)
	[09:17] BobSmith : Ken - Looking at your Ontologies for Bioinformatics book - and the strong focus 
	on Bayesian Web - Maybe EDM - MikeBennett might find strong interest in a mutual project??    (3EEY)
	[09:23] MikeBennett: @Bob - indeed. We would love to work with others. In addition to the model I 
	described above, we are also seeking funding for those things that we can't simply do with staff 
	member + members' voluntary effort. Ontology integration and common reuse of standards semantics is 
	high on our agenda for this.    (3EEZ)
	[09:18] ShannonCopeland: Please see below the Overview of Red Hat's "mission" 
	which is a commercial organization that organizes and delivers open source technology to businesses 
	worldwide:    (3EF0)
	[09:18] ShannonCopeland: OVERVIEW    (3EF1)
	Red Hat is a global leader in providing open source software technologies to enterprise customers. 
	These offerings include our core enterprise operating system platform, Red Hat Enterprise Linux, our 
	enterprise middleware platform, Red Hat JBoss Middleware, as well as our virtualization, cloud, and 
	storage offerings and other Red Hat enterprise technologies. Our development and licensing model We 
	employ an open source software development and licensing model that uses the collaborative input of 
	a worldwide community of contributors to develop and enhance software. We actively participate in 
	this community-oriented development process, often in a leadership role, and leverage it to create 
	our Red Hat- and JBoss-branded enterprise technologies. We believe that the open source development 
	and licensing model offers advantages for Red Hat and our customers over proprietary software 
	development and licensing models. Through the open source development model, we leverage a global 
	community of developers and users, whose collective resources and knowledge supplement the 
	developers we employ. As a result, we believe we are able to offer enhancements, fixes and upgrades 
	more quickly and with less development cost than is typical of many proprietary software vendors. In 
	turn, our customers are able to take advantage of the quality and value of open source software, 
	which we help develop, aggregate, integrate, test, certify, deliver, maintain and support for their 
	enterprise use. The collectively developed software is typically distributed under open source 
	licenses, such as the GNU General Public License and GNU Lesser General Public License, that 
	generally permit access to human-readable software source code. These licenses also provide 
	relatively broad rights for licensees to use, copy, modify and distribute open source software. 
	These broad rights afford significant latitude for our customers to inspect, suggest changes, 
	customize or enhance the software if they so choose. Red Hats participation in the 
	community-oriented development process is illustrated by Red Hats sponsorship role in the Fedora 
	Project, and other open source communities. This participation enables us to leverage the 
	efforts of these worldwide communities, which we believe allows us to reduce both development cost 
	and time and to enhance community acceptance and support of our offerings and technologies. Thus, we 
	are able to use the Fedora Project, and other open source communities as proving grounds 
	and virtual laboratories for innovations that we can draw upon for inclusion in our enterprise 
	technologies. Additionally, the open and transparent nature of these communities provides our 
	customers and potential customers with access and insights into the future direction of Red Hat 
	offerings and technologies. Our offerings Red Hat Enterprise Linux is an enterprise-class operating 
	system that runs on a broad range of hardware, including mainframes, servers, work stations and 
	personal computers. Red Hat Enterprise Linux is designed to meet the performance, reliability and 
	scalability demands of large and small enterprises, from the data center to the edge of the network 
	to cloud deployments. Red Hat JBoss Middleware delivers a range of middleware technologies for 
	developing, deploying and managing applications that are accessible via the Internet, corporate 
	intranets, extranets, clouds and virtual private networks. Examples of applications deployed on Red 
	Hat JBoss Middleware include hotel and airline reservation systems, online banking, credit card 
	processing, securities trading, healthcare systems, customer and partner portals, retail and 
	point-of-sale systems and telecommunications network infrastructure.    (3EF2)
	[09:32] ShannonCopeland: Red Hat is a Billion Dollar company now; doubled their value in the last 3 years
	 ... theirs should be a model to consider ... they fund research and other open source project too    (3EF3)
	[09:19] MikeBennett: OMG also has a "sponsorship" structure as well with different levels of 
	contributions and privileges    (3EF4)
	[09:20] MikeBennett: Effort in development of standards, ontologies and so on, is by voluntary 
	member effort, in response to perceived self interest of the institution in the activities. For OMG 
	this might include tool vendors getting together to propose or update modeling language standards; 
	in the EDM Council it's an investment on their part in common resources which they can then use 
	(data quality matrices, data management maturity, FIBO ontology etc.).    (3EF5)
	[09:32] BobSmith: Perhaps a review of the OOR Mission (and implicit workflow processes) is worth a minute?  Project Mission    (17YN)    (3EF6)
	The charter of the Open Ontology Repository (OOR) Initiative is to the promote the global use and sharing of ontologies by:    (17ZH)
	 1. establishing a hosted registry-repository;    (17ZI)
	 2. enabling and facilitating open, federated, collaborative ontology repositories, and    (17ZJ)
	 3. establishing best practices for expressing interoperable ontology and taxonomy work in registry-repositories.    (17ZK)
	(ref. )    (17ZL)
	... where,    (19K3)
	An ontology repository is a facility where ontologies and related information artifacts can be stored, retrieved and managed.    (19K5)    (3EF7)
	Note that the "Open Ontology Repository (OOR) Initiative" is supposed to be an independent effort, and is only being incubated in the Ontolog collaborative work environment, for the time being.    (3EF8)
	[09:40] PeterYim: [action] ShannonCopeland can help start a conversation with someone at Red Hat    (3EF9)
	[09:40] ShannonCopeland:*1_*1_*1_*1_*1_*1_*2_*1_Y_*1_*1_*1_false_1_R_*1_*51_*1_*51_true_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2_*2&pvs=ps&trk=pp_profile_name_link    (3EFA)
	[09:41] ShannonCopeland: John Ryan Director, Global Business Development at Red Hat    (3EFB)
	[09:41] ToddSchneider: Have to. Good hunting.    (3EFC)
	[09:41] ToddSchneider: Oops, have to go.    (3EFD)
	[09:41] MikeDean: another possibility is to join a foundation ... e.g. becoming an Apache Incubator 
	Project ... for infrastructure and visibility (more than for funding)    (3EFE)
	[09:43] MikeDean:    (3EFF)
	[09:43] MikeDean: Andy Seaborne of Jena is VP, W3C Relations    (3EFG)
	[09:46] PeterYim: [action] MikeDean will take a lead to explore the above possibility    (3EFH)
	[09:49] PeterYim: archives of material relating to our past NSF grant proposal are at:
	 Message Archives:
	 Shared Files:
	 Need authenticate to access info:
	 >  username = oor-nsf07601
	 >  password = ***    (3EFI)
	[09:49] TerryLongstreth: Have to leave -- Good Luck    (3EFJ)
	[10:00] MichaelGruninger: ref. "Project Description" writeup included in    (3EFK)
	[10:01] MichaelGruninger: this writeup - - is still quite relevant    (3EFL)
	[10:05] PeterYim: [action] KenBaclawski will review the past proposal documents (the "Project Description" 
	writeup especially) and update that, so we have something everyone can use or borrow from    (3EFM)
	[10:01] ShannonCopeland: Thank you. I have to sign off. Great meeting.    (3EFN)
	[10:06] BobSmith : Another call - Thanks,    (3EFO)
	[10:07] PeterYim: next meeting focused on funding - possibly Oct-30 (that's the next open OOR 
	meeting slot); Ken will decide and announce later. We can definitely talk about this some more 
	during the regular monthly team conf calls at the beginning on Sep-4 and Oct-9 too.    (3EFP)
	[10:08] PeterYim: great meeting!    (3EFQ)
	[10:08] PeterYim: -- session ended: 10:07am PDT --    (3EFR)
 -- end of in-session chat-transcript --    (3EB5)

4.1 Action items:    (3EBK)

4.2 Schedule Next Meeting & Adjourn:    (3EBM)

 notes taken by: PeterYim / 2012.08.22-16:44 PDT
 All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.    (3EBT)