ppy/OOR_Architecture-n-API-2_chat-transcript_unedited_20101119a.txt // anonymous morphed into JouniTuominen PeterYim1: . Welcome to the OpenOntologyRepository: OOR Team Conference Call - Fri 2010-11-19 (2JLK) Session Title: "(Post-BioPortal fork) OOR Architecture and API - Take-II" (2JS Session Co-chairs: KenBaclawski (NEU) & MichaelGruninger (U of Toronto) (2JS9) Panelists: (2JSA) * KenBaclawski (NEU) + ToddSchneider (Raytheon) (2JSB) * AldoGangemi + AlessandroAdamou (STLab, Rome) (2JSC) * JouniTuominen + KimViljanen (Aalto U, Finland) (2JSD) * MathieuDaquin (NeOn, Open University, UK) (2JSE) * EricChan (ICOM) (2JSF) please refer to details on the session page at: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_11_19 . JouniTuominen: Peter: are you controlling the presentation slides in the shared vnc and the presenter tells everyone (including you) to advance on slides, or how does it work? PeterYim1: yes ... just tell me when to advance slides ... and call out the slide number as well JouniTuominen: Peter: ok, thanks anonymous morphed into MichaelGruninger anonymous1 morphed into My Coyne KimViljanen: hello KimViljanen: PeterYim: If possible, use a PDF client for presenting our ONKI/SeCo slideset (not sure if it works ok with OpenOffice) KimViljanen: s/client/app/ My Coyne: Where would I be able to obtain the presentation? KimViljanen: Peter, try to press ALT+TAB KimViljanen: a few times KimViljanen: (ah sorry, thought you lost the slideshow) My Coyne: Does anyone has a problem with audio: the speaker voice is very faint PeterYim1: I can hear them ok ... Ken seems to be fading in and out a bit, though PeterYim1: @Kim - I will show your slides with the Acrobat Reader KimViljanen: Peter: try to press F11 KimViljanen: (or select from view => fullscreen) KimViljanen: http://www.onki.fi KimViljanen: LOOS (workshop in ESWC2009): http://www.slideshare.net/digikim/ores2010-linked-openontologyservices20100528slideshare My Coyne: Questions for LOOS: (1) does LOOS use any underline grid or enterprise service bus for its registration? (2) Is there any API allows for merging of ontologies? (3) is LOOS available for dowloading trials? anonymous morphed into BartGajderowicz ToddSchneider: ONKI seems to provide more capabilities than envisioned by the OOR ImmanuelNormann lowered your hand KimViljanen: Todd: e.g.? PeterYim1: very well thought through presentation, Jouni and Kim ... thank you! ToddSchneider: Annotation KimViljanen: but the main question we wanted to present is: is the OOR application needed or the APIs to connect existing ontology repositories? KimViljanen: ok, so we are now planning the OOR Architecture (global) _and_ the Architechture of the reference implementation KenBaclawski: Yes, Kim, that is the idea. ImmanuelNormann: @ONKIs: I like the openess in your proposal w.r.t. technical solutions like REST vs. SOAP, different programming languages, etc. But I get the impression that you are committed to OWL-ontologies only. How open are you w.r.t. to different ontology languages? KimViljanen: Immanuel: our idea in LOOS was to support "simple" ontologies in the spirit of SKOS. that is, we think there are common features shared among different ontology languages such as "concepts have labels" KimViljanen: Immanuel: and for example if the user is searching for "fish", the user can then continue using the specific ontology repository for ontology specific functionalities, which may be ontology language dependent, require inference etc ImmanuelNormann: as said before I like the openess w.r.t to technical means to implement an OOR. But at some point we need to specify some service APIs - and finally we have to commit to some format to define service APIs. One option would be WSDL. What is your opinion? KimViljanen: I would support many: e.g. in ONKI we provide both a REST, Web Service and JavaScript API --- the last two automatically created from the same java classes KimViljanen: (which mean WSDL can be used describing the APIs) My Coyne: Is ICOM a licensed product from Oracle? PeterYim1: ICOM is an OASIS Technical Committee (TC) ... it is being developed as an open standard ImmanuelNormann: Kim: REST, SOAP, Java, JavaScript, ..., are rather specific language specific solutions. I think it wouldn't make sense to specify e.g. one API in two or more languages. I was rather thinking about programming language independent spec like e.g. IDL is used at W3C for specifying the DOM model, or WSDL for web services or WADL for the REST world. So is WSDL your favourite? KimViljanen: Immanuel: well... typically we have made so simple APIs that just writing them in a (free form) human readable document has been enough My Coyne: Thanks, Peter. This is very helpful. KimViljanen: Peter: thanks for the positive feedback above KimViljanen: Immanuel: btw, we forgot to say in our presentation that we were discussing whether OOR could initiate / produce a W3C recommendation of this OOR API issue, as a member contribution or something (not fully familiar with the W3C procedures on this) anonymous morphed into MattHettinger MikeBennett: Standardization of metadata about ontologies - agreed, very important. There are a number of common problems currently implemented in different ways by different ontologies. We could start by cataloguing these. Provenance is one such. KimViljanen: could the first step for aligning the ontologies be that each of us provides a document on their APIs (I suppose everybody have a somekind of a document existing), to get an overview ToddSchneider: Yes. I'd suggest placing the artifacts on the OOR Architecture Wikipage ToddSchneider: If possible, UML models would be optimal. PeterYim1: @Kim - International standardization is definitely a medium to long term goal ... whether it is W3C or OASIS or ISO, as the SDO (standard development organization) infrastructure we would leverage would depend on other pragmatic factors (e.g. who is on the team, experience of the players, ... etc.) KimViljanen: (ONKI LOOS API has ca. 10-15 methods) KenBaclawski: Here is the suggestion for followup action items: 1. Post your artifacts on the OOR Architecture wikipage, 2. Review the artifacts on the wikipage, 3. Schedule a new meeting. KenBaclawski: Those who were not at the Take I architecture meeting should review that wikipage. KimViljanen: thanks for an inspiring meeting! PeterYim1: that Architecture & API (take-1) meeting would be at: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_10_15 YuriyMilov: Thanks for the great presentations KenBaclawski: Everyone should create their own subpage of the architecture wikipage. PeterYim1: nice session ... thank you! PeterYim1: -- session ended: 8:06am PST -- Sent transcript to: peter.yim@cim3.com //