Hi Heiko,
The Timex3 standard for temporal expressions [1], as widely used for
linguistic analysis, suggests 'XX' if the date or month is unknown. I'm
not aware if people are using that to encode temporal expressions in
Linked datasets, but it would definitely be a better solution than using
'01' for unknown days or months.
Best wishes
Isabelle
[1]
http://www.timeml.org/site/publications/timeMLdocs/timeml_1.2.1.html#timex3
--
Isabelle Augenstein,
Department of Computer Science, The University of Sheffield,
Regent Court, 211 Portobello, S1 4DP, Sheffield, UK
Tel: +44(0) 1442221876, Fax: +44(0)1142221810
www: http://staffwww.dcs.shef.ac.uk/people/I.Augenstein/
On 10/02/2014 14:43, Jerven Bolleman wrote:
Hi Heiko,
http://www.w3.org/TR/xmlschema-2/#gYear and
http://www.w3.org/TR/xmlschema-2/#gYeargYearMonth
are the datatypes that you should use.
Regards,
Jerven
On 10 Feb 2014, at 15:37, Heiko Paulheim <[email protected]>
wrote:
Hi all,
xsd:dateTime and xsd:date are used frequently for encoding dates in RDF, e.g.,
for birthdays in the vcard ontology [1]. Is there any best practice to encode
incomplete date information, e.g., if only the birth *year* of a person is
known?
As far as I can see, the XSD spec enforces the provision of all date components [2], but
"1997-01-01" seems like a semantically wrong way of expressing that someone is
born in 1997, but the author does not know exactly when.
Thanks,
Heiko
[1] http://www.w3.org/2006/vcard/ns
[2] http://www.w3.org/TR/xmlschema-2/#dateTime
[3] http://www.w3.org/TR/xmlschema-2/#date
--
Dr. Heiko Paulheim
Research Group Data and Web Science
University of Mannheim
Phone: +49 621 181 2646
B6, 26, Room C1.08
D-68159 Mannheim
Mail: [email protected]
Web: www.heikopaulheim.com
