Project

General

Profile

Activity

From 03/22/2002 to 04/20/2002

04/20/2002

10:24 AM Bug #477 (Resolved): referencing complex types is not done consistently
In all modules we import other schemas and use components. Sometimes we define
elements that use a ComplexType, oth...
Matt Jones

04/19/2002

08:41 PM Bug #338: need coverage documentation, review all documentation
chris did this today. he also changed all of the tag names to be comprehnsible. Chad Berkley

04/18/2002

09:28 AM Bug #430: need DTDs to correspond to XSD files
added entities back into the dtds. they now correspond to the xsd files. Chad Berkley

04/17/2002

11:09 AM Bug #470: need to be able to inline data in EML
added the eml-data module. this module allows data to be inserted into the xml. if it is binary, it needs to be bas... Chad Berkley

04/16/2002

04:52 PM Bug #337: storage type issues
Chad. I will not get to this before I leave. Could you look into STMML and
come up with a strategy? Maybe have Chr...
Matt Jones
04:46 PM Bug #428: eml-constraint overlaps with packaging concepts
The issues here are the same that were just addressed in bug#427. See the
discussion there for details of the resolu...
Matt Jones
04:46 PM Bug #427: eml-constraint use of identifers
*** Bug 428 has been marked as a duplicate of this bug. *** Matt Jones
04:35 PM Bug #427: eml-constraint use of identifers
Clarified documentation in eml-constraint to indicate that the entities that
participate in the constraint should be ...
Matt Jones
04:41 PM Bug #335: decompose eml identifiers into familyid and revision
Resolving this bug as WONTFIX based on the comments I made previously in the
bug. At a minimum this request would no...
Matt Jones
04:37 PM Bug #269: resolve packaging issues
FIXED. Existing "eml" wrapper module to be incorporated into the beta7 release. Matt Jones
10:09 AM Bug #472 (Resolved): establish consistent namespaces for schemas
EML currently uses namespaces of the form "eml:modulename" for each of the eml
modules (e.g., eml:dataset). In cont...
Matt Jones

04/15/2002

10:41 PM Bug #471 (Resolved): eml spec overview document
Need an overview document that gives the background and rationale for eml. This
would likely have both normative an...
Matt Jones
05:09 PM Bug #335: decompose eml identifiers into familyid and revision
After putting a lot of thought into this issue, mu conclusion is that we should
NOT make these changes to the "identi...
Matt Jones
04:45 PM Bug #269: resolve packaging issues
Created a new module "eml.xsd" that allows us to wrap up multiple eml modules
(and other metadata) into a single XML ...
Matt Jones
04:12 PM Bug #337: storage type issues
Possibly use STMML as a value contsraint for the value space for dataTypes.
Thus, it would be based on XML Datatypes...
Matt Jones
03:47 PM Bug #470 (Resolved): need to be able to inline data in EML
Request to be able to inline data in the same file as EML. For binary data,
this could be Base64 encoded. For text...
Matt Jones

04/11/2002

09:35 AM Bug #249: Update XSLT stylesheets for EML 2.0 modules
OK, partially did the eml-entity and eml-attribute stylesheets for marine. Need
to put together the rest.
Matt Jones

04/05/2002

08:11 AM Bug #450: entityType and format
added additional documentation to make these fields unambiguous. Chad Berkley

03/27/2002

10:27 AM Bug #450 (Resolved): entityType and format
The eml-entity module has a field called "entityType" that is supposed to
contain the type of the entity for "other"...
Matt Jones

03/22/2002

12:47 PM Bug #427: eml-constraint use of identifers
In looking at this issue, I think the best way to handle this would be to split eml-attribute up into multiple files.... Chad Berkley
11:04 AM Bug #443: revise duration elements in eml-access
duration and ticket count are now removed Chad Berkley
12:54 AM Bug #443: revise duration elements in eml-access
I think it is reasonable to possibly eliminate advanced features like duration
and ticketCount from eml-access for no...
Matt Jones
10:59 AM Bug #339: bounding box vs point data in eml-coverage
made westbc and southbc optional so now if you want to define a single point, you can just use northbc and eastbc. Chad Berkley
 

Also available in: Atom