This HTML5 document contains 7 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:P58_has_section_definition
rdf:type
owl:ObjectProperty
owl:inverseOf
ecrm:P58i_defines_section
rdfs:label
P58 has section definition
rdfs:domain
ecrm:E18_Physical_Thing
rdfs:range
ecrm:E46_Section_Definition
rdfs:comment
Scope note: This property links an area (section) named by a E46 Section Definition to the instance of E18 Physical Thing upon which it is found. The CRM handles sections as locations (instances of E53 Place) within or on E18 Physical Thing that are identified by E46 Section Definitions. Sections need not be discrete and separable components or parts of an object. This is part of a more developed path from E18 Physical Thing through P58, E46 Section Definition, P87 is identified by (identifies) that allows a more precise definition of a location found on an object than the shortcut P59 has section (is located on or within). A particular instance of a Section Definition only applies to one instance of Physical Thing. Examples: - HMS Victory (E22) has section definition "poop deck of HMS Victory" (E46) In First Order Logic: P58(x,y) ⊃ E18(x) P58(x,y) ⊃ E46(y)
skos:notation
P58