From OntologPSMW

Jump to: navigation, search
[ ]

Contents

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

Topic: "Rethinking our Funding Strategy" - Brainstorm Session     (1A)

Session Chair: KenBaclawski (Northeastern University)     (1B)

  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at: http://vnc2.cim3.net:5800/     (1C7E)
    • view-only password: "ontolog"     (1C7E1)
    • 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.     (1C7E2)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please point your browser directly to the slides (where applicable) and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1C7E3)
    • 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").     (1C7F1)
    • 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.     (1C7F2)
    • thanks to the soaphub.org 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) oor_20120814@soaphub.org ... Handy for mobile devices!     (1C7F3)
  • Discussions and Q & A:     (1C7G)
    • Nominally, when a presentation is in progress, the moderator will mute everyone, except for the speaker.     (1C7G1)
    • 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.)     (1C7G2)
    • 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.)     (1C7G3)
    • 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.)     (1C7G4)
  • RSVP to peter.yim@cim3.com appreciated, ... or simply just by adding yourself to the "Expected Attendee" list below (if you are a member of the team.)     (1C7H)
  • 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.     (1C7J)

Attendees     (1D)

  • Expecting:     (1D2)
    • ... if you are coming to the meeting, please add your name above (plus your affiliation, if you aren't already a member of the community) above, or e-mail <peter.yim@cim3.com> so that we can reserve enough resources to support everyone's participation. ...     (1D3A)

Agenda Ideas     (1D5)

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

Abstract     (1E)

Topic: "Rethinking our Funding Strategy" - Brainstorm Session     (1E1)

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.     (1E2)

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

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.     (1E4)

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.     (1E5)

Resources     (1F)

Agenda     (1G)

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

Proceedings     (1H)

Please refer to the above     (1H1)

IM Chat Transcript captured during the session    (1H2)

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

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

-- begin in-session chat-transcript --     (1H2C)

[08:25] Peter P. Yim: Welcome to the     (1H2D)

"OOR Funding" Workshop-II - Tue 2012_08_21     (1H2E)

Topic: "Rethinking our Funding Strategy" - Brainstorm Session     (1H2F)

Session Chair: Ken Baclawski (Northeastern University)     (1H2G)

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

Can't find Skype Dial pad?     (1H2J)

  • for Windows Skype users: Can't find Skype Dial pad? ... it's under the "Call" dropdown menu as "Show Dial pad"     (1H2K)
  • for Linux Skype users: please stay with (or downgrade to) Skype version 2.x for now     (1H2L)

(as a Dial pad seems to be missing on Linux-based Skype v4.x for skype-calls.)     (1H2M)

Proceedings:     (1H2P)

[08:25] Peter P. Yim: Hi Terry!     (1H2Q)

[08:27] Terry Longstreth: Hi Peter. Don't know what I can contribute today, but I'm curious.     (1H2R)

[08:33] anonymous morphed into Shannon Copeland     (1H2S)

[08:34] Bob Smith : Hi Shannon     (1H2T)

[08:35] Mike Bennett: Hi Shannon, glad you could make it.     (1H2U)

[08:35] Peter P. Yim: -- session started: 8:35am PDT --     (1H2V)

[08:36] Peter P. Yim: == Ken Baclawski starts with the slides     (1H2W)

[08:38] Peter P. Yim: slides are at:     (1H2X)

[08:50] Peter P. Yim: see a listing of the various OOR instances, and who's on the OOR.NET network, at:     (1H2Z)

[08:58] Peter P. Yim: == open discussion begins ...     (1H2AB)

[08:59] Terry Longstreth: Project Goals (Larger scope) :     (1H2AC)

1-Show capability for fostering reuse of cataloged concepts     (1H2AD)

2-Show methodology for fusing conceptual models (i.e. Ontology interoperability - OntoIOp) and managing the evolution of fused models     (1H2AE)

3-Demonstrate feasibility of managing heterogeneous concept description languages     (1H2AF)

Unsaid - a fused ontology, derived from heterogeneous sources is (cheaper, faster, better) solution than inventing new ontology 'by hand'     (1H2AG)

[09:11] Terry Longstreth: Business Case:     (1H2AH)

Value Proposition -     (1H2AI)

Advantages of an OOR for management of concept relationships across a specific application domain     (1H2AJ)

Resource requirements / Costs     (1H2AK)

- Define business entity to manage work (foundation/consortium)     (1H2AM)

- Define transition from development to Ontology management role     (1H2AN)

- Different from open source software     (1H2AO)

- the goal is to have a sharable, manageable, evolvable knowledge base, in perpetuity.     (1H2AP)

- as concepts evolve, users are impacted     (1H2AQ)

[09:23] Bob Smith : An OASIS TC has recently developed a White Paper that relates to Terry's     (1H2AR)

Management point - Transforming Government Framework (TGF) and a Pattern Language for implementing     (1H2AS)

that Framework. http://www.PeterFBrown.com summarizes the business case for TGF.     (1H2AT)

[09:22] Todd Schneider: Terry, go you explain your point about 'management' further?     (1H2AV)

[09:27] Todd Schneider: We should distinguish between operating an instance of OOR and 'active'     (1H2AW)

management of the content residing in an instance.     (1H2AX)

[09:10] Peter P. Yim: role models: Apache Foundation; Linux;     (1H2AY)

[09:11] Peter P. Yim: my opinion, ideally: A Foundation with an endowment would be a great model to pursue     (1H2AZ)

[09:12] Todd Schneider: What organization funded the Semantic Media Wiki work?     (1H2AAA)

[09:13] Todd Schneider: Vulcan, wasn't it?     (1H2AAB)

[09:13] Mike Dean: Todd: yes     (1H2AAC)

[09:16] Todd Schneider: So would Vulcan be an option? I don't anything about them.     (1H2AAD)

[09:13] Mike Bennett / Peter P. Yim: EDMCouncil, OMG, OASIS ... all work on a "Membership" model, where     (1H2AAE)

they get their operating funding from member subscription fees     (1H2AAF)

[09:18] Mike Bennett: see: http://edmcouncil.org - is a 501(c)(6) "business league" organization     (1H2AAG)

[09:18] Mike Dean: EDM Council is a 501(c)(6) Business League - see irs.gov link -     (1H2AAH)

[09:17] Bob Smith : Ken - Looking at your Ontologies for Bioinformatics book - and the strong focus     (1H2AAJ)

on Bayesian Web - Maybe EDM - Mike Bennett might find strong interest in a mutual project??     (1H2AAK)

[09:23] Mike Bennett: @Bob - indeed. We would love to work with others. In addition to the model I     (1H2AAL)

described above, we are also seeking funding for those things that we can't simply do with staff     (1H2AAM)

member + members' voluntary effort. Ontology integration and common reuse of standards semantics is     (1H2AAN)

high on our agenda for this.     (1H2AAO)

[09:18] Shannon Copeland: Please see below the Overview of Red Hat's "mission" http://www.redhat.com     (1H2AAP)

which is a commercial organization that organizes and delivers open source technology to businesses     (1H2AAQ)

worldwide:     (1H2AAR)

Red Hat is a global leader in providing open source software technologies to enterprise customers.     (1H2AAT)

These offerings include our core enterprise operating system platform, Red Hat Enterprise Linux, our     (1H2AAU)

enterprise middleware platform, Red Hat JBoss Middleware, as well as our virtualization, cloud, and     (1H2AAV)

storage offerings and other Red Hat enterprise technologies. Our development and licensing model We     (1H2AAW)

employ an open source software development and licensing model that uses the collaborative input of     (1H2AAX)

a worldwide community of contributors to develop and enhance software. We actively participate in     (1H2AAY)

this community-oriented development process, often in a leadership role, and leverage it to create     (1H2AAZ)

our Red Hat- and JBoss-branded enterprise technologies. We believe that the open source development     (1H2AAAA)

and licensing model offers advantages for Red Hat and our customers over proprietary software     (1H2AAAB)

development and licensing models. Through the open source development model, we leverage a global     (1H2AAAC)

community of developers and users, whose collective resources and knowledge supplement the     (1H2AAAD)

developers we employ. As a result, we believe we are able to offer enhancements, fixes and upgrades     (1H2AAAE)

more quickly and with less development cost than is typical of many proprietary software vendors. In     (1H2AAAF)

turn, our customers are able to take advantage of the quality and value of open source software,     (1H2AAAG)

which we help develop, aggregate, integrate, test, certify, deliver, maintain and support for their     (1H2AAAH)

enterprise use. The collectively developed software is typically distributed under open source     (1H2AAAI)

licenses, such as the GNU General Public License and GNU Lesser General Public License, that     (1H2AAAJ)

generally permit access to human-readable software source code. These licenses also provide     (1H2AAAK)

relatively broad rights for licensees to use, copy, modify and distribute open source software.     (1H2AAAL)

These broad rights afford significant latitude for our customers to inspect, suggest changes,     (1H2AAAM)

customize or enhance the software if they so choose. Red Hats participation in the     (1H2AAAN)

community-oriented development process is illustrated by Red Hats sponsorship role in the Fedora     (1H2AAAO)

Project, JBoss.org and other open source communities. This participation enables us to leverage the     (1H2AAAP)

efforts of these worldwide communities, which we believe allows us to reduce both development cost     (1H2AAAQ)

and time and to enhance community acceptance and support of our offerings and technologies. Thus, we     (1H2AAAR)

are able to use the Fedora Project, JBoss.org and other open source communities as proving grounds     (1H2AAAS)

and virtual laboratories for innovations that we can draw upon for inclusion in our enterprise     (1H2AAAT)

technologies. Additionally, the open and transparent nature of these communities provides our     (1H2AAAU)

customers and potential customers with access and insights into the future direction of Red Hat     (1H2AAAV)

offerings and technologies. Our offerings Red Hat Enterprise Linux is an enterprise-class operating     (1H2AAAW)

system that runs on a broad range of hardware, including mainframes, servers, work stations and     (1H2AAAX)

personal computers. Red Hat Enterprise Linux is designed to meet the performance, reliability and     (1H2AAAY)

scalability demands of large and small enterprises, from the data center to the edge of the network     (1H2AAAZ)

to cloud deployments. Red Hat JBoss Middleware delivers a range of middleware technologies for     (1H2AAAAA)

developing, deploying and managing applications that are accessible via the Internet, corporate     (1H2AAAAB)

intranets, extranets, clouds and virtual private networks. Examples of applications deployed on Red     (1H2AAAAC)

Hat JBoss Middleware include hotel and airline reservation systems, online banking, credit card     (1H2AAAAD)

processing, securities trading, healthcare systems, customer and partner portals, retail and     (1H2AAAAE)

point-of-sale systems and telecommunications network infrastructure.     (1H2AAAAF)

[09:32] Shannon Copeland: Red Hat is a Billion Dollar company now; doubled their value in the last 3 years     (1H2AAAAG)

... theirs should be a model to consider ... they fund research and other open source project too     (1H2AAAAH)

[09:19] Mike Bennett: OMG also has a "sponsorship" structure as well with different levels of     (1H2AAAAI)

contributions and privileges     (1H2AAAAJ)

[09:20] Mike Bennett: Effort in development of standards, ontologies and so on, is by voluntary     (1H2AAAAK)

member effort, in response to perceived self interest of the institution in the activities. For OMG     (1H2AAAAL)

this might include tool vendors getting together to propose or update modeling language standards;     (1H2AAAAM)

in the EDM Council it's an investment on their part in common resources which they can then use     (1H2AAAAN)

(data quality matrices, data management maturity, FIBO ontology etc.).     (1H2AAAAO)

[09:32] Bob Smith: Perhaps a review of the OOR Mission (and implicit workflow processes) is worth a minute? Project Mission (17YN)     (1H2AAAAP)

The charter of the Open Ontology Repository (OOR) Initiative is to the promote the global use and sharing of ontologies by: (17ZH)     (1H2AAAAQ)

1. establishing a hosted registry-repository; (17ZI)     (1H2AAAAR)

2. enabling and facilitating open, federated, collaborative ontology repositories, and (17ZJ)     (1H2AAAAS)

3. establishing best practices for expressing interoperable ontology and taxonomy work in registry-repositories. (17ZK)     (1H2AAAAT)

... where, (19K3)     (1H2AAAAV)

An ontology repository is a facility where ontologies and related information artifacts can be stored, retrieved and managed. (19K5)     (1H2AAAAW)

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.     (1H2AAAAX)

[09:40] Peter P. Yim: [action] Shannon Copeland can help start a conversation with someone at Red Hat     (1H2AAAAY)

[09:41] Shannon Copeland: John Ryan Director, Global Business Development at Red Hat     (1H2AAAAAB)

[09:41] Todd Schneider: Have to. Good hunting.     (1H2AAAAAC)

[09:41] Todd Schneider: Oops, have to go.     (1H2AAAAAD)

[09:41] Mike Dean: another possibility is to join a foundation ... e.g. becoming an Apache Incubator     (1H2AAAAAE)

Project ... for infrastructure and visibility (more than for funding)     (1H2AAAAAF)

[09:43] Mike Dean: Andy Seaborne of Jena is VP, W3C Relations     (1H2AAAAAH)

[09:46] Peter P. Yim: [action] Mike Dean will take a lead to explore the above possibility     (1H2AAAAAI)

[09:49] Peter P. Yim: archives of material relating to our past NSF grant proposal are at:     (1H2AAAAAJ)

Need authenticate to access info:     (1H2AAAAAN)

> username = oor-nsf07601     (1H2AAAAAO)

> password = ***     (1H2AAAAAP)

[09:49] Terry Longstreth: Have to leave -- Good Luck     (1H2AAAAAQ)

[10:00] Michael Grüninger: ref. "Project Description" writeup included in     (1H2AAAAAR)

[10:01] Michael Grüninger: this writeup -     (1H2AAAAAT)

[10:05] Peter P. Yim: [action] Ken Baclawski will review the past proposal documents (the "Project Description"     (1H2AAAAAV)

writeup especially) and update that, so we have something everyone can use or borrow from     (1H2AAAAAW)

[10:01] Shannon Copeland: Thank you. I have to sign off. Great meeting.     (1H2AAAAAX)

[10:06] Bob Smith : Another call - Thanks,     (1H2AAAAAY)

[10:07] Peter P. Yim: next meeting focused on funding - possibly Oct-30 (that's the next open OOR     (1H2AAAAAZ)

meeting slot); Ken will decide and announce later. We can definitely talk about this some more     (1H2AAAAAAA)

during the regular monthly team conf calls at the beginning on Sep-4 and Oct-9 too.     (1H2AAAAAAB)

[10:08] Peter P. Yim: great meeting!     (1H2AAAAAAC)

[10:08] Peter P. Yim: -- session ended: 10:07am PDT --     (1H2AAAAAAD)

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

  • Further Question & Remarks - please post them to the [ oor-forum ] listserv     (1H2AAAAAAF)
    • all subscribers to the previous summit discussion, and all who responded to today's call will automatically be subscribed to the [ oor-forum ] listserv     (1H2AAAAAAF1)
    • if you are already subscribed, post to <oor-forum [at] ontolog.cim3.net>     (1H2AAAAAAF2)
    • Also, if you are not yet a member of the Ontolog community (i.e. if you are not yet subscribed to the [ontolog-forum] list) , you might consider become a member of the community. Please refer to membership details here.     (1H2AAAAAAF3)

4.1 Action items:     (1H2AAAAAAG)

4.2 Schedule Next Meeting & Adjourn:     (1H2AAAAAAI)

notes taken by: Peter P. Yim / 2012.08.22-16:44 PDT     (1H2AAAAAAM)

All participants, please review and edit to enhance accuracy and granularity of the documented proceedings.     (1H2AAAAAAN)


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