Closed andrea-perego closed 2 years ago
Maybe this brief discussion helps: https://github.com/OpenGovLD/specs/issues/109
Maybe this brief discussion helps: OpenGovLD/specs#109
Thanks, @akuckartz .
In addition to this, DCAT 2 allows any datetime-related datatypes. More precisely, the range of these properties is defined as follows:
rdfs:Literal
encoded using the relevant ISO 8601 Date and Time compliant string [DATETIME] and typed using the appropriate XML Schema datatype [XMLSCHEMA11-2] (xsd:gYear
,xsd:gYearMonth
,xsd:date
, orxsd:dateTime
).
See, e.g., §6.4.7 Property: release date.
This issue asks for a relaxation of the range requirement. Are there users that need support for more coarse grained temporal information?
I do not need support for this, as in Czechia these are always dates or dateTimes. However, I think we should stay in sync with DCAT unless there is a serious reason to diverge.
Personally, I would like to see a solution based on W3C Time Ontology but that is a completely different approach.
@jakubklimek in https://w3c.github.io/dxwg/dcat/#Property:resource_release_date it reads that W3C DCAT is allowing more than one xsd temporal representation.
So the request is actually more bringing DCAT-AP in line with the possibilities DCAT offers. (So less restrictions).
On W3C time ontology, that is worth exploring, but out of scope for this request.
During WG 21 Oct 2021, the wg decided to align with W3C DCAT to allow all temporal xsd types.
The range of properties as
dct:issued
anddct:modified
is described as follows:There are however cases when only the year is used.
The above description could be revised as follows: