6715 2009-03-17 23:13:41 +0000 Eventing: Mismatch in wseventing outline 2009-05-27 04:04:18 +0000 1 1 1 Unclassified WS-Resource Access Eventing FPWD PC Windows XP CLOSED REMIND hasProposal P2 normal --- 1 dug dug public-ws-resource-access-notifications oldest_to_newest 24303 0 dug 2009-03-17 23:13:41 +0000 Eventing shows this in the pseudo-schema: <wse:Subscribe ...> <wse:EndTo>endpoint-reference</wse:EndTo> ? <wse:Delivery Mode="xs:anyURI"? >xs:any</wse:Delivery> <wse:Expires>(xs:dateTime | xs:duration)</wse:Expires> ? <wse:Filter Dialect="xs:anyURI"? > xs:any </wse:Filter> ? ... </wse:Subscribe> But the xsd shows: - the xs:any in Delivery as xs:any* - attribute extensibility on Delivery - the xs:any in Filter as xs:any* - attribute extensibility on Filter Proposal: Change the pseudo-schema to match the xsd: <wse:Subscribe ...> <wse:EndTo>endpoint-reference</wse:EndTo> ? <wse:Delivery Mode="xs:anyURI"? ...> xs:any* </wse:Delivery> <wse:Expires>(xs:dateTime | xs:duration)</wse:Expires> ? <wse:Filter Dialect="xs:anyURI"? ...> xs:any* </wse:Filter> ? ... </wse:Subscribe> by making the xs:any on Delivery and Filter xs:any* and adding ... to these elements. 24609 1 bob 2009-04-07 20:00:05 +0000 resolved with comment #1