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

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

Namespace Prefixes

PrefixIRI
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#
efrbroohttp://erlangen-crm.org/efrbroo/
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
efrbroo:R33_has_content
rdf:type
owl:DatatypeProperty
rdfs:subPropertyOf
ecrm:P3_has_note
rdfs:label
has content
rdfs:domain
efrbroo:F12_Nomen
rdfs:comment
Scope note: This property associates an instance of F12 Nomen with one or more equivalent serialized content models for it. In digital form the symbol arrangement constituting an instance of F12 Nomen can only be represented through a particular encoding, for example ASCII or Latin1 for the Latin script. We call such a representation a content model. The property R33.1 has encoding: E55 Type allows for specifying the encoding of a particular associated content model. Together with this specification, a content model allows for unambiguously defining a nomen independently from the encoding used for representing the content. Examples: - ‘0x65 0x61 0x72 0x74 0x68’ [R33.1 has encoding ASCII] - ‘0x0065 0x0061 0x0072 0x0074 0x0068’ [R33.1 has encoding UNICODE UTF16] - ‘earth ’ [R33.1 has encoding printed Latin Arial] Scope note: This property associates an instance of F12 Nomen with one or more equivalent serialized content models for it. In digital form the symbol arrangement constituting an instance of F12 Nomen can only be represented through a particular encoding, for example ASCII or Latin1 for the Latin script. We call such a representation a content model. The property R33.1 has encoding: E55 Type allows for specifying the encoding of a particular associated content model. Together with this specification, a content model allows for unambiguously defining a nomen independently from the encoding used for representing the content. Examples: - ‘0x65 0x61 0x72 0x74 0x68’ [R33.1 has encoding ASCII] - ‘0x0065 0x0061 0x0072 0x0074 0x0068’ [R33.1 has encoding UNICODE UTF16] - ‘earth ’ [R33.1 has encoding printed Latin Arial] Properties: R33.1 has encoding: E55 Type