Issue Verification - 3.18, AI 109

[Susan Malaika <malaika@us.ibm.com>]

3.18 Resource property Topics should be TopicExpression

The text of the issue 3.18 in the issues list for brokered notification 
refers to resource property Topics:
"Resource property Topics does not exist any more (resolution of WSN2.38). 
It should be changed to TopicExpression" 

The email referred to in issue 3.18 says: 
"The following declaration in the wsdl:

<xsd:element name="NotificationBrokerRP">
      <xsd:complexType>
            <xsd:sequence>
                  <!-- From NotificationProducer -->
                  <xsd:element ref="wsnt:Topic" minOccurs="1"
                        maxOccurs="unbounded" />
                  <xsd:element ref="wsnt:FixedTopicSet"
                        minOccurs="1" maxOccurs="1" />
                  <xsd:element ref="wsnt:TopicExpressionDialects"
                        minOccurs="1" maxOccurs="unbounded" />
                  <!-- NotificationBroker specific  -->
                  <xsd:element ref="wsbn:RequiresRegistration"
                        minOccurs="1" maxOccurs="1" />
            </xsd:sequence>
      </xsd:complexType>
</xsd:element>

incorrectly referes to a non-existent element wsnt:Topic This should be
wsnt:TopicExpression


The text of issue 2.38 says:
"The Topics RP holds different TopicExpression values, and therefore 
TopicExpression is a more appropriate name for it."
The resolution of 2.38 says:
Tighten the current wording in the description of this resource property - 
Change ?reasonably expect the acceptance of a topic? to ?should not 
produce a topic unknown fault?
...............................................................................
My verification notes:
It looks like the NotificationBrokerRP element reference has been fixed 
and refers to TopicExpression. However I do see an RP called Topic and not 
TopicExpression elsewhere eeeeeeeeeeeeeeeeeekkkkkkkkk. Does this need 
examing? 
<!-- ====== Resource Properties for PublisherRegistration ========= -->
   <xsd:element name="PublisherReference" 
                      type="wsa:EndpointReferenceType" />
   <xsd:element name="Topic"
                      type="wsn-b:TopicExpressionType" />
   <xsd:element name="Demand" 
                      type="xsd:boolean" />
   <xsd:element name="CreationTime" 
                      type="xsd:dateTime" />
<xsd:element name="NotificationBrokerRP" >


Although the text of issue 3.18 refers to resource properties only, some 
items in brokered notification do use Topic and not TopicExpression, e.g., 
in messages 
<!-- ========== Message Types for NotificationBroker  ============ -->
   <xsd:element name="RegisterPublisher">
            <xsd:complexType>
               <xsd:sequence>
                  <xsd:element name="PublisherReference" 
                               type="wsa:EndpointReferenceType" 
                               minOccurs="0" maxOccurs="1" />
                  <xsd:element name="Topic" 
                               type="wsn-b:TopicExpressionType"
                               minOccurs="0" maxOccurs="unbounded" />
Maybe that's OK - but just thought I'd mention 
..........................................................................................................................................................................................................................................



AI 109 for base notification says - Bryan to clarify new para "The NP MUST 
respond with ..." in the description of 
wsnt:Filter/wsnt:TopicExpression/@Dialect.

My verification notes:

Here is the new text and it looks fine to me
If the TopicExpression is incompatible with or does not comply with the 
rules of the dialect, the NotificationProducer MUST respond with a 
InvalidTopicExpressionFault.

Susan Malaika