[kepler-dev] [Bug 4942] KarXmlGenerator generated a invalid kar xml if KarEntry has dependsOnModule element

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4942

--- Comment #9 from Jing Tao <tao at nceas.ucsb.edu> 2010-04-20 14:03:09 PDT ---
Here is an email from Aaron:

Hi Jing, I was thinking about this a bit and I think option 1 is the way to go.
 The KAREntryHandler mechanism allows any attribute
to be added to a KAREntry so the KARXML file will reflect that and should
validate when it does.  Since the required attributes like
lsid are enforced in the KARFile mechanism it is OK not to enforce it in the
schema but we still need to allow any attribute to exist
there.  A new KAREntryHandler that is developed with a new module may want to
add an attribute that is not in the option 2 schema and
the developer shouldn't need to know about the customAttribute to add
attributes to the Manifest (and by consequence the KARXML).  So
I'd recommend option 1 for best compatibility if I'm understanding the schema
correctly.

Aaron


Since Aaron is the person who is working on this part, i will go with option 1:

<xs:complexType name="karEntryType">
    <xs:sequence>
       <xs:element name="karEntryAttributes" type="xs:anyType"/>
       <xs:element name="karEntryXML" type="xs:anyType" />
     </xs:sequence>
</xs:complexType>

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.