Skip to main content

xsd:date vs. xsd:dataTime

Published on: 01/08/2013 Discussion Archived

The issue was raised at https://joinup.ec.europa.eu/release/dcat-application-profile-data-portals-europe-final-draft#comment-14600

 

The datatypes for the the release date and modification date are set to be xsd:date range.

Portals like the EU ODP have more precise indications: therefore it uses xsd:DateTime. The origin is that Eurostat is publishing twice a day an update to EU ODP.

In the current proposal this precision is explicitely be lost. Can it DCAT-AP be relaxed to be using xsd:DateTime union xsd:Date?

In this case precision is kept if present, on the other hand it is not mandatory so that no artificial date is inserted.

Component

Documentation

Category

improvement

Comments

Makx DEKKERS
Makx DEKKERS Thu, 01/08/2013 - 16:53

Consideration

I checked with the Government Linked Data WG and got the reply that the granularity of the "date" fields can be as precise as you want.

 

Proposed resolution

Use xsd:dateTime as a second allowable datatype for all date fields in the Application Profile

 

Proposed action

Update specification adding xsd:dateTime as valid datatype throughout section 7 alongside xsd:date.

Login or create an account to comment.