Dear all,
Attached you can find the rdfs encoding for the .1 properties as Martin
described.
Also in the file http://www.ics.forth.gr/isl/CRMext/Roles.pdf you can
see 3 possible solutions and relevant examples.
The rdfs has not been tested extensively, so if you notice any errors
please let me know.
Best,
Maria
On 3/2/2016 11:47 μμ, Simon Spero wrote:
There is generally no problem with reification qua reification!
The CRM is committed to reification in its model of actions and
events. See Davidson's "The Logical Form of Action Sentences" [1] for
the paper that made this approach dominant. It's worth a read.
The collection "Essays on Action and Events" [2] collects other
related papers; for commentary see [3] - mostly for Quine's essay on
identity conditions for events to which Davidson is replying in the
second edition of [2]. Identity is one of the things that requires
consideration when considering reification.
-----
What is usually being objected to specifically is "RDF reification".
This facility consists of a class called rdf:Statement, together with
the properties - subject, predicate, and object.
The mechanism that is provided is pretty awful.
Here is a reified statement.
_:x a rdf:Statement,
rdf:subject :foo,
rdf:predicate :property,
rdf:object :bar .
This does *not* entail
:foo :property :bar.
--------
[1]
http://isites.harvard.edu/fs/docs/icb.topic638346.files/Davidson1967.pdf
[2]
http://www.oxfordscholarship.com/view/10.1093/0199246270.001.0001/acprof-9780199246274
[3]
https://books.google.com/books/about/Actions_and_Events.html?id=Tjl6QgAACAAJ&source=kp_cover
On Feb 3, 2016 2:02 PM, "Dan Matei" <[email protected]
<mailto:[email protected]>> wrote:
Despite the fact that I'm always told that reification is not
recomanded, I decided to "piser contre le vent" :-)
Functionally, the reification is just natural. Proof: the
"invention" of .1 properties in CRM.
Aaa, if the formalisms we have do not handle it well, please
invent a suitable formalism, my dear friends.
Dan
------------------------------------------------------------------
Dan Matei
consultant (documentaristică, biblioteci digitale),
Fundația Gellu Naum,
[Institutul Național al Patrimoniului]
-----Original Message-----
From: martin <[email protected] <mailto:[email protected]>>
To: [email protected] <mailto:[email protected]>
Date: Wed, 3 Feb 2016 20:09:26 +0200
Subject: Re: [Crm-sig] Modelling .1 properties
> Dear Simon,
>
> Our messages crossed, your analysis is correct! We have discussed
> however, that reification or annotation is not recommended,
rather an
> introduction of a node (class) representing a triary property
rather than
> an individual entity. From the existence of an instance of
> PC14_carried_out_by we can automatically infer
> the instance of P14, as described in the formalization.
>
> All the best,
>
> martin
>
> On 3/2/2016 7:55 μμ, Simon Spero wrote:
> >
> > The first order formalization given in the crm document are:
> >
> > P14(x,y,z) ⊃ [P14(x,y) ∧ E55(z)]
> >
> > Note that the predicate on the left hand side has three arguments,
> > which is more arguments than rdf is comfortable with.
> >
> > The "in the role of" property is modifying an instance of a
"carried
> > out by" property.
> > An activity can be carried out by several different agents,
each in a
> > different role, so the property cannot be attached directly to the
> > activity.
> >
> > There are several possible ways of representing this using
semantic
> > web tools.
> >
> > The first approach is to use RDF reification. I am not going
to say
> > anything more about this.
> >
> > If you are using OWL 2, you can add an annotation each
"carried out
> > by" property assertion. This is not ideal, as annotations are not
> > really supposed to be part of the data in the model, and most
> > reasoners ignore them. They are also not easy to work with in RDF.
> >
> > A third approach is to define your own class for reification,
> > representing an instance of a "carrying out" ; this class
would have
> > properties relating the activity, the agent, and the role.
> >
> > The best approach may be to define a sub property of P14 for
each type
> > of carrying out in a role which is relevant to your model.
> > You can specify the role associated with all uses of this property
> > using a property whose subject is the subproperty.
> >
> > Simon
> >
> > On Feb 3, 2016 10:01 AM, "Allison Miller"
> > <[email protected]
<mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>>
> > wrote:
> >
> > Hello,
> >
> > I wish to use the CIDOC CRM but need a formal model to do
so and
> > have a question concerning .1 properties.
> >
> > eg. E7 Activity has: P14 carried out by (performed): E39
Actor and
> > (P14.1 in the role of: E55 Type)
> >
> > It is a property I need to use - but I can’t work out how
to model it!
> >
> > I thought I could use the Erlangen OWL implementation, but
I can’t
> > find these properties in it. (That’s not to claim they aren’t
> > there, my knowledge of OWL is limited.)
> >
> > I would welcome any guidance on P14.1, and other .1
properties, in
> > the Erlangen implementation, or advice on including them in a
> > definition compatible with Semantic Web technologies if
anyone has
> > done this.
> >
> > Kind regards,
> >
> > Alli
> >
> > E-mail: [email protected]
<mailto:[email protected]>
> > <mailto:[email protected]
<mailto:[email protected]>>
> >
> > Web: www.sysemia.com <http://www.sysemia.com>
<http://www.sysemia.com/>
> >
> >
> >
> > Sysemia Limited
> >
> > The Innovation Centre, Bristol & Bath Science Park, Dirac
> > Crescent, Emerson's Green, Bristol BS16 7FR
> >
> > Registered in England and Wales. Company Number: 7555456
> >
> > DISCLAIMER
> >
> > Information contained in this e-mail is intended for the
use of
> > the addressee only, and is confidential and may also be
> > privileged. If you receive this message in error, please
advise us
> > immediately. If you are not the intended recipient(s),
please note
> > that any form of distribution, copying or use of this
> > communication or the information in it is strictly
prohibited and
> > may be unlawful. Attachments to this e-mail may contain
software
> > viruses which may damage your systems. Sysemia Ltd have taken
> > reasonable steps to minimise this risk, but we advise that any
> > attachments are virus checked before they are opened.
> >
> >
> > _______________________________________________
> > Crm-sig mailing list
> > [email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
> > http://lists.ics.forth.gr/mailman/listinfo/crm-sig
> >
> >
> >
> > _______________________________________________
> > Crm-sig mailing list
> > [email protected] <mailto:[email protected]>
> > http://lists.ics.forth.gr/mailman/listinfo/crm-sig
>
>
> --
>
> --------------------------------------------------------------
> Dr. Martin Doerr | Vox:+30(2810)391625
<tel:%2B30%282810%29391625> |
> Research Director | Fax:+30(2810)391638
<tel:%2B30%282810%29391638> |
> | Email: [email protected]
<mailto:[email protected]> |
> |
> Center for Cultural Informatics |
> Information Systems Laboratory |
> Institute of Computer Science |
> Foundation for Research and Technology - Hellas (FORTH) |
> |
> N.Plastira 100, Vassilika Vouton, |
> GR70013 Heraklion,Crete,Greece |
> |
> Web-site: http://www.ics.forth.gr/isl |
> --------------------------------------------------------------
>
_______________________________________________
Crm-sig mailing list
[email protected] <mailto:[email protected]>
http://lists.ics.forth.gr/mailman/listinfo/crm-sig
_______________________________________________
Crm-sig mailing list
[email protected]
http://lists.ics.forth.gr/mailman/listinfo/crm-sig
--
------------------------------------------------------------------------
Maria Theodoridou
R & D Engineer
Information Systems Laboratory & Centre for Cultural Informatics
Institute of Computer Science
Foundation of Research and Technology - Hellas (FORTH)
Science and Technology Park of Crete
Vassilika Vouton, P.O.Box 1385, GR-711 10 Heraklion, Crete, Greece
Tel.: +30-2810-391731 Fax: +30-2810-391638 E-mail: [email protected]
URL: http://www.ics.forth.gr/isl
------------------------------------------------------------------------
<?xml version="1.0"?>
<!--
CRMpc 1.0 Encoded in RDFS modified December 5, 2014
RDFS created by FORTH-ICS November 19, 2014
Introducing class PC0 CRM_Property and properties P01 has domain and P02 has range
in order to encode links on links in RDF
All XX.1 properties of CIDOC-CRM are introduced as subclasses of PC0 CRM_Property
-->
<rdf:RDF xml:lang="en"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#";
xml:base="http://www.cidoc-crm.org/cidoc-crm/";>
<rdfs:Class rdf:about="PC0_CRM_Property">
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P01_has_domain">
<rdfs:domain rdf:resource="PC0_CRM_Property"/>
<rdfs:range rdf:resource="E1_CRM_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="P01i_is_domain_of">
<rdfs:domain rdf:resource="E1_CRM_Entity"/>
<rdfs:range rdf:resource="PC0_CRM_Property"/>
</rdf:Property>
<rdf:Property rdf:about="P02_has_range">
<rdfs:domain rdf:resource="PC0_CRM_Property"/>
<rdfs:range rdf:resource="E1_CRM_Entity"/>
</rdf:Property>
<rdf:Property rdf:about="P02i_is_range_of">
<rdfs:domain rdf:resource="E1_CRM_Entity"/>
<rdfs:range rdf:resource="PC0_CRM_Property"/>
</rdf:Property>
<rdf:Property rdf:about="P03_has_range_literal">
<rdfs:domain rdf:resource="PC0_CRM_Property"/>
<rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Literal"/>
</rdf:Property>
<rdfs:Class rdf:about="PC3_has_note">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P3.1_has_type">
<rdfs:domain rdf:resource="PC3_has_note"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC14_carried_out_by">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P14.1_in_the_role_of">
<rdfs:domain rdf:resource="PC14_carried_out_by"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC16_used_specific_object">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P16.1_mode_of_use">
<rdfs:domain rdf:resource="PC16_used_specific_object"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC19_was_intended_use_of">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P19.1_mode_of_use">
<rdfs:domain rdf:resource="PC19_was_intended_use_of"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC62_depicts">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P62.1_mode_of_depiction">
<rdfs:domain rdf:resource="PC62_depicts"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC67_refers_to">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P67.1_has_type">
<rdfs:domain rdf:resource="PC67_refers_to"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC69_is_associated_with">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P69.1_has_type">
<rdfs:domain rdf:resource="PC69_is_associated_with"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC102_has_title">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P102.1_has_type">
<rdfs:domain rdf:resource="PC102_has_title"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC107_has_current_or_former_member">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P107.1_kind_of_member">
<rdfs:domain rdf:resource="PC107_has_current_or_former_member"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC130_shows_features_of">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P130.1_kind_of_similarity">
<rdfs:domain rdf:resource="PC130_shows_features_of"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC136_was_based_on">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P136.1_in_the_taxonomic_role">
<rdfs:domain rdf:resource="PC136_was_based_on"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC137_exemplifies">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P137.1_in_the_taxonomic_role">
<rdfs:domain rdf:resource="PC137_exemplifies"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC138_represents">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P138.1_mode_of_representation">
<rdfs:domain rdf:resource="PC138_represents"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC139_has_alternative_form">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P139.1_has_type">
<rdfs:domain rdf:resource="PC139_has_alternative_form"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
<rdfs:Class rdf:about="PC144_joined_with">
<rdfs:subClassOf rdf:resource="PC0_CRM_Property"/>
<rdfs:comment></rdfs:comment>
</rdfs:Class>
<rdf:Property rdf:about="P144.1_kind_of_member">
<rdfs:domain rdf:resource="PC144_joined_with"/>
<rdfs:range rdf:resource="E55_Type"/>
</rdf:Property>
</rdf:RDF>
