RE: [wsdm] MUWS schema and WSDM fixes

["Sedukhin, Igor S" <Igor.Sedukhin@ca.com>]

#1 State and StateTransition elements are used to indicate things wrapped in other elements sometimes. See MOWS.

Types are also used.

 

#2 I agree, but why then MUWS defines all those propery collection containers? What is the purpose??

I thought the original purpose of this was that if I want to implement this set of properties I'd do that.

Should we then define model groups instead so that developers can ref them... I think so... http://www.w3.org/TR/xmlschema-1/#cModel_Group_Definitions

 

#3 I do not agree. I believe that definitions of request/reply elements are very reusable and have no tie with WSDL. They can be used by any kind of messaging softare to design message peyload even if the WSDL is not there or cannot be processed by the tools. I believe that spec is right and Id' like to see schema reflect the spec and not the vice versa.

 

 

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749 

 

---

From: Murray, Bryan P. [mailto:bryan.murray@hp.com]
Sent: Tuesday, November 23, 2004 3:12 PM
To: Sedukhin, Igor S; wsdm@lists.oasis-open.org
Subject: RE: [wsdm] MUWS schema and WSDM fixes

#1 This was an oversight. Both State and StateTransition are listed as GEDs in the spec. However, I don't understand why either one needs to be a GED. It is important to define the type so that properties and notifications can be defined with these types. Why do we need to have GEDs with these names?

 

#2 MUWS should not add xs:any to every resource properties snippet that we define - this is up to the developer that composes the desired properties documents together into a final resource properties document. The developer may choose to add xs:any or not for the resources she is implementing. MUWS should not dictate whether this is done.

 

#3 One reason for separating the schema and the WSDL into 2 namespaces is to separate the reusable type definitions from the one time use WSDL definitions. For this reason, I think the message definitions need to be done in the WSDL namespace. I would change the spec to make this so.

 

Bryan

---

From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
Sent: Tuesday, November 23, 2004 12:00 AM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] MUWS schema and WSDM fixes

#1

<xs:element name="StateTransition" type="muws-p2-xs:StateTransitionType"/>

this is missing, on the other hand,

 

<xs:element name="State" type="muws-p2-xs:StateType"/>

is not needed

 

#2 why are all property elements not open? e.g.

 

<xs:complexType name="OperationalStatusPropertiesType">

<xs:sequence>

<xs:element ref="muws-p2-xs:OperationalStatus"/>

</xs:sequence>

</xs:complexType>

it needs

 

<xs:any minOccurs="0" maxOccurs="unbounded"

namespace="##any" processContents="lax"/>

 

#3 you've declared operations e.g. QueryRelationshipsByType in http://docs.oasis-open.org/wsdm/2004/12/muws/wd-wsdm-muws-part2-1.0.wsdl namespace. That is not right it was supposed to be in the schema namespace (according to the spec).

 

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749