Ken, (01)
Unfortunately, I think the answer will be that necessarily
the OOR and its code base will diverge from BioPortal.
However, when that occurs will depend on BioPortal and the
rapidity with which the OOR development progresses. (02)
I think there sufficient evidence, of which you've just
provided some, to indicate that in order to support
arbitrary representation languages and become platform
independent, substantial changes in the BioPortal code
need to take place. (03)
Todd (04)
P.S. I'm sending this directly to you because Ontolog keeps bouncing my
messages and
I haven't taken the time to fix the problem. (05)
From:
kenb <kenb@xxxxxxxxxxx>
To:
OpenOntologyRepository-development <oor-dev@xxxxxxxxxxxxxxxx>
Date:
09/17/2010 05:53 PM
Subject:
[oor-dev] Request for comments: OOR source code fork strategy
Sent by:
oor-dev-bounces@xxxxxxxxxxxxxxxx (06)
At the recent meeting "Getting OOR Development Going - Take-IV"
held on Friday 17 September 2010 [1], an issue was raised
regarding what it means to fork the OOR code base from the
BioPortal code base. I am asking for comments and discussion
about this issue. (07)
While BioPortal is a very well developed system that serves its
community extremely well, the BioPortal requirements and
community differ from the OOR requirements and communities. The
differences appear to be significant enough that the OOR
architecture will need to diverge from the BioPortal
architecture. (08)
Accordingly, the issue is whether the OOR code base should remain
consistent with the BioPortal code base or the OOR code base
should diverge so that it would no longer remain consistent with
the BioPortal code base. (09)
As this is a serious issue for the OOR initiative, there should
be a community discussion with the aim of reaching a
consensus. Clearly there are advantages and disadvantages of each
choice. (010)
I have already performed some refactoring of the BioPortal core
services to extract the REST/WADL and SOAP/WSDL APIs. This
refactoring did not make any changes to the functionality
supported by the core services, so it remains consistent with the
BioPortal code base. The WSDL and Java SEI are available at [2].
I have also introduced an initial proposal for the OOR
architecture which is available in several formats at the same
URL [2]. (011)
If the choice is to diverge, then there must be volunteers who
can contribute to the development of the OOR use cases,
architecture and component APIs. At the recent meeting [1], the
consensus was to shift from informal discussion of requirements
and goals to concrete use case scenarios [3][4], architecture [2],
and APIs [2]. (012)
[1] http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_09_17
[2] http://www.ccs.neu.edu/home/kenb/oor
[3] http://www.ccs.neu.edu/home/kenb/ontologies/index.html
[4] http://www.ccs.neu.edu/home/kenb/ontologies/oor-usecase.xml (013)
-- Ken Baclawski (014)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-dev/
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-dev/
Shared Files: http://ontolog.cim3.net/file/work/OOR/dev/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (015)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-dev/
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-dev/
Shared Files: http://ontolog.cim3.net/file/work/OOR/dev/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (016)
|