Activity

From 05/31/2006 to 06/29/2006

12:24 PM Bug #2054: use of <any> in additionalMetadata is invalid: My intention was that you would follow the schema outlined under Comment #4 which preserves the ability to have multi... Matt Jones
12:11 PM Bug #2054: use of <any> in additionalMetadata is invalid: Closing Comment on bug #2479 was the following:
"The workaround for the time being until a new version of EML is rel... John Cree
08:39 AM Bug #2480: Multiple date ranges in temporalCoverage: An explanation of multiple date range handling was given. It is done via multiple coverage elements. John Cree

11:10 AM Bug #2479: unable to validate eml.xsd and related schemas with XML*Spy and related suite of products: Yes, this is an existing, known issue that is currently being tracked in bug #2054. The EML schema is invalid, and c... Matt Jones
09:54 AM Bug #2479 (Resolved): unable to validate eml.xsd and related schemas with XML*Spy and related suite of products: As per question 10. in the FAQ's
"How can I get my existing metadata into EML?" ... "Case 3: If your metadata is al... John Cree
11:10 AM Bug #2054: use of <any> in additionalMetadata is invalid: *** Bug 2479 has been marked as a duplicate of this bug. *** Matt Jones
10:27 AM Bug #2480: Multiple date ranges in temporalCoverage: Thanks Matt. I overlooked that the entire coverage was repeatable.
Is there an equivalence for the Status fields fr... John Cree
10:19 AM Bug #2480: Multiple date ranges in temporalCoverage: In EML you can specify multiple, dicontiguous time periods by repeating the coverage element. No need to have two se... Matt Jones
10:06 AM Bug #2480 (Resolved): Multiple date ranges in temporalCoverage: If an information holding being described covers 2 or more widely separated time periods, e.g. 1980-1990 and 1995 to ... John Cree

Also available in: Atom

EML