LISTSERV mailing list manager LISTSERV 16.0

Help for DATETIME Archives


DATETIME Archives

DATETIME Archives


DATETIME@C4VLPLISTSERV01.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

DATETIME Home

DATETIME Home

DATETIME  January 2011

DATETIME January 2011

Subject:

Re: dual representations

From:

"C. M. Sperberg-McQueen" <[log in to unmask]>

Reply-To:

Discussion of the Developing Date/Time Standards <[log in to unmask]>

Date:

Fri, 21 Jan 2011 22:28:08 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

On Jan 20, 2011, at 4:46 AM, Edward C. Zimmermann wrote:
>>
>
> ISO 8601 is, in fact, a standard format for user input.

That's an interesting point of view. The last time I read that
spec, though, I remember it making an explicit statement
that as far as the WG knew the format was not a common
culturally expected format in any language, culture, or locale,
and regarding this as an advantage in that it did not favor
or appear to favor any one cultural practice over another.

So if you mean that ISO 8601 is intended to serve as a way
to make sense of input from general or untrained users, I
think the historical facts of the matter are against you.

If you only mean that it's a text format and thus typable, then of
course you're quite right, but the observation is perhaps less
compelling. A date format using integers counting the number
of days since the death of Julius Caesar (or any other epoch)
is also a text format and readily typable; would anyone say
it's a format for user input?

It's quite true that many formats designed and specified for
interchange may prove to be suitable for input from at least
some users; I know a few technically oriented people
who have acquired the habit of using ISO 8601 dates in
their daily life because they like the format.

But designing a format to accept and handle unstructured
input from users who are not trained in the details of the format,
and designing a format for interchange among software
systems which may be expected to do some validation of
their input are (in my experience at least) two rather different
activities. Most obviously, in most data interchange applications,
it's usually regarded as preferable to eliminate as much
variation as possible in formats: if there is no difference in
meaning between "2011-01-21" and "20110121", people
interested solely in the exchange of data among databases
will (again, in my experience) unanimously prefer to choose
one of these formats and require it, rather than allowing
either. That seems good practice to me.

 

--
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com
* http://cmsmcq.com/mib
* http://balisage.net
****************************************************************

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

August 2019
February 2019
December 2018
November 2018
October 2018
January 2018
August 2017
July 2017
June 2017
April 2017
March 2017
February 2017
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
December 2014
November 2014
March 2014
September 2013
May 2013
February 2013
October 2012
September 2012
August 2012
May 2012
March 2012
December 2011
November 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
February 2010
January 2010
December 2009
November 2009

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager