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

DATETIME March 2011

Subject:

Sv: [DATETIME] Last Call for Use Cases

From:

Karin Bredenberg <[log in to unmask]>

Reply-To:

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

Date:

Mon, 7 Mar 2011 16:26:49 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (122 lines)

Hi all,

Some comments in the text marked with Karin.

But also a question:
Cant find and may have missed, if something is undated and is stated to
be undated how to express that?

One comment about the "T" when you have date and time:
When you make a string of current date and time using C# it ends uplike
this: <date>2011-02-28 15:34:08</date> so there are no T present. So
perhaps both options should be availible.

One extra comment:
Most often we use both date and time not just time so not sure about
the use of only time. Can perhaps occur in an export from an RMS but not
sure.






Hälsningar/Regards
Karin Bredenberg
 
***************************************************************
Karin Bredenberg
Programmerare /Programmer
Riksarkivet/Swedish National Archives
IT-avdelningen/IT department
P.O. Box 12541, SE-102 29 Stockholm, Sweden
tel + 46(0)10-476 71 23
SMS + 46(0)70-349 74 55
www.riksarkivet.se


>>> "Denenberg, Ray" <[log in to unmask]> 2011-03-03 17:33 >>>
I am working on a fairly extensive revision to the draft specification,
http://www.loc.gov/standards/datetime/spec.html, attempting to
consolidate the discussion of the past month or two. I plan to complete
this by next Friday, March 11.



As part of this process, I am issuing a LAST CALL on the following
features. We need a concrete use case for each of these. For each of
the following, if no use case is provided, the feature will be dropped.



* #104 Month and day. e.g. --01-31 (January 31 of unspecified
year)

* #106 month. e.g. --12 (december of unspecified year)

* #107 day. e.g. ---04 (4th day of unspecified month)

* #110 time e.g. 22:22:20 (time with unspecified date)

* #204 Ordinal day e.g. 003 (January 3, unspecified year)

* #205 Year and ordinal day 2003-003 (January 3 of 2003)

The need for this representation is questioned because January 3 of
2003 can be represented as 2003-01-03. A use case is needed
illustration why this alternative form is required.

* #206 Calendar week e.g. 1985W15 (week 15 of 1985)

* #207 Week Date e.g. 1985W155 (week 15, day 5, of 1985)

Note: the above four are distinct from issues of publication patterns
like for example "third Monday in February".

* #319 Interval: alternative form e.g. 1964--2008 to means the
same thing as 1964/2008 (double dash syntax used in place of slash.)
 Karin: Here in Sweden its a tradition when you write an archival
description and are making an interval to use the double dash and even
the single dash is sometimes used. But when you state the normalization
you use the slash.

Example one from the ead-homepage
(http://www.loc.gov/ead/tglib/elements/unitdate.html):
<unitdate type="inclusive" normal="1952/1964">1952-1964</unitdate>

Example two from the swedish description
(http://xml.ra.se/ead/ARKIS_EAD_07.pdf page 6):
<unitdate certainty="[X]" type=”[X]”>[YYYY]--[YYYY]</unitdate>

Example three from a swedish export of an archival description:
<unitdate type="inclusive">1595--1999</unitdate>

Example four from an swedish archival description transformed to an
APEnet archival description with normalization (APEnet is an archival
portal for Europe):
<unitdate calendar="gregorian" era="ce" normal="1526/1813"
encodinganalog="3.1.3">1526--1813</unitdate>


* #323 The endpoint of an interval is another interval

* #324 duration within an interval

* #325 Named period or event as the endpoint of an interval

* #328 extension times
Karin: At some workplaces here like when you are a busdriver you can
have a shift endtime at 26:00:00 meaning that your shift ends at 2:00
in the morning. This to say that its still part of the day before when
you make the schemas for rhe drivers. But thats the only usecase I have
seen.




This LAST CALL FOR USE CASES is through next Thursday, March 10.



--Ray

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