[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsdm] Problem defining Relationship XML
I donot think making "role" an
element will solve the problem. The problem is because ''muws-p1-xs:ResourceId'
is optional and from another namespace. The name matches both the optional
particle and the following wildcard, which violates "Unique Particle
Attribution" rule.
The
following options fix the schema error:
(1) Make MUWS part1 and part2 in the same namespace, as suggested by Igor, and Fred. If this is not possible, then
(2) Introduce a wrapper element wraps elements "ManageabilityEndpointReference" and "ResourceId". These two perhaps are the most commonly used identifiers for a participant. Putting them in an element and separating from other "unknown" identifier types does not make things worse. I don't have a good name for the wrapping element yet. <complexType name =
"RelationshipParticipantType">
<xs:sequence> <xs:element name="Role" type="xs:anyURI"/> <xs:element name = "Wrapper" minOccurs='0'> <complexType> <sequence> <element ref = "muws-p1-xs:ManageabilityEndpointReference" minOccurs = "0" maxOccurs = "unbounded"/> <element ref = "muws-p1-xs:ResourceId" minOccurs = "0"/> </sequence> </complexType> </xs:element> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other"/> </complexType> (3) Rearrange the order of elements in the sequence. One possible way is to move "Role" to the third element (before "any"): <complexType name =
"RelationshipParticipantType">
<xs:sequence> <xs:element ref="muws-p1-xs:ManageabilityEndpointReference" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="muws-p1-xs:ResourceId" minOccurs="0"/> <xs:element name="Role" type="xs:anyURI"/> <xs:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="lax"/> </xs:sequence> <xs:anyAttribute namespace="##other"/> </complexType> This one doesn't look pleasant. It does correct the schema error
though.
There is no perfect solution at this time. But this issue has to be
resolved.
Thanks
Zhili Zhang TIBCO Software Inc.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]