[kepler-dev] Make element karEntryXML optional
Benjamin Leinfelder
leinfelder at nceas.ucsb.edu
Tue Apr 20 19:02:37 PDT 2010
This is very true - kar entries need not be XML. Definitely change the
schema.
On Apr 20, 2010, at 5:35 PM, Jing Tao <tao at nceas.ucsb.edu> wrote:
> Hi, devs:
>
> Under current kar xml schema, both karEntryAttributes and
> karEntryXML is requried:
> <xs:complexType name="karEntryType">
> <xs:sequence>
> <xs:element name="karEntryAttributes" type="xs:anyType"/>
> <xs:element name="karEntryXML" type="xs:anyType" />
> </xs:sequence>
> </xs:complexType>
>
> When i tried to upload a workflow run from tpc09-plant-dynamics-
> woody.kar to a remote server, I got an invalid kar xml exception.
> Derik helped me to identify that one of karEntry elements doesn't
> have a child named karEntryXML. This kar entry is a pdf file. So
> there is no xml assoicated with it.
>
> Since kar entry is not necessary in xml format, I think karEntryXML
> elment should be optional. If there is no objection, i will change
> the schema.
>
> Thanks,
>
> Jing
>
>
> Jing Tao
> National Center for Ecological
> Analysis and Synthesis (NCEAS)
> 735 State St. Suite 204
> Santa Barbara, CA 93101
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
More information about the Kepler-dev
mailing list