[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Public Comment
Comment from: ramyan@us.ibm.com Name:Ramya Nagarajan Title:Validation error in ServiceGroup XSD Organization:IBM Regarding Specification:http://docs.oasis-open.org/wsrf/wsrf-ws_service_group-1.2-spec-pr-02.pdf The ServiceGroup XSD (http://docs.oasis-open.org/wsrf/sg-2.xsd) has the following complexType definition: <xsd:complexType name="ContentType"> <xsd:sequence> <xsd:element name="RPDoc" type="wsrf-sg:RPDocType" minOccurs="0" maxOccurs="1" /> <xsd:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> <xsd:anyAttribute namespace="##other" processContents="lax"/> </xsd:complexType> This does not validate because of a Unique Particle Attribution error. One way to fix this would be to redefine ContentType as follows: <xsd:complexType name="ContentType"> <xsd:sequence> <xsd:element name="RPDoc" type="wsrf-sg:RPDocType" minOccurs="0" maxOccurs="1" /> <xsd:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> <xsd:anyAttribute namespace="##other" processContents="lax"/> </xsd:complexType> I believe that this would maintain the semantics of the ServiceGroup specification. Any thoughts on this?
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]