[Bug 654] - scope of the unit element
bugzilla-daemon@ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Fri Oct 25 10:36:56 PDT 2002
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=654
jones at nceas.ucsb.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eml-dev at ecoinformatics.org
Status|NEW |ASSIGNED
------- Additional Comments From jones at nceas.ucsb.edu 2002-10-25 10:36 -------
Peter,
Thanks for the excellent summary. I think I agree with this approach, excpet
for one point: the "library" attribute. In general I think it is crucial that we
have the STMML unit definitions available with the metadata. Consequently, I
don't think it is appropriate to define units in stmml in an external location
-- they should either be 1) directly in the EML document (additionalMetadata or
elsewhere), or 2) should be well-known (meaning, shipped with and defined as
implicit to EML itself), as we are doing with the current unitDictionary.
The changes we've proposed in this bug affect the schemas and instance
documents, but I think it is critical to get this domain/unit/measurementScale
stuff worked out in a logical way for the EML 2 release. This is precisely why
we had a review of the RC1 and RC2 releases -- to catch fatal flaws like this.
Adn I do think this stuff is fatally flawed as it now stands. People would
complain once they tried to really use it.
More information about the Eml-dev
mailing list