W3C home > Mailing lists > Public > public-schemaorg@w3.org > September 2016

Re: Open intervals for temporalCoverage ?

From: Thomas Francart <thomas.francart@sparna.fr>
Date: Wed, 14 Sep 2016 12:34:00 +0200
Message-ID: <CAPugn7VXqxyhmbGUHBBh-teEh1Qg0NDrXjcKLK=ujABOyTsxRA@mail.gmail.com>
To: Richard Wallis <richard.wallis@dataliberate.com>
Cc: "schema.org Mailing List" <public-schemaorg@w3.org>
Richard

2016-09-14 12:14 GMT+02:00 Richard Wallis <richard.wallis@dataliberate.com>:

> As the documentation for temporalCoverage
> <http://schema.org/temporalCoverage> states, it expects ISO 8601
> time interval format
> <https://en.wikipedia.org/wiki/ISO_8601#Time_intervals>, so the question
> lies there.
>
> Your understanding I believe is correct, that the current version of the
> standard ( *ISO 8601:2000* ) does not support open ended time intervals.
>
> In Dublin Core, which bases its formats on ISO 8601,  open ended
> intervals are supported
> <http://www.ukoln.ac.uk/metadata/dcmi/date-dccd-odrf/> but explicitly
> state “This representation of an *open date range* is *not* compatible
> with the representation of a time-interval defined by ISO8601:2000.”
>
> This has been the subject of a short https://github.com/project-
> open-data/project-open-data.github.io/issues/415.
>

Many thanks for the pointers.


> I support their conclusion that an open ended time period would be
> currently best represented by the appropriate use [or non-use] of
> schema:startDate and schema:endDate.
>

Indeed, but the problem is that schema:startDate and schema:endDate don't
have CreativeWork in their Domain, while temporalCoverage does. Shouldn't
startDate and endDate apply to CreativeWork too, if we want to be
consistent ?

Thomas



>
> ~Richard.
>
>
>
> Richard Wallis
> Founder, Data Liberate
> http://dataliberate.com
> Linkedin: http://www.linkedin.com/in/richardwallis
> Twitter: @rjw
>
> On 14 September 2016 at 10:25, Thomas Francart <thomas.francart@sparna.fr>
> wrote:
>
>> Hello
>>
>> Is it allowed to have values for temporalCoverage that have an open end ?
>> i.e. only a start date, but no end date, or only an end date and no start
>> date ? My understanding of the ISO 8601 format is that this is not allowed,
>> but I would like to confirm.
>>
>> We need to be able to express a temporal coverage as an open interval in
>> the description of Legislation (https://github.com/schemaorg/
>> schemaorg/issues/1156), and though we could reuse that property, but we
>> can do it only if it allows open intervals (legislation currently
>> applicable or in force would have a start date, but no end date).
>>
>> Thanks
>> Thomas
>>
>> --
>>
>> *Thomas Francart* -* SPARNA*
>> Web de *données* | Architecture de l'*information* | Accès aux
>> *connaissances*
>> blog : blog.sparna.fr, site : sparna.fr, linkedin :
>> fr.linkedin.com/in/thomasfrancart
>> tel :  +33 (0)6.71.11.25.97, skype : francartthomas
>>
>
>


-- 

*Thomas Francart* -* SPARNA*
Web de *données* | Architecture de l'*information* | Accès aux
*connaissances*
blog : blog.sparna.fr, site : sparna.fr, linkedin :
fr.linkedin.com/in/thomasfrancart
tel :  +33 (0)6.71.11.25.97, skype : francartthomas
Received on Wednesday, 14 September 2016 10:34:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 14 September 2016 10:34:51 UTC