Activity

From 09/03/2003 to 10/02/2003

04:03 PM Bug #1155 (Resolved): Documentation incorrect for dateTimeDomainType bounds: within dateTimeDomainType (eg see
eml:eml/dataset/dataTable/attributeList/attribute/measurementScale/datetime/date
... Matthew Brooke
03:55 PM Bug #1154 (Resolved): All children of required "offline" element are optional in PhysicalDistributionType: in PhysicalDistributionType, the "offline" element is required, but all its
children are optional; thus if the user... Matthew Brooke

08:20 PM Bug #1153 (Resolved): dateTimeDomain element should be optional: Under
eml:eml/dataset/dataTable/attributeList/attribute/measurementScale/datetime,
there is a sequence of 3 require... Matthew Brooke
03:15 PM Bug #1152 (Resolved): datetime element does not use consistent naming: The datetime element in eml-attribute should be spelled dateTime to be
consistent with the other dateTime elements a... Chad Berkley
03:11 PM Bug #1151 (Resolved): misspelled element name: in eml-resource.xsd, the simpleType KeyTypCode should be spelled "KeyTypeCode"
(line 393) Chad Berkley
03:08 PM Bug #1150 (Resolved): documentation for KeyTypeCode is wrong: The documentation for KeywordType says that the allowed values in an element of
type KeyTypCode are "discipline", "s... Chad Berkley

06:31 PM Bug #1124: update precision field definition and cardinality: precision field under measurementScale/interval is currently shown as
repeatable (1..inf), but under measurementScal... Matthew Brooke
05:22 PM Bug #1149 (Resolved): BoundsGroup bounds min & max have incorrect cardinality: BoundsGroup bounds min & max have incorrect cardinality. This can be seen in the
following places:
NumericDomainT... Matthew Brooke

01:19 PM Bug #1008: inline element doesn't support character child: Used Dan's schema fragment to modify eml-resource.xsd. Created a new type called
InlineType. The inline element is no... David Blankman

Also available in: Atom

EML