From OntologPSMW

Jump to: navigation, search
[ ]

Contents

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

  • Topic: "OOR-IPR session 1: An Exposition on Relevant IPR Regimes"     (1A)
  • Chair: Mr. PeterYim (Co-convener, Ontolog & OOR; Secretary, IAOA) - [ slides ]     (1B)

  • Shared-screen support (VNC session) will be started 5 minutes before the call at: http://vnc2.cim3.net:5800/     (1F5)
    • view-only password: "ontolog"     (1F5A)
    • 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.     (1F5B)
    • 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.     (1F5C)
  • Discussions and Q & A:     (1F6)
    • (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"     (1F6A)
    • You can type in your questions or comments through the browser based chat session by:     (1F6B)
      • 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.     (1F6C1)
    • (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.)     (1F6D)
    • 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) ontolog_20100909@soaphub.org ... Handy for mobile devices!     (1F6E)
  • 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.     (1F10)

Attendees     (1H)

Resources     (1H3)

Agenda & Proceedings     (1I)

Panel Discussion Session: "OOR-IPR session 1: An Exposition on the State of Relevant IPR Regimes"     (1I1)

Abstracts     (1J)

  • Session Topic: "OOR-IPR session 1: An Exposition on the State of Relevant IPR Regimes"     (1J1)
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.     (1J2)
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).     (1J3)
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.     (1J4)
In the opening session, we have invited some of the top experts in open IPR to give us an exposition on the IPR landscape and the state of relevant IPR regimes.     (1J5)
Please refer also to the background and thoughts collected during the process of organizing this mini-series, at: OpenOntologyRepository_IPR & OpenOntologyRepository_IPR/Discussion     (1J6)

Panel Members Briefings     (1J7)

Abstract: ... this talk will provide an overview on the IPR landscape as it relates to OOR, open standards and the OASIS IPR policies that may be used as a reference for this community.     (1J7B1)
Abstract: ... this talk will be devoted to open content, scientific data and an exposition of the Creative Commons licenses.     (1J7D1)
Abstract: ... this presentation will delve into "openness," open technology, open source software licenses, and what might really matter here, for the OOR initiative.     (1J7F1)

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

see raw transcript here.     (1J8A)

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

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

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

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

Panel Discussion (session-1) - Thu 9-Sep-2010     (1J8H)

  • Topic: "OOR-IPR session 1: An Exposition on Relevant IPR Regimes"     (1J8I)

and Information Technology R&D) - "IP and IT"     (1J8L)

o Mr. JamesBryceClark, JD (General Counsel, OASIS) - "Some Notes on OOR IPR"     (1J8N)

o Mr. John Wilbanks (VP of Science, Creative Commons) - "licensing and ontologies: research from creative commons"     (1J8O)

o Mr. Bruce Perens (original author of the "Open Source Definition") - "OOR Open Source Software Licensing"     (1J8P)

Please refer to dial-in and other details (include slides download links) on the session page     (1J8Q)

JamieClark: Pinging, just to establish that I'm in the chat room. I also have visual into the VNC     (1J8T)

desktop. Personally, as a speaker, I plan to ask Peter to advance my slides, and not to bother with     (1J8U)

manipulating the remote session at my end. Cheers all     (1J8V)

Peter P. Yim: Hi JamieClark ... I actually do get to advance the slides for everyone!     (1J8W)

anonymous morphed into Steve Ray     (1J8X)

anonymous1 morphed into John Wilbanks     (1J8Y)

anonymous2 morphed into Bruce Perens     (1J8Z)

anonymous1 morphed into Joel Bender     (1J8AB)

anonymous1 morphed into Cameron Ross     (1J8AC)

JamieClark: Jamie's here (on voice)     (1J8AD)

anonymous2 morphed into Yuriy Milov     (1J8AE)

anonymous morphed into Bobbin Teegarden     (1J8AF)

anonymous1 morphed into Mike Bennett     (1J8AG)

JamieClark: Thanks, George: excellent remarks and we appreciate the US government's support for     (1J8AI)

developing this concept.     (1J8AJ)

Ravi Sharma: Dr. George Strawn - Many thought provoking and positive areas covering S&T, Knowledge     (1J8AK)

and Information and ontology / OOR carving its space in the open / global IPR space. These valuabe     (1J8AL)

inputs will nurture the purpose of this series and spearhead the focus of deliberations. many     (1J8AM)

anonymous morphed into Doug Foxvog     (1J8AO)

Peter P. Yim: Mr. JamesBryceClark, JD speaking (started 11:02am PDT) ...     (1J8AP)

JamieClark: JBC slide 1-2: Topic introduction.     (1J8AQ)

JamieClark: JBC slide 3: Definition of "open" largely is a defined community's policy chat about its     (1J8AR)

requirements. Consider: even a variety among standards projects: OASIS, IETF, W3C, ISO, ITU ...     (1J8AS)

maybe microformats.org? ...     (1J8AT)

JamieClark: JBC slide 4: Some say that some restrictions are *virtuous*.     (1J8AU)

Bruce Perens: You could do that with trademark rather than copyright and it would still work.     (1J8AV)

Mike Bennett: OASIS "Keeps Copyright" in their standards - doesn't (C) exist automatically? Presume     (1J8AW)

means "Asserts Copyright"?     (1J8AX)

Bruce Perens: Mike, this means that OASIS doesn't abandon its copyright and dedicate the document to     (1J8AY)

the public domain.     (1J8AZ)

JamieClark: JBC slide 5: License form matters too. Key issue for real user: "safe to ignore"     (1J8AAB)

JamieClark: JBC slide 6: If you can't get at material, its theoretical legal availability is sort of     (1J8AAC)

irrelevant. ... Reliance on open data sources = sunk costs.     (1J8AAD)

JamieClark: JBC slide 7: As for legal uncertainty, let's plan for the worst. Note, a LATER session     (1J8AAE)

in this OOR-OPR series will discuss what best polices to use.     (1J8AAF)

JamieClark: JBC slide 8: How one stable host organization (OASIS) handles the policy issues.     (1J8AAG)

JamieClark: JBC slide 9: Look at the *workflow* of rights and contributions as well. It's not a     (1J8AAH)

static snapshot.     (1J8AAI)

JamieClark: JBC slide 10: Using a federated system introduces some additional issues.     (1J8AAJ)

Terry Longstreth: JBC Slide 9: I'm unsure of how fine a distinction can be drawn between 'read' and     (1J8AAK)

use' permission. Is there a restriction on what I, ('public') can do with materials others     (1J8AAL)

submitted with open access?     (1J8AAM)

JamieClark: JBC slide 11: Using a rating / opinions system introduces some additional issues.     (1J8AAN)

JamieClark: JBC slide 12: Thanks. Call anytime with questions.     (1J8AAO)

Peter P. Yim: Mr. John Wilbanks speaking (started 11:27am PDT) ...     (1J8AAQ)

Ravi Sharma: @JamieClark - lifecycle related - is it a workable proposition that even if some     (1J8AAS)

organization makes some comercial value add on what is largely open source that it automatically     (1J8AAT)

turns to open status in a shorter period say 3-5 years for all such proprietary add-ons to become     (1J8AAU)

Bruce Perens: Ravi Sharma, is this question regarding standards IP submissions or something else?     (1J8AAW)

Ravi Sharma: Bruce - I was thinking of OOR primarily, but really it would also apply to     (1J8AAX)

Knowledge-bases. Standards are facilitators for connecting, validating and communication of the     (1J8AAY)

knowledge pieces and bases.     (1J8AAZ)

Mike Bennett: @Ravi that does raise an interesting question, whether there are the same IPR     (1J8AAAA)

considerations for class-level ontologies versus instances.     (1J8AAAB)

Bruce Perens: Ravi Sharma - For reasons that have just been discussed I am far from sure you can make     (1J8AAAC)

any requirements stick upon the creators of commercial derivative works.     (1J8AAAD)

JamieClark: Agree with Bruce. Don't rely heavily on terms that probably don't stick; and we know     (1J8AAAE)

from experience that some don't.     (1J8AAAF)

JamieClark: Reading the Dental Association quotes. Assertions of creativity in classification sound     (1J8AAAG)

a LOT like the 'Feist' and 'West v. Mead Data' assertions that phone directory listings and caselaw     (1J8AAAH)

page numbers were creative ... Saying this not as a copyright lawyer in 2010, but because John is     (1J8AAAI)

giving me some flashbacks from 1987. (As a frisky young judicial law clerk, I was involved in the     (1J8AAAJ)

West vs. Mead case.)     (1J8AAAK)

Ravi Sharma: Mike - if class-level is open, others can use it as pattern for creating instances but     (1J8AAAL)

such creator might change status to non-open but it would become open based on original open-use     (1J8AAAM)

license declaration.     (1J8AAAN)

Bruce Perens: There is substantial doubt that a reference to an open ontology caused the referencing     (1J8AAAO)

ontology to be a derivative work of the open one.     (1J8AAAP)

John Wilbanks: Bruce - agreed. But copying ontologies is an essential part of ontology practice, and     (1J8AAAQ)

making changes to the local copies is as well...     (1J8AAAR)

Mike Bennett: @Ravi agreed. That would be a significant use case for having an ontology in the first     (1J8AAAS)

place, hence the importance of distinguishing T-Box v A-Box in thinking about these IPR issues I     (1J8AAAT)

Cameron Ross: John - For clarity, is the CC BY license amiable to using an ontology within a     (1J8AAAV)

commercial application?     (1J8AAAW)

John Wilbanks: Cameron - yes, CC BY is completely compatible with commercial use     (1J8AAAX)

Peter P. Yim: Mr. Bruce Perens speaking (started 11:47) ...     (1J8AAAZ)

Patrick Cassidy: @John Wilbanks: concerning the question of whether an ontology is software: at least     (1J8AAAAA)

the ontologies that are produced in a format that has associated reasoners (such as OWL or FOL     (1J8AAAAB)

format) should be considered as a form of software, since they are in fact instructions about how to     (1J8AAAAC)

perform inferences from data. In fact, I think of logic-based ontologies as little more than     (1J8AAAAD)

software in a specific declarative format, easier to understand and easier to modify than     (1J8AAAAE)

traditional code.     (1J8AAAAF)

John Wilbanks: Patrick - this is a fundamental question.     (1J8AAAAG)

Ravi Sharma: Bruce and JamieClark - can we not declare on open source material that any use based on     (1J8AAAAH)

this material is only non-open for x years?     (1J8AAAAI)

John Wilbanks: my instinct is that the courts will be utterly confused by the ontology question     (1J8AAAAJ)

JamieClark: John (a W3C alumni) mentions the W3C patent policy as a possible prototype. For the most     (1J8AAAAK)

part, the rules and workflow of the W3C, OASIS and IETF policies on patent handling are pretty     (1J8AAAAL)

similar. So I suspect the models would all lead to a similar design. didn't quote W3C's instance in     (1J8AAAAM)

this case, as has a deeply-negotiated rule (it's section 7) that royalties are permitted, but must     (1J8AAAAN)

be studied and made the sole personal decision of an individual. (Sort of like the IANA under Jon     (1J8AAAAO)

Postel in 1996, versus ICANN today.) Here's the link to the W3C policy:     (1J8AAAAP)

John Wilbanks: To JamieClark's point, yes - the technical standards world has worked out patent     (1J8AAAAR)

policies reasonably well, and OASIS and IETF are both excellent models as well     (1J8AAAAS)

John Wilbanks: I used the W3C one because I know it better, no other reason!     (1J8AAAAT)

Ravi Sharma: Bruce - was that Katz case? IT related?     (1J8AAAAU)

Bruce Perens: Jacobsen v. Katzer. Look in Wikipedia     (1J8AAAAV)

Mike Bennett: @Patrick but many use an ontology as a technology-neutral, formal business definition     (1J8AAAAW)

of subject matter. It so happens you can then do those things with it if it's in OWL or similar.     (1J8AAAAX)

JamieClark: @JohnWilbanks, I think our tribe figured out, a while ago, that the delta between the     (1J8AAAAY)

established practices is quite small, except in marketing brochures :D     (1J8AAAAZ)

John Wilbanks: JamieClark, heh. True. I can send you some lovely corporate marketing documents for     (1J8AAAAAA)

closed ontologies.     (1J8AAAAAB)

Cameron Ross: John: Would CC BY be considered "Gift" licensing?     (1J8AAAAAC)

John Wilbanks: Cameron, I believe so - given that Bruce classifies BSD in there, and that CC BY is an     (1J8AAAAAD)

analog to BSD.     (1J8AAAAAE)

Patrick Cassidy: @Mike - if an ontology is fairly simple and doesn't include restrictions or other     (1J8AAAAAF)

structures that enable inference more complicated than simple taxonomic subsumption, it does in fact     (1J8AAAAAG)

contain instructions for computation that can be automatically executed. This is the function of     (1J8AAAAAH)

software, regardless of whether there are lots of documentation that is also useful independent of     (1J8AAAAAI)

the instructions.     (1J8AAAAAJ)

Mike Bennett: @Patrick yes but I don't think you can necessarily determine intention from inspection.     (1J8AAAAAK)

Patrick Cassidy: @MIke-oops! if its simple, it *isn't* necessarily a program, but if is more     (1J8AAAAAL)

complicated, it is hard to distinguish from software.     (1J8AAAAAM)

Peter P. Yim: @Bruce - slide#8 ... can you give a quick rundown on how people would circumvent GPL     (1J8AAAAAN)

Bruce Perens: It's a long talk. Can we do it another time?     (1J8AAAAAP)

JamieClark: @Ravi - The idea of a sunset rule on restrictions is a darn interesting one. If     (1J8AAAAAQ)

compromise is needed. But there's a strong opendata movement these days; as a negotiating matter in     (1J8AAAAAR)

the service of openness, as a personal opinion, I'd rather start from "open", as the default, and     (1J8AAAAAS)

save ideas like "open soon" as middle-ground options only when needed. TimBL in the UK, OSTP in the     (1J8AAAAAT)

US, and others are creating some great social pressure to open up data right now. (If you think     (1J8AAAAAU)

about userfriendly simple rights, on an icon-based, no-lawyer-need basis like CC, how would we     (1J8AAAAAV)

happily represent "not open now, but it will be later"? Feh.)     (1J8AAAAAW)

John Wilbanks: @Ravi, there is some sunset stuff in the US National Institute of Health's open access     (1J8AAAAAX)

repository policy, but I tend to agree with @JamieClark - let's go for open first. Default rules of     (1J8AAAAAY)

open, with opt outs clearly defined and accessible, are a good starting point.     (1J8AAAAAZ)

Peter P. Yim: @JohnWilbanks - is there a (cc) license (for content) that is similar/analogous to LPGL     (1J8AAAAAAA)

(for software)?     (1J8AAAAAAB)

John Wilbanks: @Peter, we only provide a single share-alike license     (1J8AAAAAAC)

John Wilbanks: although we do provide layperson readable and metadata versions of GPL, LGPL, and BSD     (1J8AAAAAAD)

John Wilbanks: @BrucePerens, the core right is the right to make non-commercial copies     (1J8AAAAAAG)

Ravi Sharma: presenters: Ontologies are not patentable - is this defendable position as connected     (1J8AAAAAAH)

ontologies might be open or common relationships are open and thus not patentable? Similar argument     (1J8AAAAAAI)

for proprietary ontologies?     (1J8AAAAAAJ)

John Wilbanks: (all CC licenses carry this right, not just the right to read)     (1J8AAAAAAK)

John Wilbanks: thanks @BrucePerens for noting my comment     (1J8AAAAAAL)

JamieClark: Bruce asserts: part of proper host/repository/community management may be to *permit*     (1J8AAAAAAM)

forking, for virtuous quality & contribution reasons.     (1J8AAAAAAN)

JamieClark: @Ravi, the simple statement of problem is that "Eventually we will win this baseless     (1J8AAAAAAO)

lawsuit" is not equal to "This will be easy because we have the right to do it."     (1J8AAAAAAP)

JamieClark: <cough>SCO<koff koff>     (1J8AAAAAAQ)

John Wilbanks: apologies all, i have to jump off the call for a meeting     (1J8AAAAAAR)

John Wilbanks: it has been an honor and pleasure, and thanks to @PeterYim     (1J8AAAAAAS)

JamieClark: Thanks John! great stuff     (1J8AAAAAAT)

John Wilbanks: please buzz me at wilbanks@creativecommons.org if you want to talk more, and i'll be     (1J8AAAAAAU)

on the next call as well     (1J8AAAAAAV)

John Wilbanks: @JamieClark - let's talk more!     (1J8AAAAAAW)

John Wilbanks: (also, honored to be on a panel with @BrucePerens and George!)     (1J8AAAAAAX)

Peter P. Yim: Bruce's slide#15 - @Wilbanks and @Perens - John, while your recommended against a     (1J8AAAAAAZ)

reciprocal license, does Brunce's case of the MySQL dual licensing arrangement worth considering for     (1J8AAAAAAAA)

(some portions of) OOR? ... the reason I am asking (and in line with GeorgeStrawn's "Open access is     (1J8AAAAAAAB)

good, as is profit seeking") is that we need to make innovation sustainable!     (1J8AAAAAAAC)

Cameron Ross: @Peter It would be unlikely that I, for one, would release contributions under a dual     (1J8AAAAAAAD)

license regime.     (1J8AAAAAAAE)

JamieClark: BTW, here's an instance of FOSS folks (Apache) doing its legal diligence to make sure     (1J8AAAAAAAF)

that the OASIS patent & copyright rules would permit OASIS standards (OpenDocument) to be used under     (1J8AAAAAAAG)

is an instance of the kind of "you better check with your lawyer" review that John and Bruce     (1J8AAAAAAAI)

mentioned. If only all lawyers wrote as clearly as Eben Moglen ...     (1J8AAAAAAAJ)

Peter P. Yim: Q&A and general discussion starts now ... (12:20pm PDT) ...     (1J8AAAAAAAL)

George Strawn: "Are ontologies copyrightable or patentable now?" - panelists please discuss     (1J8AAAAAAAM)

Bruce / Jamie: @George - the jury is still out, and these are questions that probably won't have a     (1J8AAAAAAAN)

clear answer for a while yet     (1J8AAAAAAAO)

Ravi Sharma: All- please see same question earlier where I feel these should not be easy or easily     (1J8AAAAAAAP)

possible to patent. There is however a compelling counterargument for lifesaving pharmaceuticals     (1J8AAAAAAAQ)

that may use bioinformatics?     (1J8AAAAAAAR)

Cameron Ross: Would releasing an ontology under a Open Source or CC license, enforcible or not,     (1J8AAAAAAAS)

constitute prior art for future patent claims?     (1J8AAAAAAAT)

Bruce Perens: @CameronRoss, any publication can constitute prior art.     (1J8AAAAAAAU)

Doug Foxvog: @CameronRoss: A public release of material should certainly (imho as a non-lawyer)     (1J8AAAAAAAV)

constitute prior art.     (1J8AAAAAAAW)

Peter P. Yim: @anyone ... are we past the point of no return on the US Patent Reform to go from     (1J8AAAAAAAX)

first-to-invent to a "first-to-file" regime?     (1J8AAAAAAAY)

Bruce Perens: Peter, no but our main enemy on this entire argument is pharma.     (1J8AAAAAAAZ)

Ravi Sharma: All- I am reminded of "standing on Shoulders of giants" and desire for knowledge in open     (1J8AAAAAAAAA)

regime. Can the community support of this type of assertion help keep ontologies open sourced?     (1J8AAAAAAAAB)

Cameron Ross: So, could we not employ an Open Source or CC licensing strategy to protect the OOR     (1J8AAAAAAAAC)

against future patents. Of course there's still the issue of existing patents.     (1J8AAAAAAAAD)

Doug Foxvog: One ontology can be expressed in multiple semantic languages. Copyright couldn't cover     (1J8AAAAAAAAE)

the same expression in both OWL and CycL, say.     (1J8AAAAAAAAF)

Cameron Ross: @DougFoxvog - So can one circumvent copyright using automated translation?     (1J8AAAAAAAAG)

Doug Foxvog: @Cameron: good question. The information can not be copyrighted, although a specific     (1J8AAAAAAAAH)

expression of it in a specific language may be.     (1J8AAAAAAAAI)

Mike Bennett: @CameronRoss copyright depends on being able to demonstrate something was copied rather     (1J8AAAAAAAAJ)

than prior art (as patents are) so transformation if detectable would fall foul of copyright.     (1J8AAAAAAAAK)

Cameron Ross: @MikeBennett - That's what I thought. Thanks.     (1J8AAAAAAAAL)

Terry Longstreth: So, we need an implementation neutral form of expression for the intellectual     (1J8AAAAAAAAM)

content of an ontology?     (1J8AAAAAAAAN)

Bruce Perens: USC 17.1.102.b says:     (1J8AAAAAAAAO)

In no case does copyright protection for an original work of authorship extend to any idea,     (1J8AAAAAAAAP)

procedure, process, system, method of operation, concept, principle, or discovery, regardless of the     (1J8AAAAAAAAQ)

form in which it is described, explained, illustrated, or embodied in such work.     (1J8AAAAAAAAR)

In ADA v. Delta Dental (at http://lw.bna.com/lw/19971014/964140.htm) the appeals court judge found     (1J8AAAAAAAAS)

that there is sufficient creative expression in a taxonomy to make it copyrightable. A quote from     (1J8AAAAAAAAT)

The ADA couldn't stop dentists from using the ADA Code in their forms and records, or stop Delta     (1J8AAAAAAAAV)

from distributing forms that invited dentists to use the ADA's Code. However, the Court found that     (1J8AAAAAAAAW)

it was a violation of the ADA's copyright for Delta to distribute a copy of the code itself.     (1J8AAAAAAAAX)

The degree to which this applies to ontology, and indeed the value of the case as precedent, is     (1J8AAAAAAAAY)

concludes that ontologies that refer to other ontologies are not derivative works of those other     (1J8AAAAAAAAAA)

ontologies under copyright law. Ontologies might be the subject of patent rather than copyright to     (1J8AAAAAAAAAB)

the extent that they can be restricted effectively, and patenting one presents its own problems.     (1J8AAAAAAAAAC)

JamieClark: Thanks for an excellent session, it's an honor to work with Peter, George, Bruce, John &     (1J8AAAAAAAAAD)

Mike Bennett: Thanks all! Most helpful session     (1J8AAAAAAAAAG)

Peter P. Yim: thank you all ... great session!     (1J8AAAAAAAAAH)

Mike Dean: Thanks for a great session     (1J8AAAAAAAAAI)

Peter P. Yim: -- session ended: 12:47pm PDT --     (1J8AAAAAAAAAJ)

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

  • Further Question & Remarks - please post them to the [ oor-forum ] listserv     (1J8AAAAAAAAAL)
    • if you are already subscribed, post to <oor-forum [at] ontolog.cim3.net>     (1J8AAAAAAAAAL1)
    • (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] ontolog.cim3.net> from your subscribing email address, and then follow the instructions you receive back from the mailing list system.     (1J8AAAAAAAAAL2)
    • 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.     (1J8AAAAAAAAAL3)

Audio Recording of this Session     (1K)

  • 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.     (1K5)
  • 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.)     (1K6)

For the record ...     (1K7)

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


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