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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsn message

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


Subject: Re: [wsn] WS-BaseN issues addressed in 1.3a


Summary: All but 2.17 appear to be closed.  In detail:

  • 2.3 description might be a little clearer that the computed "absolute time" can cause a fault even if "duration" was specified, but basically good.  Closed, but I may tweak language in next rev.
  • <>
  • 2.11 SubscriptionReference added to Notify, with explanatory text.  Closed.
  • 2.17 Calls for three faults (InvalidTopicExpressionFault, TopicNotSupportedFault, TopicPathDialectUnknownFault) dealing with bad topic expressions to be shared by both Subscribe and GetCurrentMessage.  The text mentions invalid topic expression and unknown topic path dialect, but not with these particular names.  It doesn't mention TopicNotSupportedFault.  Further, the list for Subscribe includes faults that only apply to getCurrentMessage (topic expression names more than one topic, no message available for topic).  Unless I've grossly misunderstood, the issue should remain open.
  • 2.18 The SubscriptionManager section now RECOMMENDs WSRL but SMs MAY support other means of destruction.  They MUST advertise what they support.  Closed.
  • 2.19 The NP may now return an "Unable to subscribe" fault, for whatever reason.  Closed.
  • 2.21 Clarifications of schema have been incorporated.  Closed.
  • 2.22 {Pause,Resume}Subscription[Response] are all explicitly defined as {any}.  Closed.
  • 2.29 TerminationTime is now an optional element in SubscribeResponse.  Closed
  • 5.2 Description of pseudo-schemas follows Steve's email, with explicit mention that it is "similar to the WSDL 2.0 Part 1 specification [WSDL 2.0".  We may tweak this later if a more official description appears, but for now the issue is Closed.


Steve Graham wrote:

The latest version of WS-BaseN [1] addresses:

WSN 2.3, 2.11, 2.17, 2.18, 2.19, 2.21, 2.22, 2.29, 5.2

Would someone volunteer to verify the issues were properly executed?

I am now going to start diving into the issues resolved at the Oct f2f.

[1]http://www.oasis-open.org/apps/org/workgroup/wsn/download.php/10147/wsn-WS-BaseNotification-1.3-draft-01a.doc

sgg
++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++




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