From OntologPSMW

Jump to: navigation, search
[ ]


Joint OOR-Ontolog-NCBO-CC-IAOA-OASIS "OpenOntologyRepository_IPR Policy and Issues" Panel Discussion (session-2) - Thu 16-Sep-2010     (1)

  • Topic: "OOR-IPR session 2: what are the IPR issues relating to open ontology repositories (and ontologies in general)?"     (1A)
  • Panelists:     (1C)
    • Mr. CameronRoss (Kojeware; OOR) - "Ecosystems, Ontology Repositories, and IPR" - [ slides ]     (1C1)
    • Professor AlanRector (University of Manchester) - Remarks: "The GALEN and SNOMED IPR experience" - [ abstract ]     (1C2)
    • Dr. JohnSowa (Vivomind Intelligence; SIO) - Remarks: "Issues with Patents" - [ slides ]     (1C3)
    • Mr. BrucePerens (original author of the "Open Source Definition") - Commentary     (1C4)
    • Mr. JohnWilbanks (VP of Science, Creative Commons) - Commentary     (1C5)
    • Mr. PeterYim (Co-convener, Ontolog & OOR; Secretary, IAOA) - "Questions to ALL: what are our issues now?" - [ slides ]     (1C6)

  • Shared-screen support (VNC session) will be started 5 minutes before the call at:     (1E5)
    • view-only password: "ontolog"     (1E5A)
    • 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.     (1E5B)
    • people behind corporate firewalls may have difficulty accessing this. If that is the case, please download the slides above and running them locally. The speaker(s) will prompt you to advance the slides during the talk.     (1E5C)
  • Discussions and Q & A:     (1E6)
    • (Unless the conference host has already muted everyone) Please mute your phone, by pressing "*2" on your phone keypad, when a presentation is in progress. To un-mute, press "*3"     (1E6A)
    • You can type in your questions or comments through the browser based chat session by:     (1E6B)
      • instructions: once you got access to the page, click on the "settings" button, and identify yourself (by modifying the Name field). 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.     (1E6C1)
    • (when everyone is muted) If you want to speak or have questions or remarks to make, please "raise your hand (virtually)" by click on the "hand button" (lower right) on the chat session page. You may speak when acknowledged by the speaker or the session moderator (again, press "*3" on your phone to unmute). 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 "*2" on your phone to mute yourself after you are done speaking.)     (1E6D)
    • 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!     (1E6E)
  • Please note that this session will be recorded, and the audio archive is expected to be made available as open content to our community membership and the public at-large under our prevailing open IPR policy.     (1E10)

Attendees     (1G)

Resources     (1G4)

Agenda & Proceedings     (1H)

Panel Discussion Session: "OOR-IPR session 2: what are the IPR issues relating to open ontology repositories (and ontologies in general)?"     (1H1)

Abstracts     (1I)

  • Session Topic: "OOR-IPR session 2: what are the IPR issues relating to open ontology repositories (and ontologies in general)?"     (1I1)
This "OOR-IPR mini-series" will, hopefully, start a dialog among the global ontology community, to specifically address IPR issues relating to the "open ontology repository (OOR)" initiative. The discussion will, invariably, touch upon IPR issues pertaining to ontology in general as well.     (1I2)
This mini-series is jointly organized by the OOR initiative, the Ontolog-community, NCBO (US National Center for Biomedical Ontology), CC (Creative Commons), IAOA (the International Association for Ontology and its Applications) and OASIS (Organization for the Advancement of Structured Information Standards).     (1I3)
Given the complexity of the issues involved, one can look as this mini-series to merely be the beginning of a quest, by the collaborating parties and their communities, to fully understand the issues, and to get themselves into a position to address them.     (1I4)
In this 2nd session, we will try to find out what, really, are the IPR issues relating to open ontology repositories in particular, and to ontologies, or even the science and technology of Ontology, in general. We will attempt to enumerate the pertinent issues and try to mitigate or address them one-by-one, if we can.     (1I5)
Please refer also to the background and thoughts collected during the process of organizing this mini-series, at: OpenOntologyRepository_IPR     (1I6)
Check out the full proceedings of the Launch Session of this OOR-IPR mini-series - ConferenceCall_2010_09_09     (1I7)

Panel Members Briefings     (1I8)

  • Title: "Ecosystems, Ontology Repositories, and IPR" - [ slides ]     (1I8A)
    • Abstract: ... This presentation will summarize some of the objectives, assumptions and issues that motivate this series of sessions on IPR. A brief explanation of how the OOR fits in to a larger ecosystem for semantic applications will also be presented, along with a recommendation to give IP provenance due consideration within the OOR initiative.     (1I8A2)
i) GALEN, which was a large collaborative development in the 1990s. In that development, all attempts to determine shares of intellectual property proved both expensive and futile. It was eventually made open source as the only practical solution.     (1I8C1)
ii) The continuing saga with SNOMED, which is currently "half open" and supported by different governments joining the parent organisation. However the lack of a completely open license continues to be a major issue and cost of dealing with SNOMED. For example, the WHO and the SNOMED organisation have taken at least two years and untold legal and executive time to reach an agreement.     (1I8C2)
IP is intimately related to funding models.     (1I8C3)
Both GALEN and SNOMED's experience point to the difficulty of achieving a revenue stream for ontologies meant to enable interoperability without strong legal backing, at least in health care. The only organisations that do so as far as I know are those that are backed by some form of mandate - CPT for clinical procedures in the US, ICD-CM in the US (to a lesser degree), ( I don't know how MEDDRA is funded - the reporting standard for adverse drug reactions).     (1I8C4)
Closed IP does not work well, but alternatives are difficult to point to.     (1I8C5)

Transcript of the online chat during the session     (1I9)

see raw transcript here.     (1I9A)

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

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

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

Welcome to the Joint OOR-Ontolog-NCBO-CC-IAOA-OASIS "OpenOntologyRepository_IPR Policy and Issues"     (1I9F)

Panel Discussion (session-2) - Thu 16-Sep-2010     (1I9G)

  • Topic: "OOR-IPR session 2: what are the IPR issues relating to open ontology repositories (and ontologies in general)?"     (1I9H)

o Mr. Cameron Ross (Kojeware; OOR) - "Ecosystems, Ontology Repositories, and IPR"     (1I9K)

o Professor Alan Rector (University of Manchester) - Remarks: "The GALEN and SNOMED IPR experience"     (1I9L)

o Dr. John F. Sowa (Vivomind Intelligence; SIO) - Remarks: "Issues with Patents"     (1I9M)

o Mr. Bruce Perens (original author of the "Open Source Definition") - Commentary     (1I9N)

o Mr. John Wilbanks (VP of Science, Creative Commons) - Commentary     (1I9O)

o Mr. Peter P. Yim (Co-convener, Ontolog & OOR; Secretary, IAOA) - "Questions to ALL: what are our issues now?"     (1I9P)

anonymous morphed into Terry Longstreth     (1I9S)

John Wilbanks: Peter P. Yim, I am on the line but muted     (1I9T)

John Wilbanks: in a noisy environment     (1I9U)

anonymous morphed into Alan Rector     (1I9W)

John Wilbanks: Peter P. Yim, can you speak up or increase your mic volume?     (1I9Z)

Ravi Sharma: @Cameron: why should OOR Support proprietary extensions? as mentioned in your slide.     (1I9AA)

Cameron Ross: @RaviSharma - Proprietary extension allow commercial entities to utilize the OOR.     (1I9AB)

Peter P. Yim: great ... Hi Bruce     (1I9AD)

Ravi Sharma: @Cameron: i view the OOR as a container, kindly compare the keystone unix Kernel with     (1I9AE)

technologies involved in creating and supporting OOR lifecycle, I also envisage OOR lifecycle to     (1I9AF)

have ecosystem like evolution where some technologies and ontologies will not be able to survive?     (1I9AG)

Cameron Ross: @RaviSharma - OOR being a compilation of the OOR content, the software used to     (1I9AH)

implement the OOR and the federation of specific OOR instances. The tools for creating and     (1I9AI)

supporting the OOR life-cycle help to define the content... the keystone would result from the uses     (1I9AJ)

of this content. Imagine that the OOR grows in terms of content and we have all kinds of     (1I9AK)

applications that build on top of it (define applications in a very general sense here). Now, take     (1I9AL)

away the OOR... ouch!     (1I9AM)

Ravi Sharma: @Cameron: excellent ELP     (1I9AN)

Alan Rector: One moment please - moving the microphone nearer I got cut off     (1I9AO)

Ali Hashemi: Are there slides online?     (1I9AP)

Peter P. Yim: @Ali - no slides for Alan's remarks     (1I9AQ)

John Wilbanks: this point is essential - the need to clarify and edit ontologies, not just refer to     (1I9AR)

John Wilbanks: here's an old example from 2007 -     (1I9AT)

ng_of_the_GO.     (1I9AV)

John Wilbanks: "The part_of relation in all OBO ontologies (and elsewhere in the RDF distribution) is     (1I9AX)

normalized to before being included in the Neurocommons RDF     (1I9AY)

distribution."     (1I9AZ)

Cameron Ross: @Alan - Contributions to Eclipse are also "viral" in the sense that you must contribute     (1I9AAA)

to the project under the Eclipse Public License. The primary difference, I believe, is that the EPL     (1I9AAB)

is open whereas the contribution to SNOMED is not.     (1I9AAC)

Bruce Perens: I would like to speak about challenging the patent.     (1I9AAE)

Ravi Sharma: @Dr. John Sowa - for obvious reasons given by you - Can such a patent be made to be     (1I9AAF)

rescinded or there is too much process involved?     (1I9AAG)

Ravi Sharma: @Bruce and John: can we request patent office to open their process in this particular     (1I9AAH)

case to determine if SMEs who understand Text Processing, Ontology, concepts were consulted or can     (1I9AAI)

now be inducted to review?     (1I9AAJ)

John Wilbanks: +1 for public patent foundation     (1I9AAK)

Frank Olken: Public Patent Foundation web site:     (1I9AAL)

Peter P. Yim: @Bruce - would you please type out the name and contact for Dan R so we can be sure we got     (1I9AAM)

his name right, please     (1I9AAN)

Bruce Perens: Daniel Ravisher at     (1I9AAP)

Frank Olken: PUBPAT Board of Directors - Daniel B. Ravicher, President and Executive Director     (1I9AAQ)

John Wilbanks: email is dan at pubpat dot org     (1I9AAR)

John F. Sowa: I suggest that Peter starts a wiki page (each) to collect prior art that is pertinent to     (1I9AAS)

the two example problematic patent/patent-application     (1I9AAT)

Peter P. Yim: will do ... thank you for the suggestion, John     (1I9AAU)

Peter P. Yim: @JohnSowa and All - I have initialized the wiki pages (to collect prior art for your two     (1I9AAV)

Ravi Sharma: @All- can we also sign a petition from community for patent office.     (1I9AAX)

Ravi Sharma: @ALL- I would like to know opinion in this group whether Ontology as a concept should     (1I9AAY)

not be communicated by us to be non-patentable as it is based on reasoning - (foundation of free     (1I9AAZ)

thinking and use of intellect), common knowledge from centuries, and connectedness to knowledge some     (1I9AAAA)

prior and some current that is inherently difficult to parse and separate.     (1I9AAAB)

Ravi Sharma: @JohnWilbanks - on the referred site above there is no entry for other-patents search     (1I9AAAD)

for Ontology?     (1I9AAAE)

Cameron Ross: So I guess ignorance is bliss!     (1I9AAAF)

Cameron Ross: @JohnWilbanks - Could you elaborate a bit on ontology interoperability v.s. openness?     (1I9AAAG)

Cameron Ross: @JohnWilbanks - Got it. Thanks.     (1I9AAAH)

Ravi Sharma: IS the question valid - whether ontologies are patentable?     (1I9AAAI)

Cameron Ross: @BrucePerens - What are your thoughts on the EPL 1.0?     (1I9AAAJ)

Cameron Ross: EPL = Eclipse Public Lincese     (1I9AAAK)

John Wilbanks: there is also the issue of US *public funding* for vast amounts of ontology work...     (1I9AAAL)

Bruce Perens: Freedom of thinking went out with the recent court decision in Vernor v. Autodesk. The     (1I9AAAM)

publisher can now license the WAY you use the information, as Sun has tried to do for a decade with     (1I9AAAN)

the Java reference books.     (1I9AAAO)

Cameron Ross: not funded = not sustainable     (1I9AAAQ)

Peter P. Yim: refer to PeterYim's slides #5 to #12 on "Questions to All participants"     (1I9AAAR)

Peter P. Yim: #6: Are you planning to contribute to the OOR effort; if yes, what would your     (1I9AAAS)

contribution(s) be?     (1I9AAAT)

John Wilbanks: we can bring our own research to the table     (1I9AAAV)

Ali Hashemi: 1) Yes (mainly COLORE). 2) Software/services(?)[requires other resources to be better     (1I9AAAW)

developed] - more so things that work with ontologies than ontologies themselves     (1I9AAAX)

Cameron Ross: Maybe, contributing mostly code and infrastructure, but the degree of my contribution     (1I9AAAY)

will be dictated by the level of commitment of others and also on the licensing model(s) that is     (1I9AAAZ)

eventually adopted.     (1I9AAAAA)

Peter P. Yim: #7: If you are contributing code, what would be your (top 2 or 3) open license     (1I9AAAAB)

preferences?     (1I9AAAAC)

Bruce Perens: Bruce says GPL, BSD, LGPL together provide all the common sorts of Open Source license     (1I9AAAAD)

and are compatible with each other.     (1I9AAAAE)

Ravi Sharma: @All - since there is no kernel agreed for ontologies or for OOR, unix parallels may not     (1I9AAAAF)

be directly applicable?     (1I9AAAAG)

Cameron Ross: License preferences: in order of preferences for OOR code: #1: EPL, #2: BSD, #3 some     (1I9AAAAH)

other gifting license. Not acceptable from my perspective would be GPL.     (1I9AAAAI)

Ravi Sharma: general open license     (1I9AAAAJ)

Peter P. Yim: @Ravi - not sure what license you are referring to in the above statement.     (1I9AAAAK)

Peter P. Yim: #8: If you are contributing content, what would be your (top 2 or 3) open license     (1I9AAAAL)

preferences?     (1I9AAAAM)

Cameron Ross: Content license preference at this point would be CC-by 3.0, but this isn't all that     (1I9AAAAN)

clear to me at this point.     (1I9AAAAO)

Bruce Perens: BSD, or just declare it to be in the public domain if you don't care about attribution.     (1I9AAAAP)

Pat Cassidy1: For ontology content, I suggest that the freest possible license be used; if not     (1I9AAAAQ)

public domain, then a gift license with at most an attribution requirement. If control of the name     (1I9AAAAR)

of an ontology is desirable, I would suggest that the name be trademarked.     (1I9AAAAS)

Peter P. Yim: #9; If you are planning to run an ontology repository ... Will you federate with the     (1I9AAAAT)

open instance of the OOR? ... What kind of software license do you plan to adopt? ... What kind of     (1I9AAAAU)

content license do you plan to adopt?     (1I9AAAAV)

Cameron Ross: Yes! Absolutely! As long as the OOR interfaces were reasonable to interface with.     (1I9AAAAW)

Current plan is to use EPL 1.0 for software and CC-by 3.0.     (1I9AAAAX)

Peter P. Yim: #10: Should we, as a community, take a position on Software patents? if so, what     (1I9AAAAY)

position should we take?     (1I9AAAAZ)

Ravi Sharma: consensus communique     (1I9AAAAAA)

Bruce Perens: Unfortunately software patenting is potentially a show-stopper for Open Source, so you     (1I9AAAAAB)

need to do something about it. The W3C process is probably good.     (1I9AAAAAC)

Peter P. Yim: #11: Should we, as a community, take a position on Ontology patents? if so, what     (1I9AAAAAD)

position should we take?     (1I9AAAAAE)

Ravi Sharma: Peter your Q lists what i wanted to communicate anyway. Thanks.     (1I9AAAAAF)

Ravi Sharma: Can we attempt a communique style brief as consensus of community in the next 2-3 wks?     (1I9AAAAAG)

Ravi Sharma: Ontologies should not be patentable, but some effort attribution ought to be allowed.     (1I9AAAAAH)

Cameron Ross: I don't think that ontologies should be patentable, but I see the whole patent     (1I9AAAAAI)

situation to be entirely misguided.     (1I9AAAAAJ)

Cameron Ross: I guess we should take a position, but I wouldn't dedicate a lot of resources to it...     (1I9AAAAAK)

its seems like a black hole... I think that our resources would be better spent just doing real     (1I9AAAAAL)

Peter P. Yim: #12: Any suggestion on how we can get open efforts funded ... ?     (1I9AAAAAN)

Ali Hashemi: Re funding: case studies demonstrating real $ savings for companies?     (1I9AAAAAP)

Ali Hashemi: i.e. form a committee or a group via ontolog to demonstrate a business case for open     (1I9AAAAAQ)

efforts in ontologies?     (1I9AAAAAR)

Ali Hashemi: (dunno if this is pie in the sky...)     (1I9AAAAAS)

Ali Hashemi: case can/should also be made to government organizations. Electronic health records,     (1I9AAAAAT)

etc... The case just needs to be documented and made.     (1I9AAAAAU)

Bruce Perens: Someone's going to have to tilt at this windmill some day.     (1I9AAAAAV)

Ravi Sharma: Peter: Will some of the answers in chat find their way on the active pages?     (1I9AAAAAW)

Peter P. Yim: @Ravi - the chat transcript will be captured onto the session page shortly (as usual)     (1I9AAAAAX)

Peter P. Yim: -- session ended 12:27pm PDT --     (1I9AAAAAAC)

-- end of chat session --     (1I9AAAAAAD)

  • Further Question & Remarks - please post them to the [ oor-forum ] listserv     (1I9AAAAAAE)
    • if you are already subscribed, post to <oor-forum [at]>     (1I9AAAAAAE1)
    • (if you are not yet subscribed) you may subscribe yourself to the [ oor-forum ] listserv, by sending a blank email to <oor-forum-join [at]> from your subscribing email address, and then follow the instructions you receive back from the mailing list system.     (1I9AAAAAAE2)
    • more general issues related to Ontology (say, IPR issues relating more to ontology in general, rather than to OOR specifically) are discussed at the [ontolog-forum] mailing list, which all members of the Ontolog community are already subscribed to. If what we do here aligns well with your professional interest, consider joining the community. Membership details can be found here.     (1I9AAAAAAE3)

Audio Recording of this Session     (1J)

  • suggestion: its best that you listen to the session while having the presentation opened in front of you. You'll be prompted to advance slides by the speaker.     (1J5)
  • Take a look, also, at the rich body of knowledge that this community has built together, over the years, by going through the archives of noteworthy past Ontolog events. (References on how to subscribe to our podcast can also be found there.)     (1J6)

For the record ...     (1J7)

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

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

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.