LISTSERV mailing list manager LISTSERV 16.0

Help for PIG Archives


PIG Archives

PIG Archives


PIG@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

PIG Home

PIG Home

PIG  June 2006

PIG June 2006

Subject:

Re: dates for rights

From:

"Rebecca S. Guenther" <[log in to unmask]>

Reply-To:

PREMIS Implementors Group Forum <[log in to unmask]>

Date:

Mon, 19 Jun 2006 14:43:06 -0400

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (80 lines)

ISO 8601 has limited ability to express a lot of types of dates,
especially some needed for cultural heritage objects, like those that are
questionable, approximate, etc. Perhaps we should come up with some PREMIS
conventions. I looked at this a few years ago in the context of some
Dublin Core work and could dig up my notes if needed on the limitations of
8601. There has been little consensus on conventions for these kinds of
uncertain dates. So it may be prudent to establish some for PREMIS perhaps
based on what other efforts may be using.

Rebecca

On Fri, 16 Jun 2006, Matthew Beacom wrote:

> Hello,
> 
> It may be that one simply can't use ISO 8601: 2004 this way.  Using 
> 9999 and 0000 to represent not "dates in the Gregorian calendar" but 
> rather a quality of open-endedness with respect to an end date or a 
> start date is logically outside of the domain of ISO 8601.  Anything 
> we do would be a kluge.
> 
> 9999 may not be the best value to mean "forever" as it would also 
> mean the year 9999. A bit far off to worry about, of course. And OOOO 
> would mean 1 BCE (or be illegal) as there is no year 0 between the 
> first year of the common era (1 CE) and the last year prior to the 
> 1st year of the CE (1 BCE).
> 
> I think, though, that 0000 is not needed since a way to represent the 
> open-endedness of a start date is not needed. The rights related to 
> the object can't pre-date the object itself.  So One can simply use a 
> practical (albeit) arbitrary start date such as the date of the 
> creation of the digital object or, if necessary, the date of the 
> original object for which the digital copy is a proxy.
> 
> And then--for about 8000 years anyway--9999 may work perfectly well 
> being used to mean endless. But, of course, that would be a 
> non-standard use of 9999.
> 
> Matthew Beacom
> 
> p.s. below is the abstract for ISO 8601: 2004 from
> http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=40874&ICS1=1&ICS2=140&ICS3=30
> 
> ISO 8601:2004 is applicable whenever representation of dates in the 
> Gregorian calendar, times in the 24-hour timekeeping system, time 
> intervals and recurring time intervals or of the formats of these 
> representations are included in information interchange. It includes
>     * calendar dates expressed in terms of calendar year, calendar 
> month and calendar day of the month;
>     * ordinal dates expressed in terms of calendar year and calendar 
> day of the year;
>     * week dates expressed in terms of calendar year, calendar week 
> number and calendar day of the week;
>     * local time based upon the 24-hour timekeeping system;
>     * Coordinated Universal Time of day;
>     * local time and the difference from Coordinated Universal Time;
>     * combination of date and time of day;
>     * time intervals;
>     * recurring time intervals.
> ISO 8601:2004 does not cover dates and times where words are used in 
> the representation and dates and times where characters are not used 
> in the representation.
> 
> ISO 8601:2004 does not assign any particular meaning or 
> interpretation to any data element that uses representations in 
> accordance with ISO 8601:2004. Such meaning will be determined by the 
> context of the application.
> 
> Matthew Beacom
> 
> Metadata Librarian
> Yale University Library
> 130 Wall Street P.O. Box 208240
> New Haven, CT 06520-8240
> 
> phone: (203) 432-4947
> fax: (203) 432 7231
> e-mail: [log in to unmask]
> 

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

April 2021
March 2021
January 2021
December 2020
September 2020
August 2020
July 2020
June 2020
April 2020
February 2020
December 2019
November 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 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
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager