ppy/chat-transcript_unedited_20110311a.txt



.

OpenOntologyRepository: Architecture & API Workshop-II - Fri 2011_03_11    (2PIR)

Topic: OOR Specification Workshop II - "OOR Architecture & API Specification Development Workshop-II"    (2PIS)

Session Co-chairs: KenBaclawski & ToddSchneider 

session page at: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_03_11

== Proceeedings: ==

.

PeterYim: .

OpenOntologyRepository: Architecture & API Workshop-II - Fri 2011_03_11    (2PIR)

Topic: OOR Specification Workshop II - "OOR Architecture & API Specification Development Workshop-II"    (2PIS)

Session Co-chairs: KenBaclawski & ToddSchneider 

session page at: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_03_11

== Proceeedings: ==

.

anonymous morphed into Tim Darr

Tim Darr: this is tim darr from KBSI joining

PeterYim: Hi Tim ...

Tim Darr: Hello. Sorry I missed last week, but I had a conflict.

PeterYim: @Tim - we did post a recording (and the chat transcript, although not much in there) for last weeks' call

Tim Darr: i downloaded the audio, but have not listened yet

Tim Darr: Which document are we looking at currently?

PeterYim: @Tim - the OORI.java file at: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_03_11#nid2PK8

Tim Darr: Thanks. Since I missed last week, what is the status of the forked BioPortal code?

PeterYim: @Tim - during the session, we will generally refer to that as "purple number 2PK8" ... which is what you can get to if you search on the session page for the string "2PK8"

TerryLongstreth: I'd love to see the document that describes the BIOPortal architecture and shows where our 'facade' intersects

KenBaclawski: The guiding principle we will use is to introduce a facade that exposes the OOR API and uses the BioPortal API internally. This ensures that any improvements to BioPortal can be seamlessly incorporated in the OOR Reference Implementation.

Tim Darr: where do i find that location?

PeterYim: BioPortal architecture - see: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_Architecture/From_BioPortal

Tim Darr: Thanks, but where do we get the actual code? cimcentral??

ToddSchneider: Suggested modification: An OOR guiding principle: we will provide a facade that exposes the OOR API and can be coupled to the BioPortal API. This will allow for improvements to BioPortal to be incorporated in the OOR Reference Implementation.

PeterYim: @Tim - access the semwebcentral code repository via link at: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_03_11#nid2POH

PeterYim: or, more directly http://oor.semwebcentral.org/ ... and in fact, http://semwebcentral.org/projects/oor

MikeDean: @Tim - http://semwebcentral.org/scm/?group_id=152 describes SVN access

MikeDean: @Tim - it's linked from http://semwebcentral.org/projects/oor

YuriyMilov: Sorry, need to go

Tim Darr: Thanks, Mike! You should get a request to join from Scott Fahle at KBSI. We are very interested in contributing. It seems like BioPortal has the default capabilities that we need, plus we can provide feedback and requirements moving forward.

KenBaclawski: The consensus is to have a single searchOntologyMetadata method that has a single parameter, the query, and returns a list of matching ontologies. One is basically specifying a collection of match criteria for the metadata, the match criteria being specified using the OMV (or some extension of it).

Tim Darr: @Ken - that meets our immediate requirements.

TerryLongstreth: Thoughts on admin and workflow, for consideration: Administration : functions with special privileges, rules and workflow
Admin would be tailored by instances, but should include a correlated set of common functions for protections of the content across the federation
Admin is a distinguished type of workflow, as is find, inference, persistence, etc   So Workflow is the enabling meta-language as well as a standard mechanism for scheduling functions in the system.

Tim Darr: @Peter - I agree! KBSI has resources available (as long as it is in line with our contract)

PeterYim: next week is MetaData (MichaelGruninger) ... next Architecture-API workshop - 3/25 same time ... we will focus on workflow at that workshop-III

PeterYim: -- session ended: 6:59am PST --