Re: validThrough and validUntil

I agree that different parties use these terminal dates differently in
various contexts.  It matters especially with month-defined dates.

When does my credit card expire?  At the end of the month, or the
beginning?  "Expiry date" is rather vague.

I would personally like only one property for consistency, but the reality
of usage in practice is that both kinds are utilized.  So both should be
global properties (not just one for Permits).



On Tue, Aug 7, 2018 at 7:34 PM, Thad Guidry <thadguidry@gmail.com> wrote:

> I strongly feel we should keep both.
>
> The reasoning behind this is that the data could be inclusive or exclusive
> of a Day if the Time component is not provided.  Governments and business
> might use either form, and its useful to know if something will cease being
> valid at the end of a day (validThrough) or at the beginning of a new day
> or some end time (validUntil).  I deal with this kind of distinction daily
> and I already have buckets for both forms in my workflows.  Knowing to send
> a message at the beginning of a day or towards the end for Contract renewal
> purposes.  Speaking of which, Contracts take both forms as well, and we
> haven't put work into Contracts much yet, so even more reason to keep
> both.  Insurance is another domain where processors are very picky with
> clarity of something being validUntil (I've seen Insurance contracts
> specify the validUntil using the last second in an hour for exactness).
> --
>
> Thad
> +ThadGuidry <https://plus.google.com/+ThadGuidry>
>