search

dilo00o / tdwg-rdf

Automatically exported from code.google.com/p/tdwg-rdf
0 stars 0 forks source link

Modeling as a class vs. an instance of a class #12

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Topic or term(s) which needs clarification:

It is possible to model resources as many classes or as many instances of a few 
classes.  There are tradeoffs which, depending on the circumstances, make one 
approach more suitable than the other.  

Links to existing resources related to the topic:

email discussions at
http://groups.google.com/group/tdwg-rdf/browse_thread/thread/6f05ec22e0a89f25
https://groups.google.com/forum/?fromgroups#!topic/tdwg-rdf/PDISfYpsH2c
http://lists.tdwg.org/pipermail/tdwg-content/2011-May/002388.html

Wiki page to be used for guidelines:

FewClassesVsMany

Specific considerations to be addressed in guideline:

Under what circumstances is it beneficial to model the system as many classes?
Under what circumstances is it beneficial to model the system as few classes 
with many instances?

Original issue reported on code.google.com by steve.ba...@vanderbilt.edu on 12 Jun 2012 at 12:24

GoogleCodeExporter commented 8 years ago 
Once a decision is taken on the issue of many classes vs many instances, it is 
worth examining whether one or the other of the standard OWL2 profiles can 
profitably be enforced on the ontology.  See 
http://www.w3.org/2007/OWL/wiki/Profiles and 
http://owl.cs.manchester.ac.uk/validator/

My reading of the Profile descriptions, especially in the cited wiki page, is 
that EL (resp QL) will do better with a large number of classes (resp of 
instances.)

Original comment by morris.bob on 13 Jun 2012 at 4:04