- From: Philip Ashlock - XI <philip.ashlock@gsa.gov>
- Date: Tue, 10 Jun 2014 12:18:50 -0400
- To: Richard Cyganiak <richard@cyganiak.de>
- Cc: public-gld-comments <public-gld-comments@w3.org>
Received on Tuesday, 10 June 2014 16:19:37 UTC
So are you saying an 8601 formatted recurring date would fit within the range of dctype:Frequency but only if it didn't include a start or end date? The requirement is both to express other frequencies than cld:Frequency as well as more precise times. On Tue, Jun 10, 2014 at 7:29 AM, Richard Cyganiak <richard@cyganiak.de> wrote: > Hi Philip, > > On 9 Jun 2014, at 23:22, Philip Ashlock - XI <philip.ashlock@gsa.gov> > wrote: > > > As far as I can tell accrualPeriodicity is limited to the predefined > terms for frequency http://dublincore.org/groups/collections/frequency/ > > I don’t think that’s the case. The range of dcterms:accrualPeriodicity is > dctype:Frequency. It doesn’t follow that values are limited to > cld:Frequency. > > (However, I do agree that a recurring interval with a start date is out of > range for dctype:Frequency.) > > > Are there any existing terms that could be used in place of > accrualPeriodicity using 8601 recurring interval syntax for more > flexibility? > > I’m not aware of anything suitable. > > What is the requirement here? Express other frequencies besides those in > cld:Frequency? Or express the precise time (e.g., not just monthly, but > monthly on the 10th)? > > Best, > Richard -- Philip Ashlock Chief Architect, Data.gov U.S. General Services Administration
Received on Tuesday, 10 June 2014 16:19:37 UTC