Properties with too specific domains?

[GoogleCodeExporter]

Description of the issue or change request

This has been discussed in past occasions.

From 2010-08-10's telecon

    *  Properties with too specific domains!  Do not specify domain unless there is a good reason.
    * Maintenance and re-use problem.
    * In some cases the domain is the union of other classes, eg., hasPointOfContact’s domain is the union System + Manufacturer
    * OWL 2 annotations may be used to better address this issue.
    * Also look at OWL 2 profiles (one or more restrictions)
          o important to us?
          o nailed down domains good or bad? 
    * Which property restrictions are more for documenting than for reasoning?


Please provide any relevant information/links below

- http://marinemetadata.org/community/teams/ont/property-modeling

- Chat room messages at: 
http://marinemetadata.org/community/teams/ontdevices/agendas/minutes20090623

Original issue reported on code.google.com by [email protected] on 10 Aug 2010 at 4:15