From OntologPSMW

Jump to: navigation, search
[ ]

Contents

OOR Panel Discussion Session - Fri 19-Feb-2010     (1)

Title: Coordinating our Open Ontology Repository Software Development     (1A)

Session Chair: MikeDean (Raytheon BBN)     (1B)

Panelists:     (1C)

Archives     (1H)

  • Shared-screen support (VNC session), if applicable, will be started 5 minutes before the call at: http://vnc2.cim3.net:5800/     (1I5)
    • view-only password: "ontolog"     (1I5A)
    • 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.     (1I5B)
    • 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.     (1I5C)
  • Discussions and Q & A:     (1I6)
    • (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"     (1I6A)
    • You can type in your questions or comments through the browser based chat session by:     (1I6B)
      • 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.     (1I6C1)
    • (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.)     (1I6D)
    • 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_20100219@soaphub.org ... Handy for mobile devices!     (1I6E)
  • Please note that this session will be recorded, and the entire proceedings including the audio archives are expected to be made available as open content to our community membership and the public at-large under our prevailing open IPR policy.     (1I10)

Attendees     (1K)

  • Comments:     (1K5)
    • Ed Dodds This process will serve as a case study on open innovation best practices in coordinating "big databases in the sky" solutions which are becoming increasingly relevant (given the availability and affordability of cloud computing) in the nonprofit sector, as well as global businesses, state and federal government services--so NO PRESSURE ;-)     (1K5A)

Agenda     (1L)

1. Introduction (MikeDean) - [ slides ]     (1L1)

2. Recent OOR development     (1L3)

3. Upcoming BioPortal plans (NatashaNoy, et al)     (1L7)

4. Software management (discussion)     (1L8)

5. Q & A and Open discussion (All) -- please refer to process above     (1L15)

6. Conclusion / Follow-up (MikeDean)     (1L16)

Proceedings     (1M)

Please refer to the archives above     (1M1)

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

see raw transcript here.     (1M2A)

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

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

Welcome to the OOR Panel Discussion Session - Fri 19-Feb-2010     (1M2E)

Title: Coordinating our Open Ontology Repository Software Development     (1M2F)

Session Chair: Mike Dean (Raytheon BBN)     (1M2G)

Panelists:     (1M2H)

Please refer to details on the session page     (1M2M)

anonymous1 morphed into Misha Dorf     (1M2P)

anonymous1 morphed into Jim Disbrow     (1M2Q)

Peter P. Yim: another plea (while we are waiting) ... please hep with our Ontology Summit 2010 Surveys -     (1M2R)

Peter P. Yim: take a look at the solicitation too, at:     (1M2T)

anonymous morphed into Paul Alexander     (1M2V)

anonymous1 morphed into Line Pouchard     (1M2W)

anonymous morphed into Jack Park     (1M2X)

Line Pouchard: we're not funded yet, but am working on http://dataone.org     (1M2Y)

Jim Disbrow: @Line: consider joining us - go to http://ET.gov, on the left is a "Search" button,     (1M2Z)

click it and the next screen will show a list of ET.gov components - one of which is     (1M2AA)

"Energy-Water Nexus vis-a-vis the Climate"; click on the referenced XML file and it will lead you     (1M2AB)

into what the project is doing     (1M2AC)

anonymous morphed into Bart Gajderowicz     (1M2AD)

anonymous1 morphed into Doug Foxvog     (1M2AE)

anonymous2 morphed into Lin Zhang (Forest)     (1M2AF)

Doug Foxvog: Could anonymous3 click "settings" and put in their name?     (1M2AJ)

anonymous morphed into Matt Hettinger     (1M2AK)

David Eddy: SCM (software conf mgmt) is EXTREMELY important around repository... a fatal missing     (1M2AL)

component over past 40 years     (1M2AM)

Lin Zhang (Forest): To Session Chair: I'm Lin Zhang (Forest) from China. And I'm on.     (1M2AN)

Peter P. Yim: @JimChatigny - I noticed on your slide 4, you were federating from the OOR-sandbox at     (1M2AO)

<oor-01f.cim3.net> ... please note that the OOR-sandbox is now at http://oor-01.cim3.net     (1M2AP)

(the <oor-01f> name was for testing only ... for everyone's information)     (1M2AQ)

Ravi Sharma: @MikeDean and Jim Chatigny: Is there an architecture diagram to look at that shows     (1M2AR)

pattern or Ontology Beans, etc? or did I miss it?     (1M2AS)

Paul Alexander: You can view a complete description of NCBO REST services (which at this point match     (1M2AT)

Peter P. Yim: @Ravi - guess you are aware of this:     (1M2AV)

work with Todd and consider adding to it     (1M2AX)

Ravi Sharma: Peter: great link and lot of architecture information in UML that Todd Schneider     (1M2AY)

developed that I had missed so far. Thanks     (1M2AZ)

anonymous2 morphed into Frank Olken     (1M2AAA)

Terry Longstreth: Have you trained anyone to administer the system in your absence?     (1M2AAB)

Jim Rhyne: Is there an introduction and rationale for this particular OOR architecture? Not obvious     (1M2AAC)

to me why Spring would be a good basis.     (1M2AAD)

Paul Alexander: @JimRhyne: Misha may be able to speak to the decision to use Spring. It's in OOR     (1M2AAE)

because it is used in NCBO BioPortal (which OOR is an instance of right now)     (1M2AAF)

Jim Rhyne: @MishaDorf - can you post a link to information on NCBO BioPortal architecture and     (1M2AAG)

implementation?     (1M2AAH)

Peter P. Yim: @JimRhyne - see resources listed under:     (1M2AAI)

Paul Alexander: Here's a BioPortal/OOR architecture overview:     (1M2AAK)

Jim Rhyne: @PaulAlexander - exactly what I was looking for, thanks.     (1M2AAM)

anonymous morphed into Dan Cerys     (1M2AAN)

Natasha Noy: @JimChatigny Is there a link where we can try the federated server?     (1M2AAO)

Natasha Noy: Also @JimChatigny: I think I missed this: do you download only metadata, or the     (1M2AAP)

ontologies themselves as well?     (1M2AAQ)

Natasha Noy: And Q3 @JimChatigny: Is there a way to limit what to federate from a particular     (1M2AAR)

repository (e.g., only OWL ontologies)?     (1M2AAS)

Ravi Sharma: @JimChatigny: Are you restricted to RDF? especially due to REST requiring a resource?     (1M2AAT)

Ravi Sharma: @MichaelGruninger: What about intermodule integration? Does CL fully prescribe a unique     (1M2AAU)

way of putting them together?     (1M2AAV)

Ravi Sharma: @MichaelGruninger and Ali Hashemi: Hope you are aware of current progress being made by     (1M2AAW)

Mike Linehan and others in our efforts at OMG on SBVR Data-Time?     (1M2AAX)

Ravi Sharma: @MichaelGruninger and Ali Hashemi: These have time and duration vocabularies that would     (1M2AAY)

be helpful in developing ontologies of temporal aspects?     (1M2AAZ)

Lin Zhang (Forest): @MichaelGruninger: Did the current use case include the natural language     (1M2AAAA)

translation of ontologies? If yes, maybe we can use the term "converter" rather than     (1M2AAAB)

translator for the syntax conversion. What do you think of this? Thanks.     (1M2AAAC)

Pat Cassidy: @MikeGruninger: Do you think that JohnSowa's idea of using OpenCyc as the base for     (1M2AAAD)

relating multiple ontologies could be implemented in COLORE? Any ideas on what such     (1M2AAAE)

an exercise would need in terms of work.resources?     (1M2AAAF)

Michael Grüninger: @PatCassidy: We have found that we do not need to use any ontology as an a priori     (1M2AAAG)

base for relating multiple ontologies. Once the axioms of the ontologies have     (1M2AAAH)

been explicitly stated, their relationships are much easier to identify. The problem is that nobody     (1M2AAAI)

bothers to specify their axioms when discussing the relationships between     (1M2AAAJ)

ontologies. One motivation for COLORE was to get people to actually submit axioms.     (1M2AAAK)

Pat Cassidy: @MikeGruninger: Yes, but axioms can only be related to each other if the namespaces are     (1M2AAAL)

identical, or if some translation is provided. The issue I am concerned with in     (1M2AAAM)

relating ontologies is to specify the bridging axioms that convert the assertions in one domain     (1M2AAAN)

ontology into the equivalent assertion in the other ontologies. So if the 25,000 -     (1M2AAAO)

60,000 OpenCYc hierarchy is loaded and axioms are added, how do you imagine this will interact with     (1M2AAAP)

the other modules in COLORE?     (1M2AAAQ)

Doug Foxvog: @MikeGruninger: without a base for relating ontologies, axioms expressed in one ontology     (1M2AAAR)

could not be interpreted in another. Relationships between them could not be     (1M2AAAS)

determined without mappings expressed.     (1M2AAAT)

Ali Hashemi: @DougFoxvog - can you elaborate what you mean by "base" ?     (1M2AAAU)

Doug Foxvog: I used MikeGruninger's term..     (1M2AAAV)

Michael Grüninger: @DougFoxvog: If one ontology is interpretable by another, we don't need a "base     (1M2AAAW)

ontology" to show this. You simply specify a mapping from the lexicon of one to the lexicon of     (1M2AAAX)

the other and then show that theorems are preserved.     (1M2AAAY)

Doug Foxvog: there should be some way to specify a mapping betweens terms. A star mapping is much     (1M2AAAZ)

simpler than creating an N-N mapping; but the center     (1M2AAAAA)

Michael Grüninger: BTW, the term "base ontology" is PatCassidy's and John Sowa's.     (1M2AAAAB)

Doug Foxvog: of the radial star might be more than one ontology     (1M2AAAAC)

Ali Hashemi: @DougFoxvog - one need not create N-N mappings. If you map A to B and perhaps     (1M2AAAAD)

map B to C, then you have an implicit mapping, from A to C through B. The star structure emerges.     (1M2AAAAE)

David Eddy: I'd be interesting in talking with anyone who's interested in examining the lessons     (1M2AAAAF)

learned from 40 years of repository efforts... 95% of which have gone to the bit     (1M2AAAAG)

bucket in the sky. WHY did they fail & what can we avoid repeating?     (1M2AAAAH)

Peter P. Yim: @KenBaclawski- (slide#6) what is KEEPER? is it s software tool? if so, is it an opensource     (1M2AAAAI)

Ken Baclawski: @Peter: KEEPER was the name of the project in my course. It is a web service     (1M2AAAAK)

(supporting WSDL, SOAP and REST) and will be open source.     (1M2AAAAL)

Jim Rhyne: @PeterYim phone battery died, back on now.     (1M2AAAAM)

Peter P. Yim: @JimRhyne - glad you're back     (1M2AAAAN)

Ravi Sharma: @KenBaclawski: I believe you are simply executing the OOR gatekeeping function without     (1M2AAAAO)

touching the content or relationships or internal structure of ontology, ie. using BPEL for that purpose?     (1M2AAAAP)

Terry Longstreth: @KenBaclawski - you mention 11179. Are you familiar with XMDR? Has it provided     (1M2AAAAQ)

anything useful?     (1M2AAAAR)

Ken Baclawski: @Terry: Yes, we did look at XMDR and we hope to use some of it in KEEPER.     (1M2AAAAS)

Lin Zhang (Forest): @TerryLongstreth: XMDR is a good resource. In some way, OOR is like XMDR.     (1M2AAAAT)

Peter P. Yim: we actually have XMDR folks on the OOR team (notably Bruce Bargmeyer ... although he has     (1M2AAAAU)

been less active lately)     (1M2AAAAV)

Ken Baclawski: @Peter: I have been in contact with the XMDR people, but not much has occurred in this     (1M2AAAAW)

Lin Zhang (Forest): @MichaelGruninger: Do the current use cases include the natural language     (1M2AAAAY)

translation of ontolgies? Thanks.     (1M2AAAAZ)

Ali Hashemi: @Lin, as far as I know, the current use cases do not include NL translation of     (1M2AAAAAA)

Lin Zhang (Forest): Years ago, I tranlated some wiki pages into Chinese and post there.     (1M2AAAAAC)

Lin Zhang (Forest): @AliHashemi: Thanks. But the feature is desirabe.     (1M2AAAAAD)

Ken Baclawski: @Ali, the use cases are still being developed. If you are interested in this, please     (1M2AAAAAE)

come to the Use Cases meeting.     (1M2AAAAAF)

Lin Zhang (Forest): I uploaded some ontologies with Chinese concept names onto the BioPortal, but it     (1M2AAAAAG)

couldn't display the Chinese character correctly.     (1M2AAAAAH)

Paul Alexander: @LinZhang: We recently discovered a bug that was preventing these characters from     (1M2AAAAAI)

displaying properly. BioPortal now displays them properly, but the OOR Sandbox may be running code     (1M2AAAAAJ)

from prior to the bug fix.     (1M2AAAAAK)

Lin Zhang (Forest): @PaulAlexander: Oh, that's great! I'll check that later after the t-con. Thanks.     (1M2AAAAAL)

Lin Zhang (Forest): Amino Acid with Simplified Chinese annotations     (1M2AAAAAM)

(View for Amino Acid) Version 1.3:     (1M2AAAAAN)

Lin Zhang (Forest): @PaulAlexander: Thanks. It works.     (1M2AAAAAP)

Amino Acid with Simplified Chinese annotations (View for Amino Acid) Version 1.3:     (1M2AAAAAQ)

Biomedical Resource Ontology with Simplified Chinese annotations:     (1M2AAAAAS)

Ali Hashemi: @DougFoxvog, slide 4 in MichaelGruninger's presentation provides a high level view of     (1M2AAAAAU)

some way to specify a mapping between terms     (1M2AAAAAV)

Doug Foxvog: The star model is what John F. Sowa was suggesting for the FO (Foundation Ontology). That     (1M2AAAAAW)

was also one of original ideas behind Cyc. A center of the star might have     (1M2AAAAAX)

multiple inter-related ontologies (SUMO, Cyc, etc.). Sowa is considering an FO w/ multiple modules     (1M2AAAAAY)

(for different topics).     (1M2AAAAAZ)

Ali Hashemi: @DougFoxvog, the problem with top-down star models are exactly that, they are top down.     (1M2AAAAAAA)

Another approach is to have them emerge from the mappings that exist between     (1M2AAAAAAB)

theories. For example, mathematical concepts (i.e. geometries, orderings) provide the backbone for     (1M2AAAAAAC)

many many ontologies. They serve in many was a central star. Of course, one     (1M2AAAAAAD)

doesn't know unless axioms are inputted, and mappings are generated.     (1M2AAAAAAE)

Doug Foxvog: On slide 4, pi specifies a mapping function from T0 to T1. This does not explain whether     (1M2AAAAAAF)

Pi0-1 is calculated via a star, N-N, chain of mappings, or any other specific mapping.     (1M2AAAAAAG)

Pat Cassidy: @AliHashemi: If you map all of A to all of B, there are likely to still be terms in one     (1M2AAAAAAH)

that are not in the other and vice versa, so there will be terms not mapped.     (1M2AAAAAAI)

Then if you map C to B, some of the terms in A (that have not been mapped to B because they don't     (1M2AAAAAAJ)

exist in B) will not be mapped from B to C for the same reason. The transitivity     (1M2AAAAAAK)

will only be complete by this mechanism if all ontologies have the same set of terms. One can use     (1M2AAAAAAL)

this case-by-case mechanism, but if you keep a "foundation" ontology that contains     (1M2AAAAAAM)

all of the terms that have been mapped in common between any two ontologies, then the foundation     (1M2AAAAAAN)

ontology will be able to serve as a reliable and complete intermediate for     (1M2AAAAAAO)

translation among all of the ontologies in the repository. That is the principle I have suggested     (1M2AAAAAAP)

for the FO; it is not disjoint from your approach, it just *adds* an FO to serve     (1M2AAAAAAQ)

as the most complete inventory of terms needed for translation.     (1M2AAAAAAR)

Michael Grüninger: @DougFoxvog: The definition of interpretation (on my slide 4) does not assume any     (1M2AAAAAAS)

algorithm for generating the mapping. Ali's thesis and the current paper discuss     (1M2AAAAAAT)

ways of generating new mappings from the relationships between ontologies that are specified in the     (1M2AAAAAAU)

Ali Hashemi: @PatCassidy, a partial mapping will be a partial mapping, regardless of whether it is     (1M2AAAAAAW)

into a foundation ontology or not. You can create a new module which enables a full     (1M2AAAAAAX)

mapping (i.e. extend the FO), but then we are moving away from an FO. Note you could also do this     (1M2AAAAAAY)

for A to B in the above example. ... The goal you have outlined is laudable, I've     (1M2AAAAAAZ)

already voiced some concerns. You are right however that attempting to identify ontological     (1M2AAAAAAAA)

primitives is complementary to much work being done and could help in the generation of mappings.     (1M2AAAAAAAB)

Bart Gajderowicz: @Pat, @Ali: Pat as you mentioned getting every single term in A to match every term     (1M2AAAAAAAC)

in B is very unlikely, simply because A and B were created separately. Could     (1M2AAAAAAAD)

Ontology Granulation assist in this, where it identifies key low-level terms (properties) which may     (1M2AAAAAAAE)

be sufficient to *differentiate* higher level terms (concepts). Then these     (1M2AAAAAAAF)

partial mappings will have been chosen based on *best* terms from the limited number of available     (1M2AAAAAAAG)

terms. *best* terms may introduce a level of stability in the partial mappings.     (1M2AAAAAAAH)

Ali Hashemi: Bart, that might be a useful approach in identifying what Pat calls primitives. I would     (1M2AAAAAAAI)

note that before one can identify primitives, one needs to _at least_ specify     (1M2AAAAAAAJ)

mappings between some of the dominant upper ontologies, and i would suggest, mathematical theories.     (1M2AAAAAAAK)

Pat Cassidy: @BartGajderowicz: The Foundation Ontology as I envision it would be an ontology that is     (1M2AAAAAAAL)

mapped (by complete translations) to every other ontology in the repository. So     (1M2AAAAAAAM)

if terms in different ontologies have some conceptual overlap, but are not identical, the part that     (1M2AAAAAAAN)

overlaps will be identifiable via the FO. This FO could be created by performing     (1M2AAAAAAAO)

the kind of mappings that Ali suggests, but also performing a mapping to the FO. When there are     (1M2AAAAAAAP)

terms needed that are not in the FO, they can be added. But the additions to the FO     (1M2AAAAAAAQ)

are kept to a minimum by only adding the most basic terms (primitives) that are required to     (1M2AAAAAAAR)

logically specify the terms in all of the mapped ontologies. This mechanism would     (1M2AAAAAAAS)

guarantee an automatic translation of assertions in any ontology into assertions in any other mapped     (1M2AAAAAAAT)

Doug Foxvog: @MichaelGruninger: Re your page 10, without a base for relating ontologies, axioms     (1M2AAAAAAAV)

expressed in one ontology could not be interpreted in another. Relationships between     (1M2AAAAAAAW)

them could not be determined without mappings expressed. For computers, a ROT-13 of the names of one     (1M2AAAAAAAX)

ontology would make no difference.     (1M2AAAAAAAY)

Doug Foxvog: OOPS. Ignore my last comment. I meant:     (1M2AAAAAAAZ)

Doug Foxvog: @MichaelGruninger: Re your page 10, By having ontology terms for modules as instances,     (1M2AAAAAAAAA)

common logic could be used to express simple relationships among ontologies. The     (1M2AAAAAAAAB)

issue would be whether Common Logic can associate such terms with the modules themselves.     (1M2AAAAAAAAC)

Doug Foxvog: @PatCassidy, do you envision a functional description of terms in the FO for mapping to     (1M2AAAAAAAAD)

more specific terms. E.g.,     (1M2AAAAAAAAE)

(NthInSeriesFn (AnatomicalPartTypeFn (LeftFn Hand-AnatomicalPart) FingerSeries) 3)     (1M2AAAAAAAAF)

for a SNOMED term for the third finger of the left hand?     (1M2AAAAAAAAG)

Pat Cassidy: @DougFoxvog: The FO only needs to have the basic elements that can be combined by FOL to     (1M2AAAAAAAAH)

produce the terms in the domain ontologies. So Nth in series might be a     (1M2AAAAAAAAI)

primitive, but applied to the hand it could be a domain-specific combination.     (1M2AAAAAAAAJ)

David Eddy: can someone point to a ontology glossary... I have no idea what a "theory" or "axiom" is     (1M2AAAAAAAAK)

Lin Zhang (Forest): @PeterYim and Mike Dean: I'll be out about 20 min later because my skype card is     (1M2AAAAAAAAM)

Paul Alexander: Is anyone familiar with/using Git SCM? It could work very well for this type of     (1M2AAAAAAAAO)

distributed development.     (1M2AAAAAAAAP)

Paul Alexander: Or Mercurial or some other distributed SCM system     (1M2AAAAAAAAQ)

Ravi Sharma: @KenBaclawski: My Question is for you from above relating to ISO 11179 that defines     (1M2AAAAAAAAR)

metadata Registry and data element definitions hence the question, does OOR     (1M2AAAAAAAAS)

automatically assume that things and relationships are "data Elements"? Also BPEL Q from Above     (1M2AAAAAAAAT)

repeated here for you.I believe you are simply executing the OOR gatekeeping function     (1M2AAAAAAAAU)

without touching the content or relationships or internal structure of ontology, ie. using BPEL for     (1M2AAAAAAAAV)

Ken Baclawski: @RaviSharma: ISO 11179 can specify content and relationships. However, the granularity     (1M2AAAAAAAAX)

of administered item for OOR remains to be determined. This is related to     (1M2AAAAAAAAY)

modularity. The administered items are the units being managed with a BPEL process.     (1M2AAAAAAAAZ)

Line Pouchard: @KenBaclawski: Is your NIH project planning to develop a new "environement" ontology?     (1M2AAAAAAAAAA)

Do you have a list of existing ones?     (1M2AAAAAAAAAB)

Ken Baclawski: @LinePouchard: We will be using existing ontologies when possible. Send me email.     (1M2AAAAAAAAAC)

Line Pouchard: Ken, Peter and all: I have to go. Ken: I will be in touch by email. Thank you.     (1M2AAAAAAAAAD)

Peter P. Yim: on code repository - Mike Dean, on consultation with Natasha Noy and everyone at this call:     (1M2AAAAAAAAAE)

decision reached (confirmed between the OOR-team and NCBO-team) - OOR will be     (1M2AAAAAAAAAF)

using the repository at semwebcentral for the OOR-branch (of the BioPortal extensions)     (1M2AAAAAAAAAG)

Jim Rhyne: Unfortunately have to leave the call.     (1M2AAAAAAAAAJ)

Doug Foxvog: Signing off at 6:30 p.m. (UTC), i need to head home from work.     (1M2AAAAAAAAAK)

Peter P. Yim: thanks for joining us Doug     (1M2AAAAAAAAAL)

Ravi Sharma: Thanks Mike Peter and Speakers.     (1M2AAAAAAAAAM)

Paul Alexander: Thanks everyone, please let me know if you have questions as you move the OOR     (1M2AAAAAAAAAO)

codebase to the new SVN repository.     (1M2AAAAAAAAAP)

Peter P. Yim: - session ended 2010.02.19 - 10:31am PST -     (1M2AAAAAAAAAQ)

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

  • due to time limitation, agenda items we were not able to cover will be deferred to the regular team meetings and/or the next two community panel discussion sessions     (1M2AAAAAAAAAS)

Audio Recording of this Session     (1N)

Resources     (1O)


For the record ...     (1O10)

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


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