Activity
From 10/25/2003 to 11/23/2003
11/06/2003
- 12:28 PM Bug #1195: tracking bug for 2.0.1 release
- 6) Also need to validate that the inline element now accepts the right kind of
content, probably by writing a new tes... - 12:26 PM Bug #1195: tracking bug for 2.0.1 release
- Finished (1) (revise namespaces)
Finished (2) (revise README)
Still need to do (3), (4), and (5) - 12:24 PM Bug #1149: BoundsGroup bounds min & max have incorrect cardinality
- Checked on the bounds model -- turns out that the model I proposed before is not
deterministic according to XML (with...
10/31/2003
- 09:17 AM Bug #1197 (New): dictionary needed for externallyDefinedFormat
- Externally defined format is useless for automatic processing unless you have
some idea what to look for. This is a...
10/30/2003
- 03:59 PM Bug #1149: BoundsGroup bounds min & max have incorrect cardinality
- When running the tests I found that this content model is rejected. Maybe its
because it is not deterministic accord...
10/28/2003
- 02:53 PM Bug #1195 (Resolved): tracking bug for 2.0.1 release
- This bug lists all remaining housekeeping issues to be resolved before the EML
2.0.1 release can be distributed. Pl... - 02:48 PM Bug #1154: All children of required "offline" element are optional in PhysicalDistributionType
- Cleaned up documentation for offline medium some, but I am not comfortable with
making mediumName required, because t... - 02:41 PM Bug #1151: misspelled element name
- FIXED.
- 02:40 PM Bug #1151: misspelled element name
- Renamed this simple type name so that it is spelled correctly. As it does not
actually correspnd to an element name ... - 02:39 PM Bug #1150: documentation for KeyTypeCode is wrong
- Fixed documentation, making the lists of types match, and provided full
documentation for each of the KeyTypeCode val... - 12:39 PM Bug #1155: Documentation incorrect for dateTimeDomainType bounds
- Created a new group called BoundsDateGroup that allows the documentation and
model to be different for date bounds th... - 12:38 PM Bug #1153: dateTimeDomain element should be optional
- Made the dateTimeDomain element optional. Note that this is fine for
dateTimeDomain because bounds is optional and t... - 12:36 PM Bug #1149: BoundsGroup bounds min & max have incorrect cardinality
- Changed the content model to fix this problem. Now the model allows either
minimum, maximum, or both, as described i... - 10:06 AM Bug #1152: datetime element does not use consistent naming
- This is a relatively minor issue, and I think that it is not worth breaking
backwards compatibility to fix it. I'm r... - 10:02 AM Bug #1124: update precision field definition and cardinality
- Resolved. Proposed changes have been checked into cvs for precision field.
10/27/2003
- 10:21 AM Bug #1193 (New): Temporal Description Missing?
- A temporal description field is not currently available. Should a temporal
description field (paragraph format) be ...
Also available in: Atom