This documentation relates to an old version of VIVO, version 1.10.x. Looking for another version? See all documentation.
- VIVO uses DateTimeValue and DateTimeInterval to model dates and datetimes. These are objects, not literal values. The object models are simple (see below). VIVO DateTimeValue supports the concept of a precision, which indicates whether a particular DateTimeValue is accurate to the day, or perhaps only to the month, or perhaps only to the year. Precision is an important idea – publication dates, for example, are often known only to year precision, and sometimes to year and month.
The model indicates that creating a DateTimeValue requires three triples – one to specify the type, one to specify the literal value of the datetime, and one to indicate the precision.
- VIVO provides the precisions shown below:
The DateTimeInterval is an entity that references one or two DateTimeValues. Either reference could be missing. An interval might have a start date and no end date, for example. To create a DateTimeValue with a start and end takes the statements below, where the start and end objects exist and have the URI as shown.