Difference (from prior revision)

Changed: 26c26

* '''[http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_11_19#nid2JU4 Transcript of the online chat session]''' during the panel discussion ''( ... raw transcript already online; edited transcript coming!)'' {nid 2JSL}
* '''[http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_11_19#nid2JU4 Transcript of the online chat session]''' during the panel discussion {nid 2JSL}

Changed: 193c193

(for better clarity, the version below is a [ re-organized and lightly edited chat-transcript].)
(for better clarity, the version below is a [http://ontolog.cim3.net/file/work/OpenOntologyRepository/2010-11-19_OOR-Architecture-API-2/OOR_Architecture-n-API-2_chat-transcript_edited_20101119b.txt re-organized and lightly edited chat-transcript].)

Changed: 201c201,458

'' (chat transcript ... coming!)'' {nid 2JU8}
{{{
PeterYim: Welcome to the OpenOntologyRepository: OOR Team Conference Call - Fri 2010-11-19 {nid 2JU8}
}}}

{{{
Session Title: "(Post-BioPortal fork) OOR Architecture and API - Take-II" {nid 2JXP}
}}}

{{{
Session Co-chairs: KenBaclawski (NEU) & MichaelGruninger (U of Toronto) {nid 2JXQ}
}}}

{{{
Panelists: {nid 2JXR}
}}}

{{{
* KenBaclawski (NEU) + ToddSchneider (Raytheon) * AldoGangemi + AlessandroAdamou (STLab, Rome)
* JouniTuominen + KimViljanen (Aalto U, Finland) * MathieuDaquin (NeOn, Open University, UK) *
EricChan (ICOM) {nid 2JXS}
}}}

{{{
please refer to details on the session page at:
http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_11_19 {nid 2JXT}
}}}

{{{
. {nid 2JXU}
}}}

{{{
anonymous morphed into JouniTuominen {nid 2JXV}
}}}

{{{
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? {nid 2JXW}
}}}

{{{
PeterYim: yes ... just tell me when to advance slides ... and call out the slide number as well {nid 2JXX}
}}}

{{{
JouniTuominen: Peter: ok, thanks {nid 2JXY}
}}}

{{{
anonymous morphed into MichaelGruninger {nid 2JXZ}
}}}

{{{
anonymous1 morphed into MyCoyne {nid 2JY0}
}}}

{{{
KimViljanen: hello {nid 2JY1}
}}}

{{{
MyCoyne: Where would I be able to obtain the presentation? {nid 2JY2}
}}}

{{{
MyCoyne: Does anyone has a problem with audio: the speaker voice is very faint {nid 2JY3}
}}}

{{{
PeterYim: I can hear them ok ... Ken seems to be fading in and out a bit, though {nid 2JY4}
}}}

{{{
KimViljanen: http://www.onki.fi {nid 2JY5}
}}}

{{{
KimViljanen: LOOS (workshop in ESWC2009):
http://www.slideshare.net/digikim/ores2010-linked-openontologyservices20100528slideshare {nid 2JY6}
}}}

{{{
MyCoyne: 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? {nid 2JY7}
}}}

{{{
anonymous morphed into BartGajderowicz {nid 2JY8}
}}}

{{{
PeterYim: very well thought through presentation, Jouni and Kim ... thank you! {nid 2JY9}
}}}

{{{
KimViljanen: Peter: thanks for the positive feedback above {nid 2JYA}
}}}

{{{
ToddSchneider: ONKI seems to provide more capabilities than envisioned by the OOR {nid 2JYB}
}}}

{{{
KimViljanen: Todd: e.g.? {nid 2JYC}
}}}

{{{
ToddSchneider: Annotation {nid 2JYD}
}}}

{{{
KimViljanen: but the main question we wanted to present is: is the OOR application needed or the
APIs to connect existing ontology repositories? {nid 2JYE}
}}}

{{{
KimViljanen: ok, so we are now planning the OOR Architecture (global) _and_ the Architechture of the
reference implementation {nid 2JYF}
}}}

{{{
KenBaclawski: Yes, Kim, that is the idea. {nid 2JYG}
}}}

{{{
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? {nid 2JYH}
}}}

{{{
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 {nid 2JYI}
}}}

{{{
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 {nid 2JYJ}
}}}

{{{
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? {nid 2JYK}
}}}

{{{
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 {nid 2JYL}
}}}

{{{
KimViljanen: (which mean WSDL can be used describing the APIs) {nid 2JYM}
}}}

{{{
MyCoyne: Is ICOM a licensed product from Oracle? {nid 2JYN}
}}}

{{{
PeterYim: ICOM is an OASIS Technical Committee (TC) ... it is being developed as an open standard {nid 2JYO}
}}}

{{{
MyCoyne: Thanks, Peter. This is very helpful. {nid 2JYP}
}}}

{{{
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? {nid 2JYQ}
}}}

{{{
KimViljanen: @Immanuel: well... typically we have made so simple APIs that just writing them in a
(free form) human readable document has been enough {nid 2JYR}
}}}

{{{
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) {nid 2JYS}
}}}

{{{
PeterYim: @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 should
leverage would depend on other pragmatic factors (e.g. who is on the team, experience of the members
with the particular SDO process, expedience, which approach can best help us reach our ultimate
goals ... etc.) {nid 2JYT}
}}}

{{{
anonymous morphed into MattHettinger {nid 2JYU}
}}}

{{{
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. {nid 2JYV}
}}}

{{{
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 {nid 2JYW}
}}}

{{{
ToddSchneider: Yes. I'd suggest placing the artifacts on the OOR Architecture Wikipage {nid 2JYX}
}}}

{{{
ToddSchneider: If possible, UML models would be optimal. {nid 2JYY}
}}}

{{{
KimViljanen: [on Ken's remark that BioPortal (on which the OOR sandbox is running now) features
about 126 methods] (ONKI LOOS API has ca. 10-15 methods) {nid 2JYZ}
}}}

{{{
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. {nid 2JZ0}
}}}

{{{
KenBaclawski: Those who were not at the Take I architecture meeting should review that wikipage. {nid 2JZ1}
}}}

{{{
PeterYim: that Architecture & API (take-1) meeting would be at:
http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_10_15 {nid 2JZ2}
}}}

{{{
KenBaclawski: Everyone should create their own subpage of the architecture wikipage. {nid 2JZ3}
}}}

{{{
KimViljanen: thanks for an inspiring meeting! {nid 2JZ4}
}}}

{{{
YuriyMilov: Thanks for the great presentations {nid 2JZ5}
}}}

{{{
PeterYim: nice session ... thank you! {nid 2JZ6}
}}}

{{{
PeterYim: -- session ended: 8:06am PST -- {nid 2JZ7}
}}}