To determine whether a date conforms to the Extended Date Time Format Level 0-2, enter it into the field below and click "Submit". A level 0 EDTF string can be comprised of 1 of 3 features (Date, Date Time, or Interval). A level 1 EDTF string consists of the same features, but may incorportate uncertainty, approximations, and unspecified dates. Level 1 may also feature years with more than 4 digits, and/or seasons. Additionally, level 2 includes partial uncertain/approximate and partial unspecified dates. Level 2 also features multiple dates as lists, masked precision, extended intervals, exponential and scientific notation for 'big' years. The result of this form will be either 'Valid EDTF date' or 'Invalid EDTF date'.

Here are some examples using curl:

$ curl http://digital2.library.unt.edu/edtf/isValid.json?date=2012-01
{
    "validEDTF": true,
}

$ curl http://digital2.library.unt.edu/edtf/isValid.json?date=2012Jan
{
    "validEDTF": false,
}

$ curl "http://digital2.library.unt.edu/edtf/isValid.json?date=1234&callback=foo"
foo({
    "validEDTF": true,
})

$ curl http://digital2.library.unt.edu/edtf/isValid.json?date=1985-01-13&level=0
{
    "validEDTF": true,
}

    

Parameters

date: Required - the text respresentation of the date you want to verify.
callback: Optional - the text represenation of the jsonp callback wrapper.
level: Optional - the level at which you would like the given date verified against. If none is given, the service assumes you are verifying against the full EDTF spec.

Return Value

On success, a 200 OK response will be returned containing a JSON object that looks like this:
{
    "validEDTF": true
}
    
... or if a callback is provided:
callback-value({
    "validEDTF": true
})
    

Errors

A 400 Bad Request response will be return under the following conditions:
Hosted by the University of North Texas Libraries