ppy/chat-transcript_edited_20110920b.txt


Welcome to the

= OpenOntologyRepository: Architecture & API Workshop-VII - Tue 2011_09_20 =

Topic: "OOR Architecture & API Specification Development Workshop-VII"

Session Co-chairs: KenBaclawski & ToddSchneider   

Session page: http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_09_20

.
== Proceedings: ==
.

ToddSchneider: Ken, I was able to login.

KenBaclawski: Tejas set up a VMWare on a machine in my office at NU. I can give access to anyone who needs it. The main machine is lisf.ccs.neu.edu, and the domains we can use are ontology.ccs.neu.edu and kiwi.ccs.neu.edu.

PeterYim: please use this page to capture customization details - http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR_SandBox_Customization

KenBaclawski: The static IP address of ontology.ccs.neu.edu is 129.10.112.163.  The one for kiwi.ccs.neu.edu is 129.10.112.167.

ToddSchneider: where are we with the discussion ... ref. http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_04_22#nid2ST2

  = The interface for searching ontology metadata will consist of a single method:    (2SSS)
    * The method will be called find.    (2SST)
    * The method will have a single parameter consisting of a SPARQL query.    (2SSU)
    * The return value of the method will be a SPARQL result set.    (2SSV)
    * Metadata will be represented using a named RDF graph.    (2SSW)
    * The metadata RDF graph will use the following name: http://metadata.oor.net    (2SSX)
    * Metadata will be based on an extension of OMV.    (2SSY)
          o The OMV extension may include a notion of domain specification or topics, represented as text.    (2SSZ)
    * Metadata will be federated, so it is a single named RDF graph, no matter how many OOR instances there are.

ToddSchneider: also ref. http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2011_06_17#nid2V8P
          o Quality and Gatekeeping. We distinguish between gatekeeping and quality control. Gatekeeping criteria are a set of minimal requirements that any ontology within the OOR has to meet. The latter are intended to enable the users of the OOR to find quickly ontologies that fit their needs; the criteria are not supposed to ensure the quality of the ontologies.    (2VB
          o Gatekeeping impacts metadata    (2VB9)
          o Gatekeeping will need to vet the metadata to ensure entrance criteria are met.    (2VBA)
          o Syntax checking is the responsibility of the language module.    (2VBB)
          o Each OOR instance must declare the representation languages    (2VBD)
          o Each OOR instance must declare the representation language module it spports.    (2VBE)
          o Will OOR Metadata be represented in OWL?    (2VBF)
          o Every OOR shall support RDF    (2VBG)
          o Correction: Every OOR shall support RDFS    (2VBI)
          o OMV is written in OWL    (2VBK) - From Chapter 5 of the OMV Report 2.4.1: As aforementioned, OMV is formalized as an OWL ontology.    (2VBO)
          o Gatekeeping criteria will include an attribute to indicate whether the ontology exists or the metadata represents an advertisement.    (2VBR)
          o The location of the actual ontology is the responsibility of Administration.    (2VBT)
          o Metadata needs to include an attribute for the 'availability' of the ontology    (2VBW)
          o 'Location' of the ontology must be provided.    (2VBX)
          o Representation language of the ontology is a required attribute.    (2VBY)
          o Michael will provide a preliminary list of required metadata attributes.    (2VBZ)
          o Submission process will be asynchronous    (2VC0)
          o Minimal language dependency submission is syntax validation    (2VC1)
          o Consistency checking, to some extent, will be required for submission    (2VC2)
          o Need an attribute to represent that it is consistent, which then will require another field to identify the reasoner used to do the consistency checking    (2VC3)
          o Ken has already developed the gatekeeper module which should provide enough to specify it for OOR    (2VC4)
          o Ken's gatekeeper module already has a mechanism to configure the registration workflow for a community    (2VC5)

ToddSchneider: Gatekeeper - notification(), subscription(), register()?

ToddSchneider: subscription is for particular ontology and particular user

ToddSchneider: subscription - sends notices about events related to ontology

TerryLongstreth: Create ontology == prepare system for new ontology?

ToddSchneider: registrar - creates the entry in the OOR; to do so the required metadata needs to be created

PeterYim: -- session ended: 9:41am PDT --