This HTML5 document contains 8 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n2http://erlangen-crm.org/140617/
wdrshttp://www.w3.org/2007/05/powder-s#
n4http://demo.openlinksw.com/about/id/entity/http/erlangen-crm.org/140617/
rdfshttp://www.w3.org/2000/01/rdf-schema#
skoshttp://www.w3.org/2004/02/skos/core#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
n2:P20_had_specific_purpose
rdf:type
owl:ObjectProperty
owl:inverseOf
n2:P20i_was_purpose_of
rdfs:label
P20 had specific purpose
rdfs:domain
n2:E7_Activity
rdfs:range
n2:E5_Event
rdfs:comment
Scope note: This property identifies the relationship between a preparatory activity and the event it is intended to be preparation for. This includes activities, orders and other organisational actions, taken in preparation for other activities or events. P20 had specific purpose (was purpose of) implies that an activity succeeded in achieving its aim. If it does not succeed, such as the setting of a trap that did not catch anything, one may document the unrealized intention using P21 had general purpose (was purpose of):E55 Type and/or P33 used specific technique (was used by): E29 Design or Procedure. Examples: - Van Eyck's pigment grinding in 1432 (E7) had specific purpose the painting of the Ghent alter piece (E12)
wdrs:describedby
n4:E24_Physical_Man-Made_Thing
skos:notation
P20