Activity
From 03/09/2005 to 04/07/2005
03/31/2005
- 02:28 PM Bug #2054: use of <any> in additionalMetadata is invalid
- Matt's suggestion to create a <metadata> element seems OK to me - it's just as
easy as any of the others to retrofit ... - 02:08 PM Bug #2054: use of <any> in additionalMetadata is invalid
- I don't know how many use this feature, but the design was specifically done
that way to allow one metadata snippet t... - 02:00 PM Bug #2054: use of <any> in additionalMetadata is invalid
- addendum to Sid's comment #1
Currently, it's the eml-access documentation that shows multiple describes, and
it's not... - 12:24 PM Bug #2054: use of <any> in additionalMetadata is invalid
- <additionalMetadata> is already unbounded though so making <describes>
required and solo seems the best option. Woul... - 12:10 PM Bug #2054: use of <any> in additionalMetadata is invalid
Actually 1 might not be best choice as Margaret told me that EML best practices
document recommends using multiple ...- 12:03 PM Bug #2054 (Resolved): use of <any> in additionalMetadata is invalid
- Johnoel from Hawaii also reported the same problem which Margaret reported
earlier while using latest version of XM...
03/18/2005
- 04:15 PM Bug #2048 (New): param attributeindex defined twice in eml-settings.xsl
- Johnoel reported this. attributeindex is defined twice in eml-settings.xsl.
Seems like a typo.
Also available in: Atom