Re: Requiring a date be entered as mm/dd/yy on a form field.
- From: Tim Harig <usernet@xxxxxxxxxx>
- Date: Thu, 02 Jul 2009 18:14:46 GMT
On 2009-07-02, Dr J R Stockton <reply0927@xxxxxxxxxxxxxxxxxx> wrote:
In microsoft.public.scripting.jscript message <svz2m.1952$bq1.556@nlpi06
6.nbdc.sbc.com>, Wed, 1 Jul 2009 02:05:12, Tim Harig
<usernet@xxxxxxxxxx> posted:
On 2009-06-30, Dr J R Stockton <reply0927@xxxxxxxxxxxxxxxxxx> wrote:Consider any code that validates the seconds part of an incoming time
In microsoft.public.scripting.jscript message <y4f2m.5910$iz2.2101@nlpi0Perhaps you would like to provide a solid example of such a catastrophic
70.nbdc.sbc.com>, Tue, 30 Jun 2009 02:51:10, Tim Harig
<usernet@xxxxxxxxxx> posted:
Users have the right to use whatever precision they like. The softwareMost users and coders are not really aware of Leap Seconds. Supplying
should be accurate enough to give them that precision or at properly
specify that they cannot calculate to that precision. Furthermore, UTC
is the recognized standard.
them with hours and minutes of different lengths will lead to more
significant error than being a fraction of a second different.
situation? Otherwise, coders that don't need such precision will simply
use whatever standard they are given.
with part-RegExp :[0-5]\d Coders will commonly expect a second
numbered 60 even less than they expect a day which does not contain 24
full hours.
As an edge case it will only be invalid only very infrequently, okay.
Why one would normally be validating seconds in most applications is
little extreme in and of itself. I have never as a user needed to enter
non-relative seconds into an application. Never as part of a date.
Presumably most second level code will be getting time information from the
system (ie Unix time from the epoch) or another application.
Also remember that this started as the basis for internal calculations
only. Input and output would could easily be converted to another time.
Remember that we are talking about multinationalizing here. Essentially we
are using UTC internally so that we may have a common means for converting
to the localized zone and format. Validation should not be needed for
internal calculations. For calculations in most langauges they would not
be in a text based format that could be verified with a regular expression
to begin with.
BIPM is an international authority situated in France.UTC is actually managed by a French authority.Of GMT, the NIST has this to sayMerely a local authority. You should be referring to an international
one.
Then you have answered you own question and provided an international
agency.
If you disagree with it, then perhaps you should provide examples of
organizations that oppose the use of a UTC standard in favor of a GMT
standard -- and not out of the mistaken confusion that they are the same.
Unless one supposes that they have not been informed or have failed to
understand, or have merely been slothful or uncaring : the UK
Legislature. Legal time here is GMT.
1. You have provided only a local organization vs. my local organization
and what you have provided as an international organization; but,
that is immaterial here.
2. I would bet that UK law only pertains to your inputs and outputs. I
very much doubt that they have any juristiction over the formats
used for your internal code. Which brings me to 3:
3. The discussion is about your internal code and multinationalization.
Once you have done your calculations you will presumably localize
them back to UT0 for the UK or PDT for locales in the western
hemisphere.
[ALSO]WhenTime zones do not have names, except in some locations. Some military
asked about time zones, users should be given names
use 25 of the letters A to Z, which must be somewhat limiting.
rather then just theLocal time offsets generally do have local names, but the names, and
time zone codes to choose from.
particularly the abbreviations, are not unique world-wide.
Most areas have some name that they use to refer to their timezone. It is
also a common convention to list some areas that fall under the timezone
for those who may not be clear what timezone they fall in by nomenclature.
For example, when setting one's timezone in the US, Microsoft Windows
lists three large cities within a timezone that fall under any given
timezone.
One country, however, will go to considerable lengths to eschew use of
anything like an international standard, probably not wanting to add to
the variety that it already has.
We are not a monoculture. We, unlike the UK, are a mixing pot of
many diverse nationalities. The native people are here a minority.
We have significant populations with ethnicities returning to Europe,
Asia, and Africa. Even among those there are undercurrents of differing
backgrounds. We do not have an official national language and our
inhabitants speak many. It is the habit that most other cultures tend
to remain close to their roots rather then totally assimilating into
what some people would associate with the cultural mainstream.
Everybody is as free as possible to keep and contribute the artifacts of
their background. We consider this to be one of our nations strengths that
we have so many people from diverse backgrounds with diverse experiences
that can help to see and help to solve problems from different perspectives.
The end result is that we have many separate standards and conventions.
On the other hand, it is a great example of multinationalism in action.
.
- Follow-Ups:
- References:
- Re: Requiring a date be entered as mm/dd/yy on a form field.
- From: Dr J R Stockton
- Re: Requiring a date be entered as mm/dd/yy on a form field.
- From: Tim Harig
- Re: Requiring a date be entered as mm/dd/yy on a form field.
- From: Dr J R Stockton
- Re: Requiring a date be entered as mm/dd/yy on a form field.
- Prev by Date: Re: Requiring a date be entered as mm/dd/yy on a form field.
- Next by Date: Re: formating javascript source
- Previous by thread: Re: Requiring a date be entered as mm/dd/yy on a form field.
- Next by thread: Re: Requiring a date be entered as mm/dd/yy on a form field.
- Index(es):
Relevant Pages
|
