Open caseyedavis12 opened 10 years ago
Is this pattern you've seen used before? The term "normal" seems misleading. I would make the date repeatable and specify an encoding:
<pbcoreAssetDate datetype="broadcast">April 23, 1988.</pbcoreAssetDate>
<pbcoreAssetDate datetype="broadcast" encoding="ISO8601">19880423</pbcoreAssetDate>
Update: OK, I see this is EAD based.
Maybe a dateType element field (nested elements), with source, ref, version, annotation attributes, could be used to also hold an encoding schema?
However, I think that. PBCore/Dublic Core coverage can be used for "normal" style dates, keeping assetDate ISO8601 as a default rule.
On Fri, Aug 1, 2014 at 9:52 AM, Adam Wead notifications@github.com wrote:
Is this pattern you've seen used before? The term "normal" seems misleading. I would make the date repeatable and specify an encoding:
April 23, 1988. 19880423 — Reply to this email directly or view it on GitHub https://github.com/WGBH/PBCore2.0/issues/58#issuecomment-50893162.
Yes, the Encoded Archival Description (EAD) schema has a @normal attribute for dates. It provides a consistent format of the date as an attribute and allows for the value of the element to be presented to researchers in any format. I prefer this instead of requiring pbcore users to format the value of the pbcoreAssetDate element as "19880423." You can put data in any format in the value of the element as long as you qualify it in the attributes.
We could do
<pbcoreAssetDate datetype="broadcast" encoding="ISO8601" normal="19880423" certainty="approximate">April 23, 1988</pbcoreAssetDate>
From: Adam Wead notifications@github.com<mailto:notifications@github.com> Reply-To: "WGBH/PBCore2.0" reply@reply.github.com<mailto:reply@reply.github.com> Date: Friday, August 1, 2014 10:52 AM To: "WGBH/PBCore2.0" PBCore2.0@noreply.github.com<mailto:PBCore2.0@noreply.github.com> Cc: Casey Davis casey_davis@wgbh.org<mailto:casey_davis@wgbh.org> Subject: Re: [PBCore2.0] Attribute @normal for pbcoreAssetDate (#58)
Is this pattern you've seen used before? The term "normal" seems misleading. I would make the date repeatable and specify an encoding:
— Reply to this email directly or view it on GitHubhttps://github.com/WGBH/PBCore2.0/issues/58#issuecomment-50893162.
I suggest a new attribute for pbcoreAssetDate: @normal
This will provide a consistent format of the date, following iso 8601, which can then be represented differently in the element value.