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

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

Namespace Prefixes

PrefixIRI
n13http://www.foodie-cloud.org/about/id/entity/http/purl.org/dc/terms/
n6http://www.foodie-cloud.org/about/id/http/purl.org/dc/terms/
n10http://www.w3.org/2008/05/skos#
dctermshttp://purl.org/dc/terms/
n9http://www.foodie-cloud.org/about/id/entity/http/purl.org/ontology/bibo/
n8http://www.foodie-cloud.org/about/id/entity/http/rdfs.org/sioc/
n5http://www.w3.org/2007/05/powder-s#
dchttp://purl.org/dc/elements/1.1/
skoshttp://www.w3.org/2004/02/skos/core#
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
n7http://dublincore.org/usage/terms/history/#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
dcterms:date
rdf:type
owl:ObjectProperty owl:DatatypeProperty owl:AnnotationProperty rdf:Property
rdfs:subPropertyOf
dc:date
dcterms:modified
2008-01-14
rdfs:label
Date Date
rdfs:range
rdfs:Literal
rdfs:isDefinedBy
dcterms:
rdfs:comment
A point or period of time associated with an event in the lifecycle of the resource. A point or period of time associated with an event in the lifecycle of the resource.
dcterms:hasVersion
n7:dateT-001
n5:describedby
n6:Location n8:ns n9:Document n13:Location
dcterms:description
Date may be used to express temporal information at any level of granularity. Recommended practice is to express the date, date/time, or period of time according to ISO 8601-1 [[ISO 8601-1](https://www.iso.org/iso-8601-date-and-time-format.html)] or a published profile of the ISO standard, such as the W3C Note on Date and Time Formats [[W3CDTF](https://www.w3.org/TR/NOTE-datetime)] or the Extended Date/Time Format Specification [[EDTF](http://www.loc.gov/standards/datetime/)]. If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Date ranges may be specified using ISO 8601 period of time specification in which start and end dates are separated by a '/' (slash) character. Either the start or end date may be missing. Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
dcterms:issued
2008-01-14 2008-01-14
skos:scopeNote
Use to link a bibliographic item to the date of an event. Check dcterms:created and other for proper specializations for this property
n10:scopeNote
Use to link a bibliographic item to the date of an event. Check dcterms:created and other for proper specializations for this property