On Wed, Nov 17, 2010 at 10:28 AM, John Hostage <[log in to unmask]> wrote:
> The MARC 21 Format for Holdings Data has dealt with some of these issues before (
> It uses 21-24 for the seasons, starting with spring, in conjunction with a language code in holdings field 008.  Even in English, there is the difficulty of having 2 words for the same season (autumn/fall), which makes round-trip conversions fuzzy.  The MARC format tries to allow for publication patterns to predict future issues and has the possibility to spell out which issues are published in field 853 $y.  For example, "ps21,22,23,24" would indicate "published in the seasons spring, summer, etc."  The rules are not spelled out very clearly and it all depends on implementation in various library systems.  In some interpretations, the order could be varied for a southern hemisphere publication, e.g. "ps23,24,21,22", but the format is not clear on whether this pattern should correspond to the volume number or the calendar year.  (The time when the volume number increases is handled in 853 $x; some publications change the vol. number in the middle of the year.)
> Any format is going to have difficulty with the fact that astronomical winter (or summer in the southern hemisphere) straddles two calendar years and is geographically determined.  Publishers can be lax about how they interpret this.  One may say winter 2010/2011 one year and winter 2012 the next.
> For the format under discussion, it would seem that it depends on what you're trying to achieve.  To say the use case is periodicals is too vague.  What is to be done with them?

OK, real concrete:

I am:

1. the creator of the Citation Style Language (CSL), and
2. the co-creator of the BIBO RDF ontology

1 is explicitly aimed at formatting citations and reference lists for
localized output, while 2 is one particular metadata description that
might be used as input for 1.

So I need a way to describe the cover date for a periodical issue in
ways facilitate two things:

1. sorting a bibliography reliably by date (vis-avis other entries
that may have a month date)
2. printing the date in proper, localized, form (e.g. "Summer" would
render as "Verano" in Spanish)


> If you just want to encode how they designate themselves, that should be straightforward, though the infinite variety of designations and patterns can be mind-boggling.  If you want to be able to predict issues based on a pattern, that gets trickier.
> -----------------------------------------------------------
> John Hostage                  Authorities and Database Integrity Librarian
> Langdell Hall                 [log in to unmask]
> Harvard Law School Library    +(1)(617) 495-3974 (voice)
> Cambridge, MA 02138           +(1)(617) 496-4409 (fax)