My architecture was based on the OOR use cases. I developed it before I
began studying BioPortal in detail. (01)
On Sat, 18 Sep 2010, Cameron Ross wrote: (02)
> Excellent. Clearly you've spent a lot of time analyzing the BioPortal
> architecture and refactoring the BioPortal web service interface. Is your
> proposed architecture biased by the BioPortal architecture?
> Cameron.
>
> On Sat, Sep 18, 2010 at 5:24 PM, kenb <kenb@xxxxxxxxxxx> wrote:
> Indeed, that is what I am doing, and I am hoping that I can get
> some help with it. In the oor-dev mailing list, I asked for
> volunteers who can contribute to the OOR use cases, architecture
> and component APIs.
>
>
> On Sat, 18 Sep 2010, Cameron Ross wrote:
>
> So, shouldn't we finish the specification before we start
> talking about
> forking BioPortal?
>
> On Sat, Sep 18, 2010 at 4:38 PM, kenb <kenb@xxxxxxxxxxx>
> wrote:
> I always understood that the deliverables included
> both a
> specification
> (architecture and APIs) and a reference
> implementation.
>
> -- Ken
>
> On Sat, 18 Sep 2010, Cameron Ross wrote:
>
> > OK, I see what Peter is trying to clarify...
> >
> > So, is the deliverable for the _OOR Group_ to be a
> specification for
> > an OOR, an implementation of an OOR, or both, or neither?
> >
> > Cameron.
> >
> >
> > Sent from my iPhone
> >
> > On Sep 18, 2010, at 10:52 AM, Adam Pease
> <adampease@xxxxxxxxxxxxx>
> wrote:
> >
> >> Hi Cameron,
> >> I think it's just a minor (to most of us) question of
> phrasing that
> >> Peter was clarifying. The deliverable for the ontolog
> group is just
> a
> >> discussion. The deliverable for the OOR group (as
> distinct from the
> >> larger ontolog group that is hosting the OOR discussion)
> may or may
> not
> >> be an implementation, although personally I agree with
> you that it
> >> should be an implementation, hopefully with a very
> simple and clear
> >> specification.
> >>
> >> Adam
> >>
> >> On Sat, 2010-09-18 at 10:34 -0400, Cameron Ross wrote:
> >>> Hi Peter,
> >>>
> >>> Thanks for the description, but it doesn't clarify for
> me anyway.
> We
> >>> meet, we discuss, we're talking about architecture,
> people are
> >>> starting to develop interfaces, we have the OOR
> sandbox... surely
> >>> we're striving for more than a water cooler discussion!
> >>>
> >>> This collective set of activities, whatever you chose
> to call them,
> >>> should deliver something tangible. Is this to be a
> specification
> for
> >>> an OOR, an implementation of an OOR, or both, or
> neither?
> >>>
> >>> Cameron
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On Sep 18, 2010, at 10:23 AM, Peter Yim
> <peter.yim@xxxxxxxx> wrote:
> >>>
> >>>> Thank you for asking, Cameron. For those who weren't
> already
> aware ...
> >>>>
> >>>> ONTOLOG and OOR are two separate and distinct entities
> (communities.)
> >>>>
> >>>> ONTOLOG is a community of practice (CoP) operating on
> a (donated)
> >>>> virtal collaborative work environment (CWE), which
> also serves as
> the
> >>>> community's dynamic knowledge repository (DKR). ...
> [note that
> Ontolog
> >>>> is just supposed to be a good conversation (think, the
> water
> cooler
> >>>> conversation ...)]
> >>>>
> >>>> OOR is an initiative, a project, or, more
> appropriately, a
> collection
> >>>> of projects.
> >>>>
> >>>> It so happens that the OOR initiative is being
> incubated by
> Ontolog on
> >>>> it's CWE (to the extent that some of the OOR
> transactions and work
> are
> >>>> being done on the Ontolog CWE.)
> >>>>
> >>>> While there are overlaps in these two communities'
> membership,
> there
> >>>> is no direct mandate or relationship between the two.
> >>>>
> >>>> Other communities, initiatives, projects, programs
> similarly
> incubated
> >>>> or 'residing' in the Ontolog CWE include the annual
> OntologySummit
> >>>> series, BSP, IAOA, SIO, etc. (just to show that OOR is
> not alone
> in
> >>>> this regard.)
> >>>>
> >>>> Therefore, Ontolog's deliverable to OOR (if one really
> has to
> frame it
> >>>> that way) is to provide it with a "nice place to
> work," as best it
> >>>> can.
> >>>>
> >>>> Hope this clarifies things.
> >>>>
> >>>>
> >>>> Thanks & regards. =ppy
> >>>>
> >>>> Peter Yim
> >>>> Co-convener, ONTOLOG
> >>>> Co-convener, OOR
> >>>> --
> >>>>
> >>>>
> >>>> On 9/18/10, Cameron Ross <cross@xxxxxxxxxxxx> wrote:
> >>>>> Is the primary deliverable from ONTOLOG's work on OOR
> to be a
> >>>>> specification, an implementation, or both?
> >>>>>
> >>>>> Cameron
> >>>>>
> >>>>> Sent from my iPhone
> >>>>>
> >>>>>
> _________________________________________________________________
> >>>>> Message Archives:
> http://ontolog.cim3.net/forum/oor-forum/
> >>>>> Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
> >>>>> Config/Unsubscribe:
> http://ontolog.cim3.net/mailman/listinfo/oor-forum/
> >>>>> Shared Files: http://ontolog.cim3.net/file/work/OOR/
> >>>>> Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository
> >>>>>
> >>>>
> >>>>
> _________________________________________________________________
> >>>> Message Archives:
> http://ontolog.cim3.net/forum/oor-forum/
> >>>> Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
> >>>> Config/Unsubscribe:
> http://ontolog.cim3.net/mailman/listinfo/oor-forum/
> >>>> Shared Files: http://ontolog.cim3.net/file/work/OOR/
> >>>> Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository
> >>>
> >>>
> _________________________________________________________________
> >>> Message Archives:
> http://ontolog.cim3.net/forum/oor-forum/
> >>> Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
> >>> Config/Unsubscribe:
> http://ontolog.cim3.net/mailman/listinfo/oor-forum/
> >>> Shared Files: http://ontolog.cim3.net/file/work/OOR/
> >>> Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository
> >>
> >>
> >>
> >>
> _________________________________________________________________
> >> Message Archives:
> http://ontolog.cim3.net/forum/oor-forum/
> >> Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
> >> Config/Unsubscribe:
> http://ontolog.cim3.net/mailman/listinfo/oor-forum/
> >> Shared Files: http://ontolog.cim3.net/file/work/OOR/
> >> Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository
> >
> >
> _________________________________________________________________
> > Message Archives:
> http://ontolog.cim3.net/forum/oor-forum/
> > Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
> > Config/Unsubscribe:
> http://ontolog.cim3.net/mailman/listinfo/oor-forum/
> > Shared Files: http://ontolog.cim3.net/file/work/OOR/
> > Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository
> >
>
> _________________________________________________________________
> Message Archives: http://ontolog.cim3.net/forum/oor-forum/
> Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
> Config/Unsubscribe:
> http://ontolog.cim3.net/mailman/listinfo/oor-forum/
> Shared Files: http://ontolog.cim3.net/file/work/OOR/
> Wiki:
> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository
>
>
>
>
> --
> Kojeware Corporation
>
>
>
> _________________________________________________________________
> Message Archives: http://ontolog.cim3.net/forum/oor-forum/
> Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
> Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-forum/
> Shared Files: http://ontolog.cim3.net/file/work/OOR/
> Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository
>
>
>
>
> --
> Kojeware Corporation
>
> (03)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-forum/
Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-forum/
Shared Files: http://ontolog.cim3.net/file/work/OOR/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (01)
|