OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [wsdm] more or less final MOWS schema


I guess these may not contradict each other. That is, group can be merely part of the aggretate sequence. I'll bring up the conformance question in WSRF. Seems like just the spec wording ambiguity. XML Schema allows this all right. 
-----Original Message-----
From: Vambenepe, William N [mailto:vbp@hp.com]
Sent: Tue 11/23/2004 10:40 PM
To: Sedukhin, Igor S; wsdm@lists.oasis-open.org
Cc:
Subject: RE: [wsdm] more or less final MOWS schema

Hi Igor,
 
The way you define the properties document by referring to the model group looks elegant but it is unclear to me (to put it generously) whether it is compliant with WS-ResourceProperties. Quoting from WS-RP section 4.2:
 
"The child elements MUST be aggregated using xsd:sequence or xsd:all": so for one thing you might have to put a <sequence> wrapper around the <group>.
 
"Child elements MUST be defined using XML schema element reference (@ref).": you do use a @ref but it's @ref on a group, not an element...
 
Maybe we should bring that up to WSRF and have them be more friendly to model groups as I like the mechanism. That being said, like all other rarely seen schema constructs, I would like to ask the group what kind of support there is for this in the tools? Any feedback on this?
 
Regards,
 
William
 
 


From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
Sent: Tuesday, November 23, 2004 2:06 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] more or less final MOWS schema

I have reworked the MOWS schema to be nicely serializeable and properly open. Note the use of developer-friendly, reuseable model groups instead of useless types for property sets. The file is attached. The most important fix is to the RequestProcessingNotification. It is as follows.
I will update MOWS spec in the next rev.
 

<RequestProcessingNotification CurrentTime=”xs:dateTime” ...>

<muws-xs2:StateTransition Time=”…”>

            <muws-xs2:EnteredState>…</muws-xs2:EnteredState>

            <muws-xs2:PreviousState>…</muws-xs2:PreviousState>

           

</muws-xs2:StateTransition> +

<Request ...>

            <Message ...>

            (

                        <NotIncluded/> |

                        <Text>xs:string</Text> |

                        <Binary>xs:base64Binary</Binary> |

                        <Xml ...>{any}*</Xml>

            )

            <Size Unit=(“bit” | “byte” | “word” | “dword” | “qword”) ...>xs:positiveInteger</Size> ?

            {any}*

            </Message>

            <TransportInformation ...> {any}* </TransportInformation> ?

            {any}*

</Request> ?

<Reply>

            … see contents of the Request element above …

</Reply> ?

{any}*

</RequestProcessingNotification>

 
 

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

 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]