@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix ns0: <Date\u0020may\u0020be\u0020used\u0020to\u0020express\u0020temporal\u0020information\u0020at\u0020any\u0020level\u0020of\u0020granularity.\u0020\u0020Recommended\u0020practice\u0020is\u0020to\u0020express\u0020the\u0020date,\u0020date/time,\u0020or\u0020period\u0020of\u0020time\u0020according\u0020to\u0020ISO\u00208601-1\u0020[[ISO\u00208601-1](https://www.iso.org/iso-8601-date-and-time-format.html)]\u0020or\u0020a\u0020published\u0020profile\u0020of\u0020the\u0020ISO\u0020standard,\u0020such\u0020as\u0020the\u0020W3C\u0020Note\u0020on\u0020Date\u0020and\u0020Time\u0020Formats\u0020[[W3CDTF](https://www.w3.org/TR/NOTE-datetime)]\u0020or\u0020the\u0020Extended\u0020Date/Time\u0020Format\u0020Specification\u0020[[EDTF](http://www.loc.gov/standards/datetime/)].\u0020\u0020If\u0020the\u0020full\u0020date\u0020is\u0020unknown,\u0020month\u0020and\u0020year\u0020(YYYY-MM)\u0020or\u0020just\u0020year\u0020(YYYY)\u0020may\u0020be\u0020used.\u0020Date\u0020ranges\u0020may\u0020be\u0020specified\u0020using\u0020ISO\u00208601\u0020period\u0020of\u0020time\u0020specification\u0020in\u0020which\u0020start\u0020and\u0020end\u0020dates\u0020are\u0020separated\u0020by\u0020a\u0020'/> .
dct:available
rdfs:subPropertyOf dct:date .
dct:created
rdfs:subPropertyOf dct:date .
dct:date
dct: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."@en ;
dct:issued "2008-01-14"^^<http://www.w3.org/2001/XMLSchema#date> ;
a owl:AnnotationProperty, owl:DatatypeProperty, owl:NamedIndividual ;
rdfs:comment "A point or period of time associated with an event in the lifecycle of the resource."@en ;
rdfs:isDefinedBy <http://purl.org/dc/terms/> ;
rdfs:label "Date"@en ;
rdfs:range rdfs:Literal ;
rdfs:subPropertyOf dc:date .
dct:dateAccepted
rdfs:subPropertyOf dct:date .
dct:dateCopyrighted
rdfs:subPropertyOf dct:date .
dct:dateSubmitted
rdfs:subPropertyOf dct:date .
dct:issued
rdfs:subPropertyOf dct:date .
dct:modified
rdfs:subPropertyOf dct:date .
dct:valid
rdfs:subPropertyOf dct:date .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix ns0: <Date\u0020may\u0020be\u0020used\u0020to\u0020express\u0020temporal\u0020information\u0020at\u0020any\u0020level\u0020of\u0020granularity.\u0020\u0020Recommended\u0020practice\u0020is\u0020to\u0020express\u0020the\u0020date,\u0020date/time,\u0020or\u0020period\u0020of\u0020time\u0020according\u0020to\u0020ISO\u00208601-1\u0020[[ISO\u00208601-1](https://www.iso.org/iso-8601-date-and-time-format.html)]\u0020or\u0020a\u0020published\u0020profile\u0020of\u0020the\u0020ISO\u0020standard,\u0020such\u0020as\u0020the\u0020W3C\u0020Note\u0020on\u0020Date\u0020and\u0020Time\u0020Formats\u0020[[W3CDTF](https://www.w3.org/TR/NOTE-datetime)]\u0020or\u0020the\u0020Extended\u0020Date/Time\u0020Format\u0020Specification\u0020[[EDTF](http://www.loc.gov/standards/datetime/)].\u0020\u0020If\u0020the\u0020full\u0020date\u0020is\u0020unknown,\u0020month\u0020and\u0020year\u0020(YYYY-MM)\u0020or\u0020just\u0020year\u0020(YYYY)\u0020may\u0020be\u0020used.\u0020Date\u0020ranges\u0020may\u0020be\u0020specified\u0020using\u0020ISO\u00208601\u0020period\u0020of\u0020time\u0020specification\u0020in\u0020which\u0020start\u0020and\u0020end\u0020dates\u0020are\u0020separated\u0020by\u0020a\u0020'/> .
dct:available
rdfs:subPropertyOf dct:date .
dct:created
rdfs:subPropertyOf dct:date .
dct:date
dct: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."@en ;
dct:issued "2008-01-14"^^<http://www.w3.org/2001/XMLSchema#date> ;
a owl:AnnotationProperty, owl:DatatypeProperty, owl:NamedIndividual ;
rdfs:comment "A point or period of time associated with an event in the lifecycle of the resource."@en ;
rdfs:isDefinedBy <http://purl.org/dc/terms/> ;
rdfs:label "Date"@en ;
rdfs:range rdfs:Literal ;
rdfs:subPropertyOf dc:date .
dct:dateAccepted
rdfs:subPropertyOf dct:date .
dct:dateCopyrighted
rdfs:subPropertyOf dct:date .
dct:dateSubmitted
rdfs:subPropertyOf dct:date .
dct:issued
rdfs:subPropertyOf dct:date .
dct:modified
rdfs:subPropertyOf dct:date .
dct:valid
rdfs:subPropertyOf dct:date .