Christopher Smith wrote:
Hi all,
Given the text in the bes specification (v26), the type of the elements within ActivityStatusType should not be xsd:anyType, but should use the definitions as follows. This is in line with the extensible state model as described in the specification:
The difference being the ##other namespace, right? Otherwise I think they're functionally equivalent.
<xsd:complexType name="ActivityStateType"> <xsd:sequence> <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType>
<xsd:complexType name="ActivityStatusType"> <xsd:choice> <xsd:element name="Pending" type="bes-factory:ActivityStateType"/> <xsd:element name="Running" type="bes-factory:ActivityStateType"/> <xsd:element name="Cancelled" type="bes-factory:ActivityStateType"/> <xsd:element name="Failed" type="bes-factory:ActivityStateType"/> <xsd:element name="Finished" type="bes-factory:ActivityStateType"/> </xsd:choice> </xsd:complexType>
Um ... how can we track these issues, and (more importantly) quickly get some closure on them in order to update our implementations?
Great question. I lost track of where the spec is. Last I remember it was going to be edited for release. What's going on with that? Unless someone objects, I think we could easily hold a lazy vote (i.e. -1, +0, +1) on these schema "bug fixes" and then update the spec if no -1's are encountered within a few days. Peter
-- Chris
-- ogsa-bes-wg mailing list ogsa-bes-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-bes-wg