On 10/04/2010 4:20 PM, kenb wrote:
> On Sat, 10 Apr 2010, Ron Wheeler wrote:
>
>
>> On 09/04/2010 2:52 PM, kenb wrote:
>>
>>> On Tue, 6 Apr 2010, Cameron Ross wrote:
>>>
>>>
>>>
>>>> Thanks Todd.
>>>>
>>>> The use cases thus far describe Create, Retrieve, Update and Delete
>>>> (CRUD) functionality that is typical of a repository. I'm looking for
>>>> use cases that correspond to the eventual end uses of onologies
>>>> residing within the repository. For example, the trigger for the
>>>> "Find Ontology" use case is "Need for an ontology". What are the use
>>>> cases that motivate the need for an ontology. Although such use cases
>>>> may not be required for the system level implementation of the
>>>> repository, I believe they are essential to develop an understanding
>>>> of the types of problems that an ontology repository will help to solve.
>>>>
>>>> I guess I'm struggling to understand the value of ontology
>>>> repositories beyond their ability to facilitate the development and
>>>> sharing of ontologies. If there isn't any value beyond this, then
>>>> what is the need for an "online" repository. Wouldn't a system that
>>>> allows for the sharing and collaborative development of static
>>>> ontology artifacs (e.g. files) suffice? SourceForge comes to mind.
>>>>
>>>>
>>> The OOR use cases consider workflows/processes such as reviewing, mapping,
>>> composing, etc. The use cases also distinguish the roles (actors) that
>>> are involved in these processes. IMHO, these go significantly beyond CRUD
>>> functionality.
>>>
>>>
>>>
>>>> Perhaps this a naive view, or it has been discussed previously. If
>>>> so, some links would be much appreciated.
>>>>
>>>>
>>> See the OOR use case descriptions at
>>> http://ontolog.cim3.net/file/work/OOR/OOR-Use-Cases/oor-usecase.xml and
>>>
>>>
>> Horribly bureaucratic process. No way this will be able to get any
>> following among application developers.
>>
> The workflows and policies are entirely at the discretion of the
> particular community. So they can be as bureaucratic or unbureaucratic as
> the community desires.
>
>
>> The only criteria for submitting an ontology to a central repository
>> should be some claim on the namespace.
>>
> The OOR is federated. So there is no central repository.
>
I hope that the SIO will produce a structure similar to Maven so that
local and central and federated repositories can be built the way Nexus
is used to manage and distribute software artifacts.
>
>> Our company owns "com.artifact-software" and I should be able to submit
>> any ontology that I want as long as I supply the minimal metadata to
>> permit the OOR to index it.
>>
> Yes, but presumably somebody has to check that the metadata is complete
> and accurate.
>
>
That is what the software does for complete. Accuracy will be judged by
the community.
>> If people like the license that I give and can merge the ontology with
>> the rest of their set, then they will use it.
>>
> Better still, if an organization recommends your ontology, then it will be
> used by even more people.
>
>
>> Adding a bunch of gatekeepers is only going to make the marketplace go
>> elsewhere.
>>
> There seem to be no end of debates about whether publications should be
> carefully reviewed (such as journal articles) or not (such as blogs). The
> OOR does not require either one. Each community can decide for itself.
>
>
> -- Ken
>
>
>>> the main OOR use cases page at
>>> http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_UseCases
>>>
>>> -- Ken
>>>
>>>
>>>
>>>> Cameron.
>>>>
>>>>
>>>> Kojeware Corporation
>>>>
>>>> On Apr 6, 2010, at 12:07 PM, Todd J Schneider<todd.schneider@xxxxxxxxxxxx
>>>>
>>>>
>>>>> wrote:
>>>>>
>>>>>
>>>>
>>>>> Ron, Cameron,
>>>>>
>>>>> The OOR team does have high-level use cases addressing different
>>>>> roles of OOR users. Among them are Developer and [general] User.
>>>>>
>>>>> See
>>>>> http://ontolog.cim3.net/cgi-bin/wiki.pl?
>>>>> OpenOntologyRepository_UseCases
>>>>>
>>>>> Feel free to extend or add to the existing use cases.
>>>>>
>>>>> Todd
>>>>>
>>>>>
>>>>>
>>>>> From:
>>>>> Ron Wheeler<rwheeler@xxxxxxxxxxxxxxxxxxxxx>
>>>>> To:
>>>>> "[sio-dev] discussion"<sio-dev@xxxxxxxxxxxxxxxx>
>>>>> Date:
>>>>> 04/06/2010 10:54 AM
>>>>> Subject:
>>>>> Re: [sio-dev] Fwd: [ontolog-forum] Sharing and Integrating
>>>>> Ontologies
>>>>> Sent by:
>>>>> sio-dev-bounces@xxxxxxxxxxxxxxxx
>>>>>
>>>>>
>>>>>
>>>>> Does anyone have a written use case for what an ontologist would
>>>>> want us
>>>>> to produce?
>>>>> What are the problems he/she should be trying to solve when they
>>>>> contemplate selecting one of our artifacts?
>>>>> How will our artifacts interface with the rest of the solutions set?
>>>>>
>>>>> Are we in a position to write the introductory chapter of the user
>>>>> documentation?
>>>>>
>>>>> Do we have a place on the wiki where these ideas can be developed?
>>>>>
>>>>>
>>>>> Ron
>>>>>
>>>>>
>>>>> Rick Murphy wrote:
>>>>>
>>>>>
>>>>>>> On Thu, Apr 1, 2010 at 7:32 AM, John F. Sowa<sowa@xxxxxxxxxxx
>>>>>>> <mailto:sowa@xxxxxxxxxxx>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>>> John Bateman and his group at Bremen put together a variety of free
>>>>>>>> and open source tools and integrated them with their methodology.
>>>>>>>> One of the most important is HeTS (Heterogeneous Tool System),
>>>>>>>> which can translate from one logic to another while preserving
>>>>>>>> the semantics:
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>> I spent most of last Winter investigating HETs, CASL, Haskell and
>>>>>> Isabelle. At this point I have a modest capacity to engage in
>>>>>> modeling
>>>>>> and coding with this tool suite.
>>>>>>
>>>>>> I look forward to the discussion !
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Rick
>>>>>>
>>>>>>
>>>>>> _________________________________________________________________
>>>>>> Msg Archives: http://ontolog.cim3.net/forum/sio-dev/
>>>>>> Join Community:
>>>>>>
>>>>>>
>>>>> http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
>>>>>
>>>>>
>>>>>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/sio-dev/
>>>>>> Unsubscribe: mailto:sio-dev-leave@xxxxxxxxxxxxxxxx
>>>>>> Community Shared Files: http://ontolog.cim3.net/file/work/SIO/
>>>>>> Community Wiki:
>>>>>>
>>>>>>
>>>>> http://ontolog.cim3.net/cgi-bin/wiki.pl?SharingIntegratingOntologies
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _________________________________________________________________
>>>>> Msg Archives: http://ontolog.cim3.net/forum/sio-dev/
>>>>> Join Community: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
>>>>>
>>>>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/sio-dev/
>>>>> Unsubscribe: mailto:sio-dev-leave@xxxxxxxxxxxxxxxx
>>>>> Community Shared Files: http://ontolog.cim3.net/file/work/SIO/
>>>>> Community Wiki:
>>>>> http://ontolog.cim3.net/cgi-bin/wiki.pl?SharingIntegratingOntologies
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _________________________________________________________________
>>>>> Msg Archives: http://ontolog.cim3.net/forum/sio-dev/
>>>>> Join Community: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
>>>>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/sio-dev/
>>>>> Unsubscribe: mailto:sio-dev-leave@xxxxxxxxxxxxxxxx
>>>>> Community Shared Files: http://ontolog.cim3.net/file/work/SIO/
>>>>> Community Wiki:
>http://ontolog.cim3.net/cgi-bin/wiki.pl?SharingIntegratingOntologies
>>>>>
>>>>>
>>>>>
>>>> _________________________________________________________________
>>>> Msg Archives: http://ontolog.cim3.net/forum/sio-dev/
>>>> Join Community: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
>>>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/sio-dev/
>>>> Unsubscribe: mailto:sio-dev-leave@xxxxxxxxxxxxxxxx
>>>> Community Shared Files: http://ontolog.cim3.net/file/work/SIO/
>>>> Community Wiki:
>http://ontolog.cim3.net/cgi-bin/wiki.pl?SharingIntegratingOntologies
>>>>
>>>>
>>>>
>>>>
>>> _________________________________________________________________
>>> Msg Archives: http://ontolog.cim3.net/forum/sio-dev/
>>> Join Community: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
>>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/sio-dev/
>>> Unsubscribe: mailto:sio-dev-leave@xxxxxxxxxxxxxxxx
>>> Community Shared Files: http://ontolog.cim3.net/file/work/SIO/
>>> Community Wiki:
>http://ontolog.cim3.net/cgi-bin/wiki.pl?SharingIntegratingOntologies
>>>
>>>
>>>
>>>
>>
>> _________________________________________________________________
>> Msg Archives: http://ontolog.cim3.net/forum/sio-dev/
>> Join Community: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/sio-dev/
>> Unsubscribe: mailto:sio-dev-leave@xxxxxxxxxxxxxxxx
>> Community Shared Files: http://ontolog.cim3.net/file/work/SIO/
>> Community Wiki:
>http://ontolog.cim3.net/cgi-bin/wiki.pl?SharingIntegratingOntologies
>>
>>
>>
>
> _________________________________________________________________
> Msg Archives: http://ontolog.cim3.net/forum/sio-dev/
> Join Community: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/sio-dev/
> Unsubscribe: mailto:sio-dev-leave@xxxxxxxxxxxxxxxx
> Community Shared Files: http://ontolog.cim3.net/file/work/SIO/
> Community Wiki:
>http://ontolog.cim3.net/cgi-bin/wiki.pl?SharingIntegratingOntologies
>
>
> (01)
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/sio-dev/
Join Community: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/sio-dev/
Unsubscribe: mailto:sio-dev-leave@xxxxxxxxxxxxxxxx
Community Shared Files: http://ontolog.cim3.net/file/work/SIO/
Community Wiki:
http://ontolog.cim3.net/cgi-bin/wiki.pl?SharingIntegratingOntologies (02)
|