Damian Steer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [sorry, forgot to reply-all] Peter Ansell wrote: | That is fine for classes, but how do you map individuals without metadata side-effects? Looking at my previous answer again I think I should take another run at this :-) One way of thinking about equivalence is in terms of substitution: if :x :equiv :y when is it safe to substitute :x with :y? The default is: it's not safe (obviously). :x equivalentClass :y -> safe when used as a class (e.g. rdf:type :x) :x sameAs :y -> always safe (watch out!) :x sameConceptAs :y -> safe in subject positions
do you mean subject in the 'topic, dc:subject' sense, rather than subject/predicate/object sense? On first reading I thought you meant the latter, which would be problematic since any inverse of property can flip values into 'object' role. So assuming the former, I quite agree.
Also thanks for expanding on what I meant. I was indeed picking a strong example to emphasise my (under articulated) case. Using an owl:sameAs claim between independently developed classes and properties is almost always misleading, confusing and untrue. So yup I agree that application-specific properties such as these are often more useful.
Also btw folks there is no such thing as dc:author. It was changed in the mid-late 1990s to be dc:creator, so as to better cover non-written creations such as images, museum artifacts etc. So best to avoid/fix it in mail threads before 'dc:author' ends up getting mentioned in books etc.
cheers, Dan
:x sameWorkAs :y -> safe for author, creation date :x sameManifestationAs :y -> safe for the the above, and length (?) Does that help? Damian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI4NdRAyLCB+mTtykRAppqAJ9kzkWgcWt0zeWfWdMfWwqtdhoblwCeNCWH 54J20+PaNd1xmCmcFLs9DN8= =/gW2 -----END PGP SIGNATURE-----
