LISTSERV mailing list manager LISTSERV 16.0

Help for DATETIME Archives


DATETIME Archives

DATETIME Archives


[email protected]


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  June 2011

DATETIME June 2011

Subject:

Re: A three level suggestion

From:

Bruce D'Arcus <[log in to unmask]>

Reply-To:

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

Date:

Mon, 6 Jun 2011 14:37:54 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (33 lines)

On Mon, Jun 6, 2011 at 2:08 PM, Ray Denenberg
<[log in to unmask]> wrote:
> From: Bruce D'Arcus
>> What's the basis on which level two and three features are distributed?
>
> "are" distributed or "would be" distrubuted?  At this point the distribution is just a suggestion, and comments are solicited.

The latter. E.g. what's the basic on which you made the strawman distinctions?

> Level 0 is straightforward: anything reatained in the spec that conforms to ISO 8601. (And I propose to eliminate the distinction of whether or not it is part of W3CDTF.)  And so those features retained that are not part of ISO 8601 would be distributed over levels 2 and 3, and the question is on what basis.  I see three factors: 1. difficulty of implementation; 2. need; 3. separability.
>
> By "separability" I mean that I think we would want the BNF to be three (somewhat) distinct sections (perhaps all referencing a common part) corresponding to the three levels.  Placing a feature in level 2 vs. level 3 (or vice versa) might make it easier (or more difficult) to achieve the desired separability.
>
> I plan to begin looking at the BNF in terms of the above, but I would appreciate input from implementers and users about which features should be level 2 and which should be level 3.

For our usecase (bibliographic citation formatting, data exchange,
etc.; Zotero, CSL, Mendeley kinds of use cases), we would probably end
up cherry-picking from levels 2 and 3. We're unlikely to support
anything but very general uncertainty, for example, and not things
like masks.

One way to slice the levels is how different feature diverge from the
base. For example, a standard range of "2002-02/2002-03" is not
supported by Level 0, but it's components are.

OTOH, 2002-0u has no reasonable approximation I can see in ISO 8601.

Perhaps that suggests they should go on different levels?

I don't know; just a question.

Bruce

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

March 2022
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