RE: The 'valid time' requirement

Frans,

On Thursday, October 22, 2015 11:45 AM, Frans Knibbe wrote:

> On: Wednesday, October 21, 2015 2:57 PM, Frans Knibbe wrote:
> [...]
> 
> > I think the spatial scope limitation for requirements is a very just one and
> > should not be disregarded easily. It guards us against taking on too much of
> > all the things that can be done towards improving data on the web. The
> > danger of taking on too much is that we won't have the capacity to actually
> > make serious improvements, our capacities will be spread too thin and our
> > efforts will lack focus. Moreover, we have expertise on spatial matters, but
> > making decisions on subjects that have an application that is not uniquely
> > spatial should probably involve other experts too. So I think that
> > conscientiously focussing on things that are really spatial will help our group
> > to reach meaningful results.
> 
> So your proposal would be to delegate this to the Data on the Web WG?
> 
> Poor Data on the Web WG ... they have to solve a lot of problems. But yes, in
> general what we could do is to bring the matter to the attention of other
> communities that do have this in scope.
> 
> The community behind the DCMI metadata terms could also be a good
> target. It has the definition of dcterms:valid, which can be used to indicate
> the temporal validity of data. Unfortunately, it is restricted to dates. What we
> probably want is make use of other expressions of time to indicate the
> interval in which something is valid, and to be able to use temporal functions
> (Allen's algebra) on validity intervals. So once OWL Time gets updated to
> allow more freedom in expressions of time, it would be great if the DCMI had
> a 'valid' property with a liberal time range, for which OWL Time based
> expressions can be used.

dcterms:valid isn't necessarily restricted to dates. The property has range rdf:Literal and refines dcterms:date [1]. The range of dcterms:date is also rdf:Literal (surprise...), its definition is "a point or period of time associated with an event in the lifecycle of the resource" (period is good!) and the comment says that "date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF]", the important part being "temporal information at any level of granularity".

[1] http://purl.org/dc/terms/date


Best,

Lars

Received on Thursday, 22 October 2015 18:10:30 UTC