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

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

Namespace Prefixes

PrefixIRI
n16http://kingsley.idehen.net/about/id/entity/urn/ontology:semantic:
dctermshttp://purl.org/dc/terms/
n8http://kingsley.idehen.net/about/id/entity/http/rdfs.org/sioc/
foafhttp://xmlns.com/foaf/0.1/
n7http://purl.org/dc/terms/subject#
wdrshttp://www.w3.org/2007/05/powder-s#
dchttp://purl.org/dc/elements/1.1/
schemahttp://schema.org/
n11http://kingsley.idehen.net/sparql/
skoshttp://www.w3.org/2004/02/skos/core#
rdfshttp://www.w3.org/2000/01/rdf-schema#
voidhttp://rdfs.org/ns/void#
n5http://kingsley.idehen.net/about/id/http/purl.org/dc/terms/
n12http://kingsley.idehen.net/about/id/entity/http/purl.org/dc/terms/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n17http://dublincore.org/usage/terms/history/#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
dcterms:subject
rdf:type
owl:ObjectProperty rdf:Property schema:CreativeWork
dcterms:modified
2012-06-14
rdfs:label
Subject
rdfs:isDefinedBy
dcterms:
rdfs:comment
The topic of the resource. A topic of the resource.
rdfs:subPropertyOf
dc:subject
foaf:topic
dcterms:dateAccepted dcterms:LCC dcterms:Location dcterms:temporal dcterms:conformsTo dcterms:Standard dcterms:spatial dcterms:isFormatOf dcterms:hasFormat dcterms:Agent dcterms:isRequiredBy dcterms:requires dcterms:isReplacedBy dcterms: dcterms:replaces dcterms:PhysicalResource dcterms:PhysicalMedium dcterms:isReferencedBy dcterms:Frequency dcterms:accrualPolicy dcterms:Policy dcterms:extent dcterms:created dcterms:MethodOfAccrual dcterms:modified dcterms:RFC1766 dcterms:accrualPeriodicity dcterms:MethodOfInstruction dcterms:accrualMethod dcterms:RFC5646 dcterms:ISO639-2 dcterms:provenance dcterms:ProvenanceStatement dcterms:instructionalMethod dcterms:license dcterms:LicenseDocument dcterms:rightsHolder dcterms:bibliographicCitation dcterms:isVersionOf dcterms:creator dcterms:BibliographicResource dcterms:educationLevel dcterms:hasVersion dcterms:accessRights dcterms:dateCopyrighted dcterms:relation dcterms:MediaType dcterms:rights dcterms:dateSubmitted dcterms:Jurisdiction dcterms:isPartOf dcterms:issued dcterms:type dcterms:language dcterms:FileFormat dcterms:publisher dcterms:date dcterms:MESH dcterms:description dcterms:format dcterms:hasPart dcterms:abstract dcterms:LCSH dcterms:alternative dcterms:contributor dcterms:RFC4646 dcterms:ISO639-3 dcterms:RFC3066 dcterms:Period dcterms:references dcterms:W3CDTF dcterms:Box dcterms:ISO3166 dcterms:SizeOrDuration dcterms:URI dcterms:medium dcterms:available dcterms:Point dcterms:valid dcterms:AgentClass dcterms:identifier dcterms:tableOfContents dcterms:RightsStatement dcterms:audience dcterms:title dcterms:coverage dcterms:LocationPeriodOrJurisdiction dcterms:source dcterms:LinguisticSystem dcterms:NLM dcterms:MediaTypeOrExtent dcterms:IMT dcterms:TGN dcterms:DCMIType dcterms:UDC dcterms:PeriodOfTime dcterms:mediator dcterms:DDC
owl:sameAs
n7:this
void:sparqlEndpoint
n11:
dcterms:hasVersion
n17:subjectT-002
dcterms:description
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. Recommended practice is to refer to the subject with a URI. If this is not possible or feasible, a literal value that identifies the subject may be provided. Both should preferably refer to a subject in a controlled vocabulary.
dcterms:issued
2008-01-14
skos:note
This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration.
wdrs:describedby
n5: n8:ns n12: n12:hasPart n5:hasPart n5:source n12:source n16:mapping
schema:url
dcterms:subject
schema:mainEntity
n12:subject