W3C home > Mailing lists > Public > public-media-annotation@w3.org > April 2010

Catalog of Ontology Modeling Issues

From: Michael F Uschold <uschold@gmail.com>
Date: Wed, 14 Apr 2010 14:35:03 -0700
Message-ID: <y2k406b38b51004141435r2139cbccod82e2df25d9f5f0@mail.gmail.com>
To: public-lod@w3.org, public-semweb-lifesci@w3.org, semantic-web@w3.org, topbraid-composer-users@googlegroups.com, protege-owl@lists.stanford.edu, owl@lists.mindswap.org, obo-discuss@lists.sourceforge.net, ontolog-forum@ontolog.cim3.net, public-media-annotation@w3.org, semantic_web@googlegroups.com, protege-discussion@lists.stanford.edu
 * *
Dear Ontology Engineers*,

*Please forward this message to any other list that discusses ontology
modeling issues.

*WHAT: *We invite your participation in collecting and sharing ontology
modeling issues <http://ontologydesignpatterns.org/wiki/Community:Main> and
solutions on the Ontology Design Pattern
Wiki<http://ontologydesignpatterns.org/wiki>.
(ODP Wiki)

*
WHY: *There is a ton of content about ontology modeling issues in discussion
list archives, BUT:

   1. the same issues get discussed over and over on different lists;
   2. the information you want is hard to find;
   3. if you do find a relevant thread,
      1. the content is raw and hard to digest;
      2. the summary you want is hard to find, even it is there.
   4. there is no agreed place to go to find out about modeling issues;
   5. it is often easier just to ask the question again, and the cycle
   continues.

We have created the * ontology modeling
issues<http://ontologydesignpatterns.org/wiki/Community:Main>
* section in the ODP Wiki <http://ontologydesignpatterns.org/wiki> to
address these problems.

*HOW:  *We envision the following steps in the evolution of a modeling
issue:

   1. Lively discussion happens on some mailing list.
   2. Post a summary to the list of the key points raised, including the
   pros and cons of proposed solutions.
   3. Post a modeling issue on the ODP Wiki (based on that summary).
   4. Post a note to any relevant discussion lists inviting them to
   contribute to the Wiki.
   5. Discuss and refine the issue further in the ODP Wiki
   6. Post major updates back to relevant discussion lists.

OR, start with step 3, and post the modeling issue directly on the ODP Wiki.

*

**To  Contribute:*

   1. Visit *Ontology Design Patterns Wiki*<http://ontologydesignpatterns.org/>
   2. Click the "*How to
register*<http://ontologydesignpatterns.org/wiki/Odp:Register>" link
at
   lower left of the page; follow instructions to get a login name and
   password.
   3. Visit the
"**<http://ontologydesignpatterns.org/wiki/Odp:WhatIsAnExemplaryOntology>
   *Ontology Modeling
Issues<http://ontologydesignpatterns.org/wiki/Community:Main>
   *" page for further information,examples and instructions.

*
Examples: *(from discussion lists)

   1. Proliferation of URIs, Managing
Coreference<http://ontologydesignpatterns.org/wiki/Community:Proliferation_of_URIs%2C_Managing_Coreference>
   2. Overloading owl
sameAs<http://ontologydesignpatterns.org/wiki/Community:GI_Overloading_owl_sameAs>
   3. Versioning and
URIs<http://ontologydesignpatterns.org/wiki/Community:Versioning_and_URIs>
   4. Representing
Species<http://ontologydesignpatterns.org/wiki/Community:epresenting_Species>
   5. Using SKOS
Concept<http://ontologydesignpatterns.org/wiki/Community:Using_SKOS_Concept>
   6. Resource multiple
attribution<http://ontologydesignpatterns.org/wiki/Community:Resource_multiple_attribution>



The above issues were ones that I found by pouring over all the threads in
the linking open data list from December 2009, plus some that I was directly
involved from 2008.  There are many others to be found from many other
lists.

This work was originally supported by the NeOn
project.<http://www.neon-project.org/>

Thanks very much,
 Michael
======
Received on Wednesday, 14 April 2010 21:35:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 14 April 2010 21:35:48 GMT