http://www.pbcore.org Public Broadcasting Metadata Dictionary Project Sat, 19 Nov 2011 15:23:52 +0000 hourly 1 http://wordpress.org/?v=3.0.4 http://www.pbcore.org/v2/attributes/datetype/comment-page-1/#comment-465 Peter Pinch Sat, 19 Nov 2011 15:23:52 +0000 http://pbcore.org/#comment-465 Often, in real world cataloging scenarios, it's impossible to know the meaning of a date associated with an item -- imagine a collection of tapes inside a box with a date written on it. Although you may question the value of even recording that date, we've learned that many catalogers believe this data is worth capturing. Often, in real world cataloging scenarios, it’s impossible to know the meaning of a date associated with an item — imagine a collection of tapes inside a box with a date written on it. Although you may question the value of even recording that date, we’ve learned that many catalogers believe this data is worth capturing.

]]> http://www.pbcore.org/v2/attributes/datetype/comment-page-1/#comment-296 Nino Gabrielli Tue, 26 Jul 2011 22:36:19 +0000 http://pbcore.org/#comment-296 It seems to me that this attribute should be mandatory in many cases to avoid ambiguity: pbcoreAssetDate is a good example for that. As long as this element describes a date of creation or representation or "other types of dates associated with an asset", shouldn't it be specified what the date refers to? It seems to me that this attribute should be mandatory in many cases to avoid ambiguity: pbcoreAssetDate is a good example for that. As long as this element describes a date of creation or representation or “other types of dates associated with an asset”, shouldn’t it be specified what the date refers to?

]]>