I haven't, but I'd be inclined to use the <date> element, with the
'normal' attribute adhering to iso 8601, as in
yyyy-mm-ddThh:mm (e.g., 2004-09-30T18:30)
Two possible problems:
* If you're using a schema to validate 'normal' values, the
schema's pattern testing may not account for the time portion, and so
you would have a validation error.
* It's not clear whether a colon is allowed as an attribute value
for anything other than an XML namespace, so some validators/parsers
may complain.
It's permissible not to use the component separators in the date
value, according to 8601, but I think that option presents parsing
difficulties unless you know you have uniform date values.
Best,
Brian
On April 10, at 11:03 AM, Cruikshank, Kathleen A wrote:
> I'm working on a collection with lots of printed-out emails, many
> of them on the same day but at different times, and I'm feeling the
> need to indicate time as well as date in the finding aid. Has
> anyone dealt with this situation, and if so, how?
>
> Thanks.
>
>
>
> Kate Cruikshank
> Political Papers Specialist
> E460 Wells Library
> Indiana University
> Bloomington, IN 47405
> Tel. 812-856-4601
> [log in to unmask]
>
>
>
--------------------------------------------------
Brian Sheppard
University of Wisconsin Digital Collections Center
[log in to unmask] (608) 262-3349
|