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
skoshttp://www.w3.org/2004/02/skos/core#
rdfshttp://www.w3.org/2000/01/rdf-schema#
ecrmhttp://erlangen-crm.org/current/
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
ecrm:P56_bears_feature
rdf:type
owl:ObjectProperty
rdfs:subPropertyOf
ecrm:P46_is_composed_of
owl:inverseOf
ecrm:P56i_is_found_on
rdfs:label
P56 bears feature
rdfs:domain
ecrm:E19_Physical_Object
rdfs:range
ecrm:E26_Physical_Feature
rdfs:comment
Scope note: This property links an instance of E19 Physical Object to an instance of E26 Physical Feature that it bears. An E26 Physical Feature can only exist on one object. One object may bear more than one E26 Physical Feature. An E27 Site should be considered as an E26 Physical Feature on the surface of the Earth. An instance B of E26 Physical Feature being a detail of the structure of another instance A of E26 Physical Feature can be linked to B by use of the property P46 is composed of (forms part of). This implies that the subfeature B is P56i found on the same E19 Physical Object as A. P56 bears feature (is found on) is a shortcut. A more detailed representation can make use of the fully developed (i.e. indirect) path from E19 Physical Object through P59 has section (is located on or within), E53 Place, P53 has former or current location (is former or current location of) to E26 Physical Feature. Examples: - silver cup 232 (E22) bears feature 32 mm scratch on silver cup 232 (E26) In First Order Logic: P56(x,y) ⊃E19(x) P56(x,y) ⊃ E26(y) P56(x,y) ⊃ P46(x,y)
skos:notation
P56