Date:         Wed, 12 May 2004 08:53:32 -0400
Reply-To:     Metadata Object Description Schema List <[log in to unmask]>
Sender:       Metadata Object Description Schema List <[log in to unmask]>
From:         Bruce D'Arcus <[log in to unmask]>
Subject:      Re: other dates coding
Comments: To: Metadata Object Description Schema List <[log in to unmask]>
In-Reply-To:  <[log in to unmask]>
Content-Type: text/plain; charset=US-ASCII; format=flowed

On May 12, 2004, at 8:13 AM, nigel kerr wrote:

> One approach is to make use of a scheme such as the OpenURL standard
> uses: see
> http://library.caltech.edu/openurl/Standard.htm, specifically the
> Initial Registry Content
> document, section 8.1 "Key/Encoded-Value Metadata Format to Describe
> Journals".

Karen Coyle had mentioned one coding (I forget which) where you have
something like 2003-44.  That's an option, but there's no way to
indicate this encoding currently.

In any case, I guess this raises two questions:

1)  Is there any clever way to code this in MODS now?  I was thinking
of maybe:

        <dateIssued encoding="w3cdtf">1999</dateIssued>
        <dateIssued>Winter</dateIssued>

2)  Could MODS use a minor change here or there (for example, an
additional data encoding option?)?

Bruce