[eml-dev] [Bug 2479] New: - unable to validate eml.xsd and related schemas with XML*Spy and related suite of products
bugzilla-daemon@ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Wed Jun 28 09:54:33 PDT 2006
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2479
Summary: unable to validate eml.xsd and related schemas with
XML*Spy and related suite of products
Product: EML
Version: 2.0.1
Platform: PC
OS/Version: All
Status: NEW
Severity: blocker
Priority: P2
Component: eml - general bugs
AssignedTo: jones at nceas.ucsb.edu
ReportedBy: john.cree at ec.gc.ca
QAContact: eml-dev at ecoinformatics.org
As per question 10. in the FAQ's
"How can I get my existing metadata into EML?" ... "Case 3: If your metadata
is already in XML but in some other form such as NBII or FGDC use the following
conversion method..." The suggested method is to write an XSLT script to do the
conversion. Although this may be possible, I am trying to save some time by
using an Altova product (Mapforce) to do the conversion. It will essentially
create the XSLT to do the conversion; however, it will only work with valid
schema definitions or DTD's as input and output. There is no problem using the
NBII DTD as input or output, however there are many errors when trying to
validate the EML schemas. Is this a problem that has been observed by others
that is occuring only with the validation done using Altova products, or is the
problem with the eml schema definitions themselves?
More information about the Eml-dev
mailing list