Re: [VCARDDAV] New Date Range Proposal

[Markus Lorenz <[e-mail]>]

Am 13.10.2010 06:03, schrieb Renato Iannella:
> 
> I am proposing to add a new EFFECTIVE-DATES Property Parameter to vCard to support the need to indicate that some vCard Properties were effective over a certain fixed time period. (Otherwise, all properties are considered to be current).
> 
> STEP 1 - Add new DATE-RANGE Property Value Data Type
> ===========================
> 
> 4.3.6.  DATE-RANGE
> 
>  A complete representations of time intervals identified by start and end as specified in [ISO.8601.2004] section 4.4.4.
> 
>  Representations (for Date and Time) with reduced accuracy are allowed.
> 
>  Examples for "date-range":
> 
>     2000-01-25T12:30:00/2005-02-25T12:30:00
>     2000-01-25/2005-02-25
>     2000-01/2005-02
>     2000/2005

What about a formal description like:

   date-range = date-and-or-time "/" date-and-or-time

   date-range-list = date-range *("," date-range)

I'm not sure if "date-and-or-time" is the best solution, as it would
allow values with only time and no date. But at the moment I couldn't
think of a reason not to allow that. It shouldn't be the problem of the
vCard format whether or not a given date-range is meaningful.

With "date-range-list" we're quite near to being able to define business
hours for work phone numbers. We'd only have to introduce weekdays.
Don't know if anyone would like that. I guess this information could
already be included in the iCalendar to which FBURL points. At least for
the whole vCard and not a specific communications property.

Please use examples that show that both values don't have to have the
same date-and-or-time format. The examples should show a possible
difference between the first and the second value:

     2000-01-25T12:30:00/2005-02-25T12:30:00
     2000-01-25T123000+0200/2005-02-25            ; <==
     2000-01-25/2005-02-25
     2000/2005-02-25                              ; <==
     2000-01/2005-02
     2000/2005

Another thing I just saw: The examples for TIME, DATE-TIME,
DATE-AND-OR-TIME and TIMESTAMP in sections 4.3.2 to 4.3.5 never use
colons. I don't have access to ISO 8601:2004, but doesn't it allow
colons in time values?

Regards


Markus