- From: Simon Spero <sesuncedu@gmail.com>
- Date: Wed, 14 Feb 2018 11:01:22 -0500
- To: Mikael Pesonen <mikael.pesonen@lingsoft.fi>
- Cc: semantic-web@w3.org
- Message-ID: <CADE8KM44MnmgEpq4drseSJ+jn5a61quwHapmYTCsj-GtL1KJ2Q@mail.gmail.com>
On Feb 14, 2018 8:13 AM, "Mikael Pesonen" <mikael.pesonen@lingsoft.fi> wrote: We are describing resources by (almost randomly) picking suitable properties from various schemes, for example FOAF, Dublin Core, Nepomuk and Organization ontology. If a scheme defines class for the property, should the resource which is being described be always defined as such? If an ontology *defines* a domain for a property, then anything to which that property is applied is by *definition* a member of the specified class. So the decision is made for you ☺️. The bigger question is whether you are applying multiple properties to the same individual in such a way as to require it to be an instance of incompatible classes. For example, a graphical calendar app might create an individual that is a green Wednesday, but the source ontologies might require colored things to be visible. (Blue Monday is a special case :) Proper document description is not a simple problem; you may be better off using a pre-baked solution as much as possible. The development of the Europeana Data Model may be a good example to look at- See e.g. https://pro.europeana.eu/resources/standardization-tools/edm-documentation Simon
Received on Wednesday, 14 February 2018 16:01:48 UTC