Changes between Version 15 and Version 16 of technicalGuideAndManual

Timestamp:

07/20/12 14:50:39 (13 years ago)

Author:

bartek

Comment:

--

technicalGuideAndManual

@@ -1 +1 @@
 {{{
-#!html
-<div class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d0e1"></a><span class="emphasis"><em>QCG Notification</em></span> v. 2.6 Technical Guide and
-    Manual</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Bartosz</span> <span class="surname">Bosak</span></h3><code class="email">&lt;<a class="email" href="mailto:bbosak@man.poznan.pl">bbosak@man.poznan.pl</a>&gt;</code></div><div class="author"><h3 class="author"><span class="firstname">Krzysztof</span> <span class="surname">Kurowski</span></h3><code class="email">&lt;<a class="email" href="mailto:krzysztof.kurowski@man.poznan.pl">krzysztof.kurowski@man.poznan.pl</a>&gt;</code></div></div></div><div><p class="releaseinfo">2.6.3</p></div><div><p class="copyright">Copyright &copy; 2008-2012 Poznan Supercomputing and Networking Center</p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#d0e37">1. Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e48">1.1. Motivations</a></span></dt><dt><span class="sect2"><a href="#d0e56">1.2. Purpose of the Document</a></span></dt><dt><span class="sect2"><a href="#d0e71">1.3. Status</a></span></dt></dl></dd><dt><span class="sect1"><a href="#d0e76">2. Terminology and WS-Notification Concept</a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e84">2.1. WS-Notification Concept</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e87">2.1.1. WS-Notification Fundamentals</a></span></dt><dt><span class="sect3"><a href="#d0e130">2.1.2. WS-BaseNotification</a></span></dt><dt><span class="sect3"><a href="#d0e192">2.1.3. WS-BrokeredNotification</a></span></dt><dt><span class="sect3"><a href="#d0e270">2.1.4. WS-Topics</a></span></dt><dt><span class="sect3"><a href="#d0e324">2.1.5. Base of QCG Notification</a></span></dt></dl></dd><dt><span class="sect2"><a href="#d0e416">2.2. UML-style Diagrams</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e457">2.2.1. `Main Use Cases</a></span></dt><dt><span class="sect3"><a href="#d0e490">2.2.2. Main Sequence Diagrams</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="#d0e499">3. User Guide for a Publisher, Subscriber and
-    NotificationConsumer </a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e504">3.1. Prefixes and Namespaces</a></span></dt><dt><span class="sect2"><a href="#d0e582">3.2. Interaction with QCG Notification</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e592">3.2.1. Publisher Interaction</a></span></dt><dt><span class="sect3"><a href="#d0e606">3.2.2. Subscriber interaction</a></span></dt><dt><span class="sect3"><a href="#d0e631">3.2.3. NotificationConsumer Interaction</a></span></dt></dl></dd><dt><span class="sect2"><a href="#ted">3.3. Topics, TopicExpressions and Dialects</a></span></dt><dt><span class="sect2"><a href="#d0e685">3.4. Extensions</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e693">3.4.1. TopicExpression</a></span></dt><dt><span class="sect3"><a href="#d0e704">3.4.2. QCG Notification Extensions</a></span></dt></dl></dd><dt><span class="sect2"><a href="#d0e715">3.5. Methods Description</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e749">3.5.1. SubscribeRequest</a></span></dt><dt><span class="sect3"><a href="#d0e856">3.5.2. SubscribeResponse</a></span></dt><dt><span class="sect3"><a href="#d0e904">3.5.3. RenewRequest</a></span></dt><dt><span class="sect3"><a href="#d0e945">3.5.4. RenewResponse</a></span></dt><dt><span class="sect3"><a href="#d0e989">3.5.5. UnsubscribeRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1022">3.5.6. UnsubscribeResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1043">3.5.7. RegisterPublisherRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1096">3.5.8. RegisterPublisherResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1141">3.5.9. Notify</a></span></dt><dt><span class="sect3"><a href="#d0e1225">3.5.10. DestroyRegistrationRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1258">3.5.11. DestroyRegistrationResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1279">3.5.12. CreatePullPointRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1303">3.5.13. CreatePullPointResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1333">3.5.14. GetMessages</a></span></dt><dt><span class="sect3"><a href="#d0e1366">3.5.15. GetMessagesResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1443">3.5.16. DestroyPullPointRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1464">3.5.17. DestroyPullPointResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1485">3.5.18. GetCurrentMessageRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1532">3.5.19. GetCurrentMessageResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1598">3.5.20. ListSubscriptions</a></span></dt><dt><span class="sect3"><a href="#d0e1700">3.5.21. ListSubscriptionsResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1797">3.5.22. ListPublishersRegistrations</a></span></dt><dt><span class="sect3"><a href="#d0e1878">3.5.23. ListPublisherRegistrationsResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1952">3.5.24. ListPullPoints</a></span></dt><dt><span class="sect3"><a href="#d0e2033">3.5.25. ListPullPointsResponse</a></span></dt><dt><span class="sect3"><a href="#d0e2107">3.5.26. ListTopicNamespaces</a></span></dt><dt><span class="sect3"><a href="#d0e2147">3.5.27. ListTopicNamespacesResponse</a></span></dt><dt><span class="sect3"><a href="#d0e2206">3.5.28. AddTopicNamespace</a></span></dt><dt><span class="sect3"><a href="#d0e2243">3.5.29. AddTopicNamespaceResponse</a></span></dt><dt><span class="sect3"><a href="#d0e2268">3.5.30. RemoveTopicNamespace</a></span></dt><dt><span class="sect3"><a href="#d0e2302">3.5.31. RemoveTopicNamespaceResponse</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="#d0e2324">4. Administration Guide of QCG
-    Notification</a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e2329">4.1. Prerequisites</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e2337">4.1.1. QCG Core library</a></span></dt></dl></dd><dt><span class="sect2"><a href="#d0e2355">4.2. Building</a></span></dt><dt><span class="sect2"><a href="#d0e2416">4.3. Creating database for QCG Notification - the
-      PostgreSQL example</a></span></dt></dl></dd><dt><span class="sect1"><a href="#configuration">5. Configuration of QCG Notification</a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e2506">5.1. Configuration File: qcg-ntfd.xml</a></span></dt><dt><span class="sect2"><a href="#moduleoptions">5.2. Module configuration</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e2838">5.2.1. Publisher modules</a></span></dt></dl></dd><dt><span class="sect2"><a href="#d0e3097">5.3. WS-Topics management</a></span></dt><dt><span class="sect2"><a href="#d0e3125">5.4. Starting QCG Notification</a></span></dt><dt><span class="sect2"><a href="#d0e3148">5.5. Stopping QCG Notification</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e37"></a>1.&nbsp;Introduction</h2></div></div></div><p><span class="bold"><strong>QCG Notification</strong></span> is a reference
+<div class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="d0e1"></a><span class="emphasis"><em>QCG-Notification</em></span> v. 2.6 Technical Guide and
+    Manual</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Bartosz</span> <span class="surname">Bosak</span></h3><code class="email">&lt;<a class="email" href="mailto:bbosak@man.poznan.pl">bbosak@man.poznan.pl</a>&gt;</code></div><div class="author"><h3 class="author"><span class="firstname">Krzysztof</span> <span class="surname">Kurowski</span></h3><code class="email">&lt;<a class="email" href="mailto:krzysztof.kurowski@man.poznan.pl">krzysztof.kurowski@man.poznan.pl</a>&gt;</code></div></div></div><div><p class="releaseinfo">2.6.3</p></div><div><p class="copyright">Copyright &copy; 2008-2012 Poznan Supercomputing and Networking Center</p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#d0e37">1. Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e48">1.1. Motivations</a></span></dt><dt><span class="sect2"><a href="#d0e56">1.2. Purpose of the Document</a></span></dt><dt><span class="sect2"><a href="#d0e71">1.3. Status</a></span></dt></dl></dd><dt><span class="sect1"><a href="#d0e76">2. Terminology and WS-Notification Concept</a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e84">2.1. WS-Notification Concept</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e87">2.1.1. WS-Notification Fundamentals</a></span></dt><dt><span class="sect3"><a href="#d0e130">2.1.2. WS-BaseNotification</a></span></dt><dt><span class="sect3"><a href="#d0e192">2.1.3. WS-BrokeredNotification</a></span></dt><dt><span class="sect3"><a href="#d0e270">2.1.4. WS-Topics</a></span></dt><dt><span class="sect3"><a href="#d0e324">2.1.5. Base of QCG-Notification</a></span></dt></dl></dd><dt><span class="sect2"><a href="#d0e416">2.2. UML-style Diagrams</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e457">2.2.1. `Main Use Cases</a></span></dt><dt><span class="sect3"><a href="#d0e490">2.2.2. Main Sequence Diagrams</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="#d0e499">3. User Guide for a Publisher, Subscriber and
+    NotificationConsumer </a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e504">3.1. Prefixes and Namespaces</a></span></dt><dt><span class="sect2"><a href="#d0e582">3.2. Interaction with QCG-Notification</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e592">3.2.1. Publisher Interaction</a></span></dt><dt><span class="sect3"><a href="#d0e606">3.2.2. Subscriber interaction</a></span></dt><dt><span class="sect3"><a href="#d0e631">3.2.3. NotificationConsumer Interaction</a></span></dt></dl></dd><dt><span class="sect2"><a href="#ted">3.3. Topics, TopicExpressions and Dialects</a></span></dt><dt><span class="sect2"><a href="#d0e685">3.4. Extensions</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e693">3.4.1. TopicExpression</a></span></dt><dt><span class="sect3"><a href="#d0e704">3.4.2. QCG-Notification Extensions</a></span></dt></dl></dd><dt><span class="sect2"><a href="#d0e715">3.5. Methods Description</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e749">3.5.1. SubscribeRequest</a></span></dt><dt><span class="sect3"><a href="#d0e856">3.5.2. SubscribeResponse</a></span></dt><dt><span class="sect3"><a href="#d0e904">3.5.3. RenewRequest</a></span></dt><dt><span class="sect3"><a href="#d0e945">3.5.4. RenewResponse</a></span></dt><dt><span class="sect3"><a href="#d0e989">3.5.5. UnsubscribeRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1022">3.5.6. UnsubscribeResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1043">3.5.7. RegisterPublisherRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1096">3.5.8. RegisterPublisherResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1141">3.5.9. Notify</a></span></dt><dt><span class="sect3"><a href="#d0e1225">3.5.10. DestroyRegistrationRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1258">3.5.11. DestroyRegistrationResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1279">3.5.12. CreatePullPointRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1303">3.5.13. CreatePullPointResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1333">3.5.14. GetMessages</a></span></dt><dt><span class="sect3"><a href="#d0e1366">3.5.15. GetMessagesResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1443">3.5.16. DestroyPullPointRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1464">3.5.17. DestroyPullPointResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1485">3.5.18. GetCurrentMessageRequest</a></span></dt><dt><span class="sect3"><a href="#d0e1532">3.5.19. GetCurrentMessageResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1598">3.5.20. ListSubscriptions</a></span></dt><dt><span class="sect3"><a href="#d0e1700">3.5.21. ListSubscriptionsResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1797">3.5.22. ListPublishersRegistrations</a></span></dt><dt><span class="sect3"><a href="#d0e1878">3.5.23. ListPublisherRegistrationsResponse</a></span></dt><dt><span class="sect3"><a href="#d0e1952">3.5.24. ListPullPoints</a></span></dt><dt><span class="sect3"><a href="#d0e2033">3.5.25. ListPullPointsResponse</a></span></dt><dt><span class="sect3"><a href="#d0e2107">3.5.26. ListTopicNamespaces</a></span></dt><dt><span class="sect3"><a href="#d0e2147">3.5.27. ListTopicNamespacesResponse</a></span></dt><dt><span class="sect3"><a href="#d0e2206">3.5.28. AddTopicNamespace</a></span></dt><dt><span class="sect3"><a href="#d0e2243">3.5.29. AddTopicNamespaceResponse</a></span></dt><dt><span class="sect3"><a href="#d0e2268">3.5.30. RemoveTopicNamespace</a></span></dt><dt><span class="sect3"><a href="#d0e2302">3.5.31. RemoveTopicNamespaceResponse</a></span></dt></dl></dd></dl></dd><dt><span class="sect1"><a href="#d0e2324">4. Administration Guide of
+    QCG-Notification</a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e2329">4.1. Prerequisites</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e2337">4.1.1. QCG Core library</a></span></dt></dl></dd><dt><span class="sect2"><a href="#d0e2355">4.2. Building</a></span></dt><dt><span class="sect2"><a href="#d0e2416">4.3. Creating database for QCG-Notification - the
+      PostgreSQL example</a></span></dt></dl></dd><dt><span class="sect1"><a href="#configuration">5. Configuration of QCG-Notification</a></span></dt><dd><dl><dt><span class="sect2"><a href="#d0e2506">5.1. Configuration File: qcg-ntfd.xml</a></span></dt><dt><span class="sect2"><a href="#moduleoptions">5.2. Module configuration</a></span></dt><dd><dl><dt><span class="sect3"><a href="#d0e2838">5.2.1. Publisher modules</a></span></dt></dl></dd><dt><span class="sect2"><a href="#d0e3097">5.3. WS-Topics management</a></span></dt><dt><span class="sect2"><a href="#d0e3125">5.4. Starting QCG-Notification</a></span></dt><dt><span class="sect2"><a href="#d0e3148">5.5. Stopping QCG-Notification</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e37"></a>1.&nbsp;Introduction</h2></div></div></div><p><span class="bold"><strong>QCG-Notification</strong></span> is a reference
     implementation of a set of industry Web Service specifications (<a class="link" href="#WS-Notification"></a><a class="ulink" href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn" target="_top">WS-Notification
     OASIS standard)</a><a class="link" href="#WS-Notification"></a> for message push/pull-style notification,
@@ -32 +31 @@
       standardization body, either implement only partially notification
       standards or do not meet high performance requirements. Therefore, our
-      main motivation was to design and implement <span class="emphasis"><em>QCG
-      Notification</em></span> to offer more advanced push/pull
+      main motivation was to design and implement
+      <span class="emphasis"><em>QCG-Notification</em></span> to offer more advanced push/pull
       (synchronous/asynchronous) standard notification routines for QCG
       Service Bus services as well as any third party Web Services.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e56"></a>1.2.&nbsp;Purpose of the Document</h3></div></div></div><p>The main goal of this document is to define a set of initial use
-      cases, scenarios and specify software requirements for <span class="emphasis"><em>QCG
-      Notification</em></span>, its programming application interface,
-      functional units and the integration with both internal and external
-      modules.</p><p>The document is aimed at software architects and programmers who
+      cases, scenarios and specify software requirements for
+      <span class="emphasis"><em>QCG-Notification</em></span>, its programming application
+      interface, functional units and the integration with both internal and
+      external modules.</p><p>The document is aimed at software architects and programmers who
       will be developing software components based on this document. Many
-      requirements and <span class="emphasis"><em>QCG Notification </em></span>concept itself
+      requirements and <span class="emphasis"><em>QCG-Notification </em></span>concept itself
       might be interesting for developers and end users of any Web
       Services.</p><p>This document assumes that the reader has at least a basic
       background in Web Service and SOA technologies.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e71"></a>1.3.&nbsp;Status</h3></div></div></div><p>This document is updated periodically on no particular
       schedule.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e76"></a>2.&nbsp;Terminology and WS-Notification Concept</h2></div></div></div><p>The aim of this section is to capture high-level functionality of
-    <span class="emphasis"><em>QCG Notification</em></span> and/or interaction without providing
+    <span class="emphasis"><em>QCG-Notification</em></span> and/or interaction without providing
     excessive implementation or technical details of the system.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e84"></a>2.1.&nbsp;WS-Notification Concept</h3></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e87"></a>2.1.1.&nbsp;WS-Notification Fundamentals</h4></div></div></div><p>Notification-based pattern is commonly used for
         interaction between distributed objects. WS-Notification is a family
@@ -92 +91 @@
         NotificationBroker and defines more advanced notification scenarios.
         The figure below shows an example scenario and notification message
-        flow where NotificationBroker is present.</p><div class="figure"><a name="d0e198"></a><p class="title"><b>Figure&nbsp;2.&nbsp;Web Services BrokeredNotification entities - QCG
-            Notification entities</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/smn_brokeredentities.png" align="middle" width="324" alt="Web Services BrokeredNotification entities - QCG Notification entities"></div></div></div><p><br class="figure-break">Note, that there are some important enlargements and
+        flow where NotificationBroker is present.</p><div class="figure"><a name="d0e198"></a><p class="title"><b>Figure&nbsp;2.&nbsp;Web Services BrokeredNotification entities -
+            QCG-Notification entities</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/smn_brokeredentities.png" align="middle" width="324" alt="Web Services BrokeredNotification entities - QCG-Notification entities"></div></div></div><p><br class="figure-break">Note, that there are some important enlargements and
         modifications in the WS-BrokeredNotificatison terminology. Below the
         most relevant definitions are presented.</p><div class="variablelist"><dl><dt><span class="term">Situation</span></dt><dd><p>Some occurrence, known by a Publisher. A Situation is a
@@ -145 +144 @@
               TopicExpression. The specification defines four Dialects:
               <span class="emphasis"><em>Simple</em></span>, <span class="emphasis"><em>Concrete</em></span>,
-              <span class="emphasis"><em>Full</em></span> and <span class="emphasis"><em>XPath</em></span>.</p></dd></dl></div><div class="figure"><a name="d0e318"></a><p class="title"><b>Figure&nbsp;3.&nbsp;Example Topic Namespace</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/smn_topicnamespace.png" align="middle" width="324" alt="Example Topic Namespace"></div></div></div><br class="figure-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e324"></a>2.1.5.&nbsp;Base of <span class="emphasis"><em>QCG Notification</em></span></h4></div></div></div><p><span class="emphasis"><em>QCG Notification</em></span> is a reference
+              <span class="emphasis"><em>Full</em></span> and <span class="emphasis"><em>XPath</em></span>.</p></dd></dl></div><div class="figure"><a name="d0e318"></a><p class="title"><b>Figure&nbsp;3.&nbsp;Example Topic Namespace</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/smn_topicnamespace.png" align="middle" width="324" alt="Example Topic Namespace"></div></div></div><br class="figure-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e324"></a>2.1.5.&nbsp;Base of <span class="emphasis"><em>QCG-Notification</em></span></h4></div></div></div><p><span class="emphasis"><em>QCG-Notification</em></span> is a reference
         implementation of WS-BaseNotification, WS-BrokeredNotification and
         WS-Topics OASIS industry standards. As a consistent and highly
@@ -153 +152 @@
         scale Web Service based systems, SOA environments and it acts as a
         core component in QCG Service Bus. To meet security requirements,
-        <span class="emphasis"><em>QCG Notification</em></span> (or <span class="emphasis"><em>QCG Notification
+        <span class="emphasis"><em>QCG-Notification</em></span> (or <span class="emphasis"><em>QCG-Notification
         Provider</em></span>) exposes well defined Web Service and programming
         interfaces over QCG security mechanisms for dynamic notification,
@@ -159 +158 @@
         the previous sections it can be used and integrated with various
         external third party Web Services playing roles of a notification
-        Publisher, Subscriber or Consumer.</p><p>A flexible plug-in architecture of <span class="emphasis"><em>QCG Notification
+        Publisher, Subscriber or Consumer.</p><p>A flexible plug-in architecture of <span class="emphasis"><em>QCG-Notification
         </em></span>enables using different communication protocols for
         messages transmission. Currently messages can be transported between
-        <span class="emphasis"><em>QCG Notification</em></span> and third party entities not
+        <span class="emphasis"><em>QCG-Notification</em></span> and third party entities not
         only through HTTP protocol, but also through XMPP (jabber) as well as
         SMTP (e-mail) protocols. It is possible to variously mix channels of
@@ -168 +167 @@
         WS-Client as a HTTP message can be distributed over XMPP to jabber
         consumers.</p><p>Below we present a set of Web Service notification use cases
-        demonstrating capabilities offered by <span class="emphasis"><em>QCG
-        Notification</em></span>.</p><div class="figure"><a name="notificationConsumers"></a><p class="title"><b>Figure&nbsp;4.&nbsp;Notification with multiple Publishers and multiple
+        demonstrating capabilities offered by
+        <span class="emphasis"><em>QCG-Notification</em></span>.</p><div class="figure"><a name="notificationConsumers"></a><p class="title"><b>Figure&nbsp;4.&nbsp;Notification with multiple Publishers and multiple
           NotificationConsumers</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/smn_example1.png" align="middle" width="324" alt="Notification with multiple Publishers and multiple NotificationConsumers"></div></div></div><br class="figure-break"><p>The <a class="link" href="#notificationConsumers" title="Figure&nbsp;4.&nbsp;Notification with multiple Publishers and multiple NotificationConsumers">diagram 4</a> shows
-        one of the basic notification flows supported by <span class="emphasis"><em>QCG
-        Notification</em></span>. Depending on records, Notifications produced
-        by a Publisher and received by the <span class="emphasis"><em>QCG
-        Notification</em></span> may or may not be dispatched to concrete
-        NotificationConsumer. Note, that Subscriptions represent relationships
-        between Topics and NotificationConsumers in this scenario. Before any
-        Notification is delivered to a NotificationConsumer, a Subscriber has
-        to send first a SubscribeRequest message to <span class="emphasis"><em>QCG
-        Notification</em></span> in which all parameters of a Subscription are
-        specified. Main parameters of a SubscribeRequest message are
-        ConsumerReference and TopicExpression defined according to the
-        specific Dialect type. On the other hand, before a Publisher starts
-        sending Notifications it may be obligated to register himself in
-        <span class="emphasis"><em>QCG Notification</em></span>. The diagram below shows a
+        one of the basic notification flows supported by
+        <span class="emphasis"><em>QCG-Notification</em></span>. Depending on records,
+        Notifications produced by a Publisher and received by the
+        <span class="emphasis"><em>QCG-Notification</em></span> may or may not be dispatched to
+        concrete NotificationConsumer. Note, that Subscriptions represent
+        relationships between Topics and NotificationConsumers in this
+        scenario. Before any Notification is delivered to a
+        NotificationConsumer, a Subscriber has to send first a
+        SubscribeRequest message to <span class="emphasis"><em>QCG-Notification</em></span> in
+        which all parameters of a Subscription are specified. Main parameters
+        of a SubscribeRequest message are ConsumerReference and
+        TopicExpression defined according to the specific Dialect type. On the
+        other hand, before a Publisher starts sending Notifications it may be
+        obligated to register himself in
+        <span class="emphasis"><em>QCG-Notification</em></span>. The diagram below shows a
         sequence of events in order to initialize an asynchronous process of
         notifications between a Publisher and a NotificationConsumer.</p><div class="figure"><a name="d0e378"></a><p class="title"><b>Figure&nbsp;5.&nbsp;Message flows: creating a Subscription, notifying
           NotificationConsumers</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/smn_example2.png" align="middle" width="324" alt="Message flows: creating a Subscription, notifying NotificationConsumers"></div></div></div><br class="figure-break"><div class="orderedlist"><ol type="1"><li><p>A Subscriber sends the SubscribeRequest message with a
             NotificationConsumer location and TopicExpression parameters to
-            <span class="emphasis"><em>QCG Notification</em></span>.</p></li><li><p><span class="emphasis"><em>QCG Notification</em></span> prepares appropriate
-            records for a Subscription.</p></li><li><p>A Publisher register himself in <span class="emphasis"><em>QCG
-            Notification</em></span> by sending the RegisterPublisher
-            message.</p></li><li><p>A registered Publisher sends the Notify message on a
-            specified Topic to a <span class="emphasis"><em>QCG Notification
-            </em></span>service.</p></li><li><p><span class="emphasis"><em>QCG Notification</em></span> checks if there are
+            <span class="emphasis"><em>QCG-Notification</em></span>.</p></li><li><p><span class="emphasis"><em>QCG-Notification</em></span> prepares appropriate
+            records for a Subscription.</p></li><li><p>A Publisher register himself in
+            <span class="emphasis"><em>QCG-Notification</em></span> by sending the
+            RegisterPublisher message.</p></li><li><p>A registered Publisher sends the Notify message on a
+            specified Topic to a <span class="emphasis"><em>QCG-Notification
+            </em></span>service.</p></li><li><p><span class="emphasis"><em>QCG-Notification</em></span> checks if there are
             NotificationConsumers subscribed on a specified Topic. If so,
-            <span class="emphasis"><em>QCG Notification</em></span> sends asynchronous
+            <span class="emphasis"><em>QCG-Notification</em></span> sends asynchronous
             Notifications to these NotifcationConsumers.</p></li></ol></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e416"></a>2.2.&nbsp;UML-style Diagrams</h3></div></div></div><p>The document uses UML-style use-case diagrams to illustrate
       high-level use cases. The following list is probably sufficient for this
@@ -221 +221 @@
       clearly ordered message layout and connections among functional units.
       The actors and messages in the sequence diagrams are more properly roles
-      in a scenario and actions associated with that scenario.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e457"></a>2.2.1.&nbsp;`Main Use Cases</h4></div></div></div><div class="figure"><a name="d0e460"></a><p class="title"><b>Figure&nbsp;6.&nbsp;Use case diagram for a Publisher</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_publisher.png" align="middle" width="432" alt="Use case diagram for a Publisher"></div></div></div><br class="figure-break"><div class="figure"><a name="d0e466"></a><p class="title"><b>Figure&nbsp;7.&nbsp;Use case diagram for a Subscriber</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_subscriber.png" align="middle" width="432" alt="Use case diagram for a Subscriber"></div></div></div><br class="figure-break"><div class="figure"><a name="d0e472"></a><p class="title"><b>Figure&nbsp;8.&nbsp;Use case diagram for a NotificationConsumer</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_consumer.png" align="middle" width="432" alt="Use case diagram for a NotificationConsumer"></div></div></div><br class="figure-break"><div class="figure"><a name="d0e478"></a><p class="title"><b>Figure&nbsp;9.&nbsp;Use case diagram for QCG Notification</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_qcgnotification.png" align="middle" width="432" alt="Use case diagram for QCG Notification"></div></div></div><br class="figure-break"><div class="figure"><a name="d0e484"></a><p class="title"><b>Figure&nbsp;10.&nbsp;Use case diagram for a QCG Notification Administrator</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_administrator.png" align="middle" width="432" alt="Use case diagram for a QCG Notification Administrator"></div></div></div><br class="figure-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e490"></a>2.2.2.&nbsp;Main Sequence Diagrams</h4></div></div></div><div class="figure"><a name="d0e493"></a><p class="title"><b>Figure&nbsp;11.&nbsp;General sequence diagram</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/seq_all.png" align="middle" width="432" alt="General sequence diagram"></div></div></div><br class="figure-break"></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e499"></a>3.&nbsp;User Guide for a Publisher, Subscriber and
+      in a scenario and actions associated with that scenario.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e457"></a>2.2.1.&nbsp;`Main Use Cases</h4></div></div></div><div class="figure"><a name="d0e460"></a><p class="title"><b>Figure&nbsp;6.&nbsp;Use case diagram for a Publisher</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_publisher.png" align="middle" width="432" alt="Use case diagram for a Publisher"></div></div></div><br class="figure-break"><div class="figure"><a name="d0e466"></a><p class="title"><b>Figure&nbsp;7.&nbsp;Use case diagram for a Subscriber</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_subscriber.png" align="middle" width="432" alt="Use case diagram for a Subscriber"></div></div></div><br class="figure-break"><div class="figure"><a name="d0e472"></a><p class="title"><b>Figure&nbsp;8.&nbsp;Use case diagram for a NotificationConsumer</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_consumer.png" align="middle" width="432" alt="Use case diagram for a NotificationConsumer"></div></div></div><br class="figure-break"><div class="figure"><a name="d0e478"></a><p class="title"><b>Figure&nbsp;9.&nbsp;Use case diagram for QCG-Notification</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_qcgnotification.png" align="middle" width="432" alt="Use case diagram for QCG-Notification"></div></div></div><br class="figure-break"><div class="figure"><a name="d0e484"></a><p class="title"><b>Figure&nbsp;10.&nbsp;Use case diagram for a QCG-Notification Administrator</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_administrator.png" align="middle" width="432" alt="Use case diagram for a QCG-Notification Administrator"></div></div></div><br class="figure-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e490"></a>2.2.2.&nbsp;Main Sequence Diagrams</h4></div></div></div><div class="figure"><a name="d0e493"></a><p class="title"><b>Figure&nbsp;11.&nbsp;General sequence diagram</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/seq_all.png" align="middle" width="432" alt="General sequence diagram"></div></div></div><br class="figure-break"></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e499"></a>3.&nbsp;User Guide for a Publisher, Subscriber and
     NotificationConsumer<span class="emphasis"><em> </em></span></h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e504"></a>3.1.&nbsp;Prefixes and Namespaces</h3></div></div></div><p>The following table presents namespaces tied with prefixes. The
       prefixes are used in example SOAP messages presented in the further
-      sections.</p><div class="table"><a name="d0e509"></a><p class="title"><b>Table&nbsp;1.&nbsp;Prefixes and Namespaces</b></p><div class="table-contents"><table summary="Prefixes and Namespaces" border="1"><colgroup><col width="12%" align="left"><col width="88%"></colgroup><tbody><tr><td align="left"><span class="bold"><strong>Prefix</strong></span></td><td><span class="bold"><strong>Namespace</strong></span></td></tr><tr><td align="left">SOAP-ENV</td><td>http://schemas.xmlsoap.org/soap/envelope/</td></tr><tr><td align="left">SOAP-ENC</td><td>http://schemas.xmlsoap.org/soap/encoding/</td></tr><tr><td align="left">xsi</td><td>http://www.w3.org/2001/XMLSchema-instance</td></tr><tr><td align="left">xsd</td><td>http://www.w3.org/2001/XMLSchema</td></tr><tr><td align="left">wsa</td><td>http://www.w3.org/2005/08/addressing</td></tr><tr><td align="left">wsbf</td><td>http://docs.oasis-open.org/wsrf/bf-2</td></tr><tr><td align="left">wstop</td><td>http://docs.oasis-open.org/wsn/t-1</td></tr><tr><td align="left">wsr</td><td>http://docs.oasis-open.org/wsrf/r-2</td></tr><tr><td align="left">wsnt</td><td>http://docs.oasis-open.org/wsn/b-2</td></tr><tr><td align="left">wsntw</td><td>http://docs.oasis-open.org/wsn/bw-2</td></tr><tr><td align="left">wsnbr</td><td>http://docs.oasis-open.org/wsn/br-2</td></tr><tr><td align="left">smn-ext</td><td>http://schemas.qoscosgrid.org/ntf/2011/04/extensions</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e582"></a>3.2.&nbsp;Interaction with <span class="emphasis"><em>QCG Notification</em></span></h3></div></div></div><p>In the next subsections an issue of cooperation with <span class="emphasis"><em>QCG
-      Notification</em></span> is presented independently for a Publisher,
-      Subscriber and NotificationConsumer. Although a conceptual style of
-      interaction is described here in details, technical particularities of
-      constructing messages are presented later.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e592"></a>3.2.1.&nbsp;Publisher Interaction</h4></div></div></div><div class="figure"><a name="d0e595"></a><p class="title"><b>Figure&nbsp;12.&nbsp;Publisher interaction sequence diagram</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/seq_publisher.png" align="middle" width="432" alt="Publisher interaction sequence diagram"></div></div></div><br class="figure-break"><p>In the most general configuration of the service, a Publisher
+      sections.</p><div class="table"><a name="d0e509"></a><p class="title"><b>Table&nbsp;1.&nbsp;Prefixes and Namespaces</b></p><div class="table-contents"><table summary="Prefixes and Namespaces" border="1"><colgroup><col width="12%" align="left"><col width="88%"></colgroup><tbody><tr><td align="left"><span class="bold"><strong>Prefix</strong></span></td><td><span class="bold"><strong>Namespace</strong></span></td></tr><tr><td align="left">SOAP-ENV</td><td>http://schemas.xmlsoap.org/soap/envelope/</td></tr><tr><td align="left">SOAP-ENC</td><td>http://schemas.xmlsoap.org/soap/encoding/</td></tr><tr><td align="left">xsi</td><td>http://www.w3.org/2001/XMLSchema-instance</td></tr><tr><td align="left">xsd</td><td>http://www.w3.org/2001/XMLSchema</td></tr><tr><td align="left">wsa</td><td>http://www.w3.org/2005/08/addressing</td></tr><tr><td align="left">wsbf</td><td>http://docs.oasis-open.org/wsrf/bf-2</td></tr><tr><td align="left">wstop</td><td>http://docs.oasis-open.org/wsn/t-1</td></tr><tr><td align="left">wsr</td><td>http://docs.oasis-open.org/wsrf/r-2</td></tr><tr><td align="left">wsnt</td><td>http://docs.oasis-open.org/wsn/b-2</td></tr><tr><td align="left">wsntw</td><td>http://docs.oasis-open.org/wsn/bw-2</td></tr><tr><td align="left">wsnbr</td><td>http://docs.oasis-open.org/wsn/br-2</td></tr><tr><td align="left">smn-ext</td><td>http://schemas.qoscosgrid.org/ntf/2011/04/extensions</td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e582"></a>3.2.&nbsp;Interaction with <span class="emphasis"><em>QCG-Notification</em></span></h3></div></div></div><p>In the next subsections an issue of cooperation with
+      <span class="emphasis"><em>QCG-Notification</em></span> is presented independently for a
+      Publisher, Subscriber and NotificationConsumer. Although a conceptual
+      style of interaction is described here in details, technical
+      particularities of constructing messages are presented later.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e592"></a>3.2.1.&nbsp;Publisher Interaction</h4></div></div></div><div class="figure"><a name="d0e595"></a><p class="title"><b>Figure&nbsp;12.&nbsp;Publisher interaction sequence diagram</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/seq_publisher.png" align="middle" width="432" alt="Publisher interaction sequence diagram"></div></div></div><br class="figure-break"><p>In the most general configuration of the service, a Publisher
         has to be registered before it starts sending Notifications. In this
         situation, a Publisher sends the RegisterPublisherRequest message to
-        <span class="emphasis"><em>QCG Notification</em></span>. If everything goes well it
+        <span class="emphasis"><em>QCG-Notification</em></span>. If everything goes well it
         receives the RegisterPublisherResponse message with a session ID. From
         this time a Publisher is entitled for sending Notify messages - the
@@ -240 +240 @@
         should unregister himself by sending DestroyRegistration. This message
         has to include a session ID likewise.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e606"></a>3.2.2.&nbsp;Subscriber interaction</h4></div></div></div><div class="figure"><a name="d0e609"></a><p class="title"><b>Figure&nbsp;13.&nbsp;Subscriber interaction sequence diagram</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/seq_subscriber.png" align="middle" width="432" alt="Subscriber interaction sequence diagram"></div></div></div><br class="figure-break"><p>When a Subscriber wants to create a Subscription, it sends the
-        SubscribeRequest message to <span class="emphasis"><em>QCG Notification</em></span>.
+        SubscribeRequest message to <span class="emphasis"><em>QCG-Notification</em></span>.
         This message should contain an address of NotificationConsumer and a
         TopicExpression that specifies a Topic or a set of Topics on which
@@ -248 +248 @@
         From the version 2.5.0 of the system, the Subscriber may specify XSLT
         document that will be used to transform message content by certain
-        publishing modules. After creation of a Subscription <span class="emphasis"><em>QCG
-        Notification</em></span> sends the SubscribeResponse message with a
-        created Subscription ID. This ID should be attached to the
-        UnsubscribeRequest message when a Subscription is not wanted and the
-        Renew message when a Subscription should be refreshed. A Subscriber is
-        allowed to create many equal Subscriptions.</p><p>If a scenario requires pull-style of notifications, a Subscriber
+        publishing modules. After creation of a Subscription
+        <span class="emphasis"><em>QCG-Notification</em></span> sends the SubscribeResponse
+        message with a created Subscription ID. This ID should be attached to
+        the UnsubscribeRequest message when a Subscription is not wanted and
+        the Renew message when a Subscription should be refreshed. A
+        Subscriber is allowed to create many equal Subscriptions.</p><p>If a scenario requires pull-style of notifications, a Subscriber
         can create a set of PullPoints. In a such situation, it has to invoke
-        the CreatePullPoint method offered by <span class="emphasis"><em>QCG Notification.
+        the CreatePullPoint method offered by <span class="emphasis"><em>QCG-Notification.
         <span class="emphasis"><em>The response parameter of this method will be an address to
         the newly created <span class="emphasis"><em>PullPoint resource (Subscribers can assign
@@ -263 +263 @@
         </em></span></em></span></em></span></p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e631"></a>3.2.3.&nbsp;NotificationConsumer Interaction</h4></div></div></div><div class="figure"><a name="d0e635"></a><p class="title"><b>Figure&nbsp;14.&nbsp;NotificationConsumer interaction sequence diagram</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/seq_consumer.png" align="middle" width="432" alt="NotificationConsumer interaction sequence diagram"></div></div></div><p><br class="figure-break">The main capability of a NotificationConsumer is a
         receiving of Notify messages. A NotificationConsumer can implement an
-        interface for receiving Notify messages sending by <span class="emphasis"><em>QCG
-        Notification</em></span> or can be a client of a PullPoint. In the
-        second case, a NotificationConsumer can invoke GetMessages method
-        offered by a certain PullPoint. Messages buffered in the PullPoint
-        will be removed from the buffer and delivered in GetMessagesResponse
-        to the consumer.</p><p>On the other hand, when a NotificationConsumer wants to receive
+        interface for receiving Notify messages sending by
+        <span class="emphasis"><em>QCG-Notification</em></span> or can be a client of a
+        PullPoint. In the second case, a NotificationConsumer can invoke
+        GetMessages method offered by a certain PullPoint. Messages buffered
+        in the PullPoint will be removed from the buffer and delivered in
+        GetMessagesResponse to the consumer.</p><p>On the other hand, when a NotificationConsumer wants to receive
         the last Notification message sent on a specific Topic, it can do this
-        by sending GetCurrentMessageRequest to <span class="emphasis"><em>QCG
-        Notification</em></span>. Requested Notification will be supplied in
-        the GetCurrentMessageResponse message.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ted"></a>3.3.&nbsp;Topics, TopicExpressions and Dialects</h3></div></div></div><p>Before start-up of a <span class="emphasis"><em>QCG Notification</em></span>
+        by sending GetCurrentMessageRequest to
+        <span class="emphasis"><em>QCG-Notification</em></span>. Requested Notification will be
+        supplied in the GetCurrentMessageResponse message.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="ted"></a>3.3.&nbsp;Topics, TopicExpressions and Dialects</h3></div></div></div><p>Before start-up of a <span class="emphasis"><em>QCG-Notification</em></span>
       service, there should be defined Topic Namespaces in a system. Topic
       Namespaces should be created (usually by Publishers) and delivered to
-      a<span class="emphasis"><em> QCG Notification</em></span> administrator in a form of XML
+      a<span class="emphasis"><em> QCG-Notification</em></span> administrator in a form of XML
       documents. A following record presents a sample Topic Namespace
       identified by
@@ -297 +297 @@
         &lt;/wstop:Topic&gt;
     &lt;/wstop:Topic&gt;                                                                                                                                                              
-&lt;/wstop:TopicNamespace&gt;</pre><p><span class="emphasis"><em>QCG Notification </em></span>supports three types of
+&lt;/wstop:TopicNamespace&gt;</pre><p><span class="emphasis"><em>QCG-Notification </em></span>supports three types of
       dialects: <span class="emphasis"><em>Simple</em></span>, <span class="emphasis"><em>Concrete</em></span> and
       <span class="emphasis"><em>Full</em></span>. If a message refer to Topics, it has to
@@ -309 +309 @@
       and check out examples of methods in the <a class="link" href="#methodsdescription">section 3.4.</a></p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e685"></a>3.4.&nbsp;Extensions</h3></div></div></div><p>The Oasis standard for notifications doesn't define details for
       lower Levels of functionality so an architect of system is obligated to
-      introduce some extensions and clarifications. In the <span class="emphasis"><em>QCG
-      Notification </em></span>scenario there are several messages that have to
-      be expanded with additional information written as embedded XML. Some of
-      these extensions are related with other Oasis standards but some are
-      quite new. Technical details are described in the successive
-      subsections.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e693"></a>3.4.1.&nbsp;TopicExpression</h4></div></div></div><p><span class="emphasis"><em>QCG Notification </em></span>remote peers have to use
+      introduce some extensions and clarifications. In the
+      <span class="emphasis"><em>QCG-Notification </em></span>scenario there are several
+      messages that have to be expanded with additional information written as
+      embedded XML. Some of these extensions are related with other Oasis
+      standards but some are quite new. Technical details are described in the
+      successive subsections.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e693"></a>3.4.1.&nbsp;TopicExpression</h4></div></div></div><p><span class="emphasis"><em>QCG-Notification </em></span>remote peers have to use
         an appropriate TopicExpression XML element. The schema of this element
         is defined according to Oasis standard in<a class="ulink" href="http://docs.oasis-open.org/wsn/b-2.xsd" target="_top"></a><a class="ulink" href="http://docs.oasis-open.org/wsn/b-2.xsd" target="_top">
@@ -323 +323 @@
         with the WSDL document, a @Dialect from the Topic element is
         significant. It is not necessary but preferred to attach the same
-        @Dialect in the TopicExpression element against.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e704"></a>3.4.2.&nbsp;<span class="emphasis"><em>QCG Notification</em></span> Extensions</h4></div></div></div><p><span class="emphasis"><em>QCG Notification</em></span> introduces some extensions
+        @Dialect in the TopicExpression element against.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e704"></a>3.4.2.&nbsp;<span class="emphasis"><em>QCG-Notification</em></span> Extensions</h4></div></div></div><p><span class="emphasis"><em>QCG-Notification</em></span> introduces some extensions
         to WSDL as well as schema documents related to the Oasis standard. The
         following schema defines these extensions. The first three elements
@@ -375 +375 @@
    &lt;/xsd:simpleType&gt;  
 
-&lt;!-- ================= QCG Notification manager : ListPullPoints ================== --&gt;
+&lt;!-- ================= QCG-Notification manager : ListPullPoints ================== --&gt;
 
    &lt;xsd:complexType name="ListSubscriptionsFilter"&gt;
@@ -435 +435 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : ListPublishersRegistrations ================== --&gt;
+&lt;!-- ================= QCG-Notification manager : ListPublishersRegistrations ================== --&gt;
 
    &lt;xsd:complexType name="ListPublishersRegistrationsFilter"&gt;
@@ -494 +494 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : ListPullPoints ================== --&gt;
+&lt;!-- ================= QCG-Notification manager : ListPullPoints ================== --&gt;
 
    &lt;xsd:complexType name="ListPullPointsFilter"&gt;
@@ -554 +554 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : ListTopicNamespaces ================== --&gt;
+&lt;!-- ================= QCG-Notification manager : ListTopicNamespaces ================== --&gt;
     
    &lt;xsd:complexType name="ListTopicNamespacesFilter"&gt;
@@ -596 +596 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : AddTopicNamespace ================== --&gt;
+&lt;!-- ================= QCG-Notification manager : AddTopicNamespace ================== --&gt;
 
    &lt;xsd:element name="AddTopicNamespace"&gt;
@@ -617 +617 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : RemoveTopicNamespace ================== --&gt;
+&lt;!-- ================= QCG-Notification manager : RemoveTopicNamespace ================== --&gt;
 
    &lt;xsd:element name="RemoveTopicNamespace"&gt;
@@ -640 +640 @@
 
 &lt;/xsd:schema&gt;</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e715"></a>3.5.&nbsp;Methods Description</h3></div></div></div><p>The main idea of this chapter is to present the types of messages
-      used in the <span class="emphasis"><em>QCG Notification</em></span> scenario as well as
+      used in the <span class="emphasis"><em>QCG-Notification</em></span> scenario as well as
       introduce how to construct and interpret these messages. The majority of
-      them is two-way style and initiated by <span class="emphasis"><em>QCG
-      Notification</em></span> clients. Exception is the Notify message that is
-      one-way style. In the first phase it is transported from a Publisher to
-      <span class="emphasis"><em>QCG Notification</em></span> and in the second it is
-      transported from <span class="emphasis"><em>QCG Notification</em></span> to subscribed
-      NotificationConsumers.</p><p>All supported by <span class="emphasis"><em>QCG Notification</em></span> message
+      them is two-way style and initiated by
+      <span class="emphasis"><em>QCG-Notification</em></span> clients. Exception is the Notify
+      message that is one-way style. In the first phase it is transported from
+      a Publisher to <span class="emphasis"><em>QCG-Notification</em></span> and in the second
+      it is transported from <span class="emphasis"><em>QCG-Notification</em></span> to
+      subscribed NotificationConsumers.</p><p>All supported by <span class="emphasis"><em>QCG-Notification</em></span> message
       types are presented and explained below.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><div class="itemizedlist"><ul type="disc"><li><p>The key information are thick;</p></li><li><p>A base of the messages structure is a delivered WSDL file,
               however there are also extensions;</p></li><li><p>For all messages it is important to set a correct
               WS-Addressing Action property which should be the same as SOAP
-              Action.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e749"></a>3.5.1.&nbsp;SubscribeRequest</h4></div></div></div><p>SubscribeRequest is sent by a Subscriber to <span class="emphasis"><em>QCG
-        Notification</em></span>. The message should contain information about
-        a NotificationConsumer and an expression defining Topic or Topics that
-        the Subscription will affect. If a message processing is successful, a
-        Subscription is created. It is possible to create many equal
-        Subscriptions by sending numerously the same SubscribeRequest
-        message.</p><pre class="programlisting">SOAP-ENV:Envelope ... &gt;
+              Action.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e749"></a>3.5.1.&nbsp;SubscribeRequest</h4></div></div></div><p>SubscribeRequest is sent by a Subscriber to
+        <span class="emphasis"><em>QCG-Notification</em></span>. The message should contain
+        information about a NotificationConsumer and an expression defining
+        Topic or Topics that the Subscription will affect. If a message
+        processing is successful, a Subscription is created. It is possible to
+        create many equal Subscriptions by sending numerously the same
+        SubscribeRequest message.</p><pre class="programlisting">SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
     &lt;wsa:Action SOAP-ENV:mustUnderstand="1"&gt;
@@ -711 +711 @@
             fault will be returned.</em></span></em></span></p></li><li><p><span class="emphasis"><em>//wsnt:Subscribe/wsnt:ConsumerReference/wsa:Address</em></span></p><p>A Consumer address. It is significant to specify a correct
             prefix (http, https, xmpp). The prefix should be adequate to the
-            expected type of connection between <span class="emphasis"><em>QCG
-            Notification</em></span> and NotificationConsumer(s): http for
-            anonymous, https for ssl-based and xmpp for sending notifications
-            to jabber clients.</p></li><li><p><span class="emphasis"><em>//wsnt:Subscribe/wsnt:Filter</em></span></p><p>In this element, a Subscriber defines filtering parameters
+            expected type of connection between
+            <span class="emphasis"><em>QCG-Notification</em></span> and NotificationConsumer(s):
+            http for anonymous, https for ssl-based and xmpp for sending
+            notifications to jabber clients.</p></li><li><p><span class="emphasis"><em>//wsnt:Subscribe/wsnt:Filter</em></span></p><p>In this element, a Subscriber defines filtering parameters
             to the Subscription being created. In other words, it identifies a
             type of Notifications that should be forwarded to the selected
@@ -740 +740 @@
             suggestion for the termination time of the Subscription being
             created (expressed as a local time with timezone). If not present,
-            the termination time is determined automatically - <span class="emphasis"><em>QCG
-            Notification <span class="emphasis"><em>specify a default time
+            the termination time is determined automatically -
+            <span class="emphasis"><em>QCG-Notification <span class="emphasis"><em>specify a default time
             period</em></span></em></span> for the Subscription to be
             valid.</p></li><li><p><span class="emphasis"><em>//wsnt:Subscribe/smn-ext:XSLTTranslation</em></span></p><p>An optional element. Inside the XSLTTranslation a Subscriber
@@ -748 +748 @@
             (for example user readable). Note that an actual XSLT document
             should be enclosed in &lt;![CDATA[ and ]]&gt; markers.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e856"></a>3.5.2.&nbsp;SubscribeResponse</h4></div></div></div><p>In answer on SubscribeRequest there is sent the
-        SubscribeResponse message. <span class="emphasis"><em>QCG Notification</em></span>
+        SubscribeResponse message. <span class="emphasis"><em>QCG-Notification</em></span>
         deliver in this message a reference to the created Subscription. This
         ID can be used for manipulation and to remove the Subscription.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -777 +777 @@
             NotificationProducer/SubscribeResponse. <span class="emphasis"><em>If differ, a
             fault will be returned.</em></span></em></span></p></li><li><p><span class="emphasis"><em>//wsnt:SubscribeResponse/wsnt:SubscriptionReference/wsa:Address</em></span></p><p>An address of a SubscriptionManager interface. In the
-            current solution it is the <span class="emphasis"><em>QCG Notification</em></span>
+            current solution it is the <span class="emphasis"><em>QCG-Notification</em></span>
             service address.</p></li><li><p><span class="emphasis"><em>//wsnt:SubscribeResponse/wsnt:SubscriptionReference/</em></span></p><p><span class="emphasis"><em>wsa:ReferenceParameters/SubscriptionID</em></span></p><p>An extensive element in xsd:any that contains Subscription
             ID. At this time it is at most 32 char long string.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e904"></a>3.5.3.&nbsp;RenewRequest</h4></div></div></div><p>When a Subscriber wants to renew a Subscription, it can send the
-        RenewRequest message to <span class="emphasis"><em>QCG Notification</em></span>. The
+        RenewRequest message to <span class="emphasis"><em>QCG-Notification</em></span>. The
         message should contain the Subscription ID element and a new
         termination time suggesation.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -830 +830 @@
             SubscriptionManager/RenewResponse. <span class="emphasis"><em>If differ, a fault
             will be returned.</em></span></em></span></p></li><li><p><span class="emphasis"><em>//wsnt:RenewResponse/wsnt:TerminationTime</em></span></p><p>A new termination time for the renewed Subscription
-            (expressed as UTC Time).</p></li></ul></div><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>//wsnt:RenewResponse/wsnt:CurrentTime</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>A </em></span>QCG
-            Notification's</em></span> time when the Subscription was renewing
-            (expressed as UTC Time).</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e989"></a>3.5.5.&nbsp;UnsubscribeRequest</h4></div></div></div><p>When a Subscriber wants to terminate a Subscription, it has to
-        send the UnsubscribeRequest message to <span class="emphasis"><em>QCG
-        Notification</em></span>. The parameter attached to this request is a
-        Subscription ID.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
+            (expressed as UTC Time).</p></li></ul></div><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>//wsnt:RenewResponse/wsnt:CurrentTime</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>A
+            </em></span>QCG-Notification's</em></span> time when the
+            Subscription was renewing (expressed as UTC Time).</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e989"></a>3.5.5.&nbsp;UnsubscribeRequest</h4></div></div></div><p>When a Subscriber wants to terminate a Subscription, it has to
+        send the UnsubscribeRequest message to
+        <span class="emphasis"><em>QCG-Notification</em></span>. The parameter attached to this
+        request is a Subscription ID.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
     &lt;wsa:Action SOAP-ENV:mustUnderstand="1"&gt;
@@ -871 +871 @@
             SubscriptionManager/UnsubscribeResponse. <span class="emphasis"><em>If differ, a
             fault will be returned.</em></span></em></span></p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e1043"></a>3.5.7.&nbsp;RegisterPublisherRequest</h4></div></div></div><p>In order to sending Notifications, a Publisher can be obligated
-        to register himself previosly in <span class="emphasis"><em>QCG
-        Notification</em></span>. For this purpose, it sends the
-        RegisterPublisherRequest message to <span class="emphasis"><em>QCG
-        Notification</em></span>.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
+        to register himself previosly in
+        <span class="emphasis"><em>QCG-Notification</em></span>. For this purpose, it sends the
+        RegisterPublisherRequest message to
+        <span class="emphasis"><em>QCG-Notification</em></span>.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
     &lt;wsa:Action SOAP-ENV:mustUnderstand="1"&gt;
@@ -900 +900 @@
             suggestion for the termination time of the Registration being
             created (expressed as a local time with timezone). If not present,
-            the termination time is determined automatically - <span class="emphasis"><em>QCG
-            Notification <span class="emphasis"><em>specify the default time
+            the termination time is determined automatically -
+            <span class="emphasis"><em>QCG-Notification <span class="emphasis"><em>specify the default time
             period</em></span></em></span> for the Registration to be valid.
             Every Notify message renews the termination time.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e1096"></a>3.5.8.&nbsp;RegisterPublisherResponse</h4></div></div></div><p>In a response to a successful registration process,
-        <span class="emphasis"><em>QCG Notification</em></span> sends RegisterPublisherResponse.
+        <span class="emphasis"><em>QCG-Notification</em></span> sends RegisterPublisherResponse.
         This message contains a reference to the created Registration. The
         attached ID is necessary to send any Notification message.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -932 +932 @@
             <span class="emphasis"><em>If differ, a fault will be
             returned.</em></span></em></span></p></li><li><p><span class="emphasis"><em>//wsnbr:RegisterPublisherResponse/wsnbr:PublisherRegistrationReference/wsa:Address</em></span></p><p>An address of a PublisherRegistration Manager interface. In
-            the current solution it is the <span class="emphasis"><em>QCG
-            Notification</em></span> service address.</p></li><li><p><span class="emphasis"><em>//wsnbr:RegisterPublisherResponse/wsnbr:PublisherRegistrationReference/wsa:ReferenceParameters/RegisterPublisherID</em></span></p><p>An extensive element in xsd:any that contains a Publisher
+            the current solution it is the
+            <span class="emphasis"><em>QCG-Notification</em></span> service address.</p></li><li><p><span class="emphasis"><em>//wsnbr:RegisterPublisherResponse/wsnbr:PublisherRegistrationReference/wsa:ReferenceParameters/RegisterPublisherID</em></span></p><p>An extensive element in xsd:any that contains a Publisher
             Registration ID. It defines a session that is created after
             registration and removed by sending the DestroyRegistration
@@ -990 +990 @@
             shorter than 4096 bytes.</p></li><li><p><span class="emphasis"><em>//wsnt:Notify/smn-ext:RegisterPublisherID</em></span></p><p>A Publisher Registration ID that was received in the
             RegisterPublisherResponse message.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e1225"></a>3.5.10.&nbsp;DestroyRegistrationRequest</h4></div></div></div><p>A Publisher can terminate a Registration by sending the
-        DestroyRegistrationRequest message to <span class="emphasis"><em>QCG
-        Notification</em></span>. The parameter attached to this request is a
-        Publisher Registration ID.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
+        DestroyRegistrationRequest message to
+        <span class="emphasis"><em>QCG-Notification</em></span>. The parameter attached to this
+        request is a Publisher Registration ID.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
     &lt;wsa:Action SOAP-ENV:mustUnderstand="1"&gt;
@@ -1030 +1030 @@
             returned.</em></span></em></span></p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e1279"></a>3.5.12.&nbsp;CreatePullPointRequest</h4></div></div></div><p>In scenarios where the pull-style of notifications delivery is
         needed, Subscribers can create PullPoints. To do this, a Subscriber
-        sends the CreatePullPointRequest message to <span class="emphasis"><em>QCG Notification
+        sends the CreatePullPointRequest message to <span class="emphasis"><em>QCG-Notification
         PullPoint</em></span>.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
@@ -1204 +1204 @@
             "http://docs.oasis-open.org/wsn/t-1/TopicExpression/Concrete",
             "http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full".
-            </em></span></p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e1532"></a>3.5.19.&nbsp;GetCurrentMessageResponse</h4></div></div></div><p>In a response to GetCurrentMessageRequest <span class="emphasis"><em>QCG
-        Notification</em></span> prepares GetCurrentMessageResponse. This
-        message includes the content of the last Notification
-        GetCurrentMessageRequest refers to.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
+            </em></span></p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e1532"></a>3.5.19.&nbsp;GetCurrentMessageResponse</h4></div></div></div><p>In a response to GetCurrentMessageRequest
+        <span class="emphasis"><em>QCG-Notification</em></span> prepares
+        GetCurrentMessageResponse. This message includes the content of the
+        last Notification GetCurrentMessageRequest refers to.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
     &lt;wsa:Action SOAP-ENV:mustUnderstand="1"&gt;
@@ -1239 +1239 @@
             differ, a fault will be returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/smn-ext:GetCurrentMessage</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>The element that contains current
             Notification and information related to this
-            notification.</em></span></em></span></p></li><li><p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/smn-ext:GetCurrentMessage/smn-ext:NotifyTime</em></span></p><p>The time when notification was received by <span class="emphasis"><em>QCG
-            Notification</em></span>; expressed as universal time (UTC).</p></li><li><p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/wsnt:ProducerReference/wsa:Address</em></span></p><p>A Notification producer (Publisher) address.</p></li><li><p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/smn-ext:GetCurrentMessage/smn-ext:Message</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>An extensive element. The content of
+            notification.</em></span></em></span></p></li><li><p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/smn-ext:GetCurrentMessage/smn-ext:NotifyTime</em></span></p><p>The time when notification was received by
+            <span class="emphasis"><em>QCG-Notification</em></span>; expressed as universal time
+            (UTC).</p></li><li><p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/wsnt:ProducerReference/wsa:Address</em></span></p><p>A Notification producer (Publisher) address.</p></li><li><p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/smn-ext:GetCurrentMessage/smn-ext:Message</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>An extensive element. The content of
             this element is the last Notification message published to the
             Topic specified in GetCurrentMessageRequest. Currently supported
             are messages shorter than 4096 bytes.</em></span></em></span></p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e1598"></a>3.5.20.&nbsp;ListSubscriptions</h4></div></div></div><p>The first method from the the group of administrative methods.
         It may be invoked to get an information about available subscriptions
-        in the <span class="emphasis"><em>QCG Notification</em></span> service. The method
+        in the <span class="emphasis"><em>QCG-Notification</em></span> service. The method
         consists of various filtering parameters.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
@@ -1295 +1296 @@
             <span class="emphasis"><em>http://schemas.qoscosgrid.org/ntf/2011/04/QCGNotificationManager/ListSubscriptionsRequest.
             <span class="emphasis"><em>If differ, a fault will be
-            returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListSubscriptions/smn-ext:Filter</em></span></p><p>The expanding element from <span class="emphasis"><em>QCG
-            Notification</em></span> schema. It consists of a number of
-            optional filtering parameters.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListSubscriptions/smn-ext:Filter/SubscriptionID</em></span></p><p>A Subscription identifier. Thanks to this parameter
+            returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListSubscriptions/smn-ext:Filter</em></span></p><p>The expanding element from
+            <span class="emphasis"><em>QCG-Notification</em></span> schema. It consists of a
+            number of optional filtering parameters.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListSubscriptions/smn-ext:Filter/SubscriptionID</em></span></p><p>A Subscription identifier. Thanks to this parameter
             Subscriptions may be simply filtered on the basis of Subscription
             ID. The value is at most 32 char long string.</p></li><li><p><span class="emphasis"><em>/smn-ext:ListSubscriptions/smn-ext:Filter/smn-ext:ConsumerReference/wsa:Address</em></span></p><p>The parameter that enables filtering Subscriptions based on
@@ -1359 +1360 @@
             <span class="emphasis"><em>If differ, a fault will be
             returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListSubscriptionsResponse</em></span></p><p>This element contains a list of subscriptions received from
-            <span class="emphasis"><em>QCG Notification</em></span> (propably also filtered on
+            <span class="emphasis"><em>QCG-Notification</em></span> (propably also filtered on
             the basis of the smn-ext:Filter element sent in
             ListSubscriptions).</p></li><li><p><span class="emphasis"><em>//smn-ext:ListSubscriptionsResponse/smn-ext:Subscription</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>The element provides information about a
@@ -1407 +1408 @@
             <span class="emphasis"><em>http://schemas.qoscosgrid.org/ntf/2011/04/QCGNotificationManager/ListPublishersRegistrationsRequest.
             <span class="emphasis"><em>If differ, a fault will be
-            returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPublishersRegistrations/smn-ext:Filter</em></span></p><p>The element from <span class="emphasis"><em>QCG Notification</em></span>
+            returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPublishersRegistrations/smn-ext:Filter</em></span></p><p>The element from <span class="emphasis"><em>QCG-Notification</em></span>
             schema. It consists of optional filtering parameters.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPublishersRegistrations/smn-ext:Filter/PublisherRegistrationID</em></span></p><p>A Publisher Registration identifier. This parameter enables
             filtering of Publisher Registrations based on Publishers
             Registrations ID. The value is at most 32 char long string.</p></li><li><p><span class="emphasis"><em>/smn-ext:ListPublishersRegistrations/smn-ext:Filter/smn-ext:PublisherReference/wsa:Address</em></span></p><p>This element enables filtering based on an addresses of
             Publishers. Depending on configuration, this address may be held
-            in the <span class="emphasis"><em>QCG Notification</em></span> service as an address
+            in the <span class="emphasis"><em>QCG-Notification</em></span> service as an address
             sent in the From element of WSA Header of RegisterPublisher
             message or an IP address of a Publisher.</p></li><li><p><span class="emphasis"><em>/smn-ext:ListPublishersRegistrations/smn-ext:Filter/smn-ext:CreationTimeMin</em></span></p><p><span class="emphasis"><em>/smn-ext:ListPublishersRegistrations/smn-ext:Filter/smn-ext:CreationTimeMax</em></span></p><p><span class="emphasis"><em>/smn-ext:ListPublishersRegistrations/smn-ext:Filter/smn-ext:TerminationTimeMin
@@ -1457 +1458 @@
             <span class="emphasis"><em>If differ, a fault will be
             returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPublishersRegistrationsResponse</em></span></p><p>The element contains a list of Publishers Registrations
-            received from <span class="emphasis"><em>QCG Notification</em></span> (propably also
+            received from <span class="emphasis"><em>QCG-Notification</em></span> (propably also
             filtered on the basis of the smn-ext:Filter element sent in a
             ListPublishersRegistrations message).</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPublishersRegistrationsResponse/smn-ext:PublisherRegistration</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>The element provides information about a
@@ -1504 +1505 @@
             <span class="emphasis"><em>http://schemas.qoscosgrid.org/ntf/2011/04/QCGNotificationManager/ListPullPointsRequest.
             <span class="emphasis"><em>If differ, a fault will be
-            returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPullPoints/smn-ext:Filter</em></span></p><p>The element from <span class="emphasis"><em>QCG Notification</em></span>
+            returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPullPoints/smn-ext:Filter</em></span></p><p>The element from <span class="emphasis"><em>QCG-Notification</em></span>
             schema. It consists of optional filtering parameters.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPullPoints/smn-ext:Filter/smn-ext:PullPointID</em></span></p><p>A PullPoint identifier. This parameter enables filtering of
             PullPoints based on PullPoint ID. The value is at most 32 char
             long string.</p></li><li><p><span class="emphasis"><em>/smn-ext:ListPullPoints/smn-ext:Filter/smn-ext:PullPointReference/wsa:Address</em></span></p><p>This element enables filtering based on an addresses of
             PullPoint. The PullPoint address is assigned after creation of a
-            PullPoint in <span class="emphasis"><em>QCG Notification</em></span> and returned
+            PullPoint in <span class="emphasis"><em>QCG-Notification</em></span> and returned
             inside CreatePullPointResponse.</p></li><li><p><span class="emphasis"><em>/smn-ext:ListPullPoints/smn-ext:Filter/smn-ext:CreationTimeMin</em></span></p><p><span class="emphasis"><em>/smn-ext:ListPullPoints/smn-ext:Filter/smn-ext:CreationTimeMax</em></span></p><p><span class="emphasis"><em>/smn-ext:ListPullPoints/smn-ext:Filter/smn-ext:TerminationTimeMin
             </em></span></p><p><span class="emphasis"><em>/smn-ext:ListPullPoints/smn-ext:Filter/smn-ext:TerminationTimeMax</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>The elements define filtering parameters
@@ -1553 +1554 @@
             <span class="emphasis"><em>If differ, a fault will be
             returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPullPointsResponse</em></span></p><p>The element contains a list of PullPoints received from
-            <span class="emphasis"><em>QCG Notification</em></span> (propably also previously
+            <span class="emphasis"><em>QCG-Notification</em></span> (propably also previously
             filtered on the basis of the smn-ext:Filter element sent in a
             ListPullPoints message).</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPullPointsResponse/smn-ext:PullPoint</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>The element provides particular
@@ -1582 +1583 @@
             <span class="emphasis"><em>http://schemas.qoscosgrid.org/ntf/2011/04/QCGNotificationManager/ListTopicNamespacesRequest.
             <span class="emphasis"><em>If differ, a fault will be
-            returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListTopicNamespaces/smn-ext:Filter</em></span></p><p>The element from <span class="emphasis"><em>QCG Notification</em></span>
+            returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListTopicNamespaces/smn-ext:Filter</em></span></p><p>The element from <span class="emphasis"><em>QCG-Notification</em></span>
             schema. It consists of optional filtering parameters.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListPullPoints/smn-ext:Filter/smn-ext:targetNamespace</em></span></p><p>A targetNamespace of a TopicNamespace. This parameter
             enables filtering of TopicNamespaces based on their
@@ -1619 +1620 @@
             <span class="emphasis"><em>If differ, a fault will be
             returned</em></span></em></span>.</p></li><li><p><span class="emphasis"><em>//smn-ext:ListTopicNamespacesResponse</em></span></p><p>The element contains a list of information about
-            TopicNamespaces received from <span class="emphasis"><em>QCG
-            Notification</em></span> (optionally filtered on the basis of the
-            smn-ext:Filter element sent in a ListTopicNamespaces
+            TopicNamespaces received from
+            <span class="emphasis"><em>QCG-Notification</em></span> (optionally filtered on the
+            basis of the smn-ext:Filter element sent in a ListTopicNamespaces
             message).</p></li><li><p><span class="emphasis"><em>//smn-ext:ListTopicNamespacesResponse/smn-ext:TopicNamespace</em></span></p><p><span class="emphasis"><em><span class="emphasis"><em>The element provides particular
             information about a single
@@ -1627 +1628 @@
             value should be compliant with anyURI.</p></li><li><p><span class="emphasis"><em>/smn-ext:ListTopicNamespacesResponse/smn-ext:TopicNamespace/smn-ext:Topic</em></span></p><p>A list of topics belonging to a TopicNamespace. Each listed
             topic is proceded by a targetNamespace so it is uniq.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e2206"></a>3.5.28.&nbsp;AddTopicNamespace</h4></div></div></div><p>An administrative method. The method may be invoked to add a new
-        TopicNamespace to the <span class="emphasis"><em>IQCG Notification</em></span>.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
+        TopicNamespace to the <span class="emphasis"><em>IQCG-Notification</em></span>.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
     &lt;wsa:Action SOAP-ENV:mustUnderstand="1"&gt;
@@ -1655 +1656 @@
             WS-Topics schema.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e2243"></a>3.5.29.&nbsp;AddTopicNamespaceResponse</h4></div></div></div><p>A response message to a AddTopicNamespaceRequest. It is empty
         and only confirms successfull addition of a TopicNamespace to the
-        <span class="emphasis"><em>QCG Notification</em></span> service. </p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
+        <span class="emphasis"><em>QCG-Notification</em></span> service. </p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
     &lt;wsa:Action SOAP-ENV:mustUnderstand="1"&gt;
@@ -1670 +1671 @@
             <span class="emphasis"><em>http://schemas.qoscosgrid.org/ntf/2011/04/QCGNotificationManager/AddTopicNamespaceResponse.</em></span><span class="emphasis"><em><span class="emphasis"><em>
             If differ, a fault will be returned.</em></span></em></span></p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e2268"></a>3.5.30.&nbsp;RemoveTopicNamespace</h4></div></div></div><p>The next administrative method. It is used to remove a
-        TopicNamespace from the <span class="emphasis"><em>QCG Notification</em></span> system.
+        TopicNamespace from the <span class="emphasis"><em>QCG-Notification</em></span> system.
         Note that the removing may be only temporary (active to the restart of
         the system) if the TopicNamespace file is protected by disabling write
@@ -1708 +1709 @@
 &lt;/SOAP-ENV:Envelope&gt;</pre><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>//SOAP-ENV:Header/wsa:Action</em></span></p><p>For this message should always be:
             <span class="emphasis"><em>http://schemas.qoscosgrid.org/ntf/2011/04/QCGNotificationManager/RemoveTopicNamespaceResponse.</em></span><span class="emphasis"><em><span class="emphasis"><em>
-            If differ, a fault will be returned.</em></span></em></span></p></li></ul></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e2324"></a>4.&nbsp;Administration Guide of <span class="emphasis"><em>QCG
-    Notification</em></span></h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e2329"></a>4.1.&nbsp;Prerequisites</h3></div></div></div><p>In order to build and install <span class="emphasis"><em>QCG
-      Notification</em></span>, an administrator has to appropriately configure
-      operating system. There is some dependencies to external software that
-      should be satisfied.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e2337"></a>4.1.1.&nbsp;QCG Core library</h4></div></div></div><p><span class="emphasis"><em>QCG Notification</em></span> is based on the
+            If differ, a fault will be returned.</em></span></em></span></p></li></ul></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="d0e2324"></a>4.&nbsp;Administration Guide of
+    <span class="emphasis"><em>QCG-Notification</em></span></h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e2329"></a>4.1.&nbsp;Prerequisites</h3></div></div></div><p>In order to build and install
+      <span class="emphasis"><em>QCG-Notification</em></span>, an administrator has to
+      appropriately configure operating system. There is some dependencies to
+      external software that should be satisfied.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e2337"></a>4.1.1.&nbsp;QCG Core library</h4></div></div></div><p><span class="emphasis"><em>QCG-Notification</em></span> is based on the
         <span class="emphasis"><em>QCG Core</em></span> library developed by the
         <span class="emphasis"><em>QCG</em></span> team. QCG Core is a common utility library
         providing set of basic modules used by other components within QCG
         Project. For more information see QCG Core documentation.</p><p>The QCG Core library should be properly configured prior to the
-        preparation of <span class="emphasis"><em>QCG Notification</em></span>.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e2355"></a>4.2.&nbsp;Building</h3></div></div></div><p>Before you compile <span class="emphasis"><em>QCG Notification</em></span>, you need
+        preparation of <span class="emphasis"><em>QCG-Notification</em></span>.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e2355"></a>4.2.&nbsp;Building</h3></div></div></div><p>Before you compile <span class="emphasis"><em>QCG-Notification</em></span>, you need
       to run the configuration script first. It will try to check if all the
       requirements are met and whether needed third party software is
       available. Simply type the following command:</p><pre class="programlisting">$ ./configure</pre><p>There are several options that can be passed to the script. If you
       type the --help parameter you will see all available options. These are
-      the most important ones:</p><div class="itemizedlist"><ul type="disc"><li><p>--prefix=DIR</p><p>specifies directory where <span class="emphasis"><em>QCG
-            Notification</em></span> will be installed.</p><p>Default: /opt/qcg</p></li><li><p>--with-qcg-core=PFX</p><p>specifies where QCG Core library is installed.</p><p>Default: no default value. qcg-core-config script is used to
+      the most important ones:</p><div class="itemizedlist"><ul type="disc"><li><p>--prefix=DIR</p><p>specifies directory where
+            <span class="emphasis"><em>QCG-Notification</em></span> will be installed.</p><p>Default: /opt/qcg</p></li><li><p>--with-qcg-core=PFX</p><p>specifies where QCG Core library is installed.</p><p>Default: no default value. qcg-core-config script is used to
             determine necessary paths</p></li><li><p>--with-client</p><p>Determine if the test client program should be build</p></li><li><p>--with-consumer</p><p>Determine if the test NotificationConsumer service should be
             build</p></li><li><p>--with-addressing-handler</p><p>Determine if the test Web Services Addressing handler
             service should be build</p></li></ul></div><p>After successful configuration step, compiling and
-      installing of <span class="emphasis"><em>QCG Notification</em></span> should be a
+      installing of <span class="emphasis"><em>QCG-Notification</em></span> should be a
       straightforward process:</p><pre class="programlisting">$ make
 $ make install</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The installation step should be done either as
-        <code class="filename">root</code> or the user that will execute <span class="emphasis"><em>QCG
-        Notification</em></span> service, assuming he has necessary privileges
-        to do this.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e2416"></a>4.3.&nbsp;Creating database for <span class="emphasis"><em>QCG Notification</em></span> - the
-      PostgreSQL example</h3></div></div></div><p><span class="emphasis"><em>QCG Notification</em></span> can be run in two basic
+        <code class="filename">root</code> or the user that will execute
+        <span class="emphasis"><em>QCG-Notification</em></span> service, assuming he has
+        necessary privileges to do this.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e2416"></a>4.3.&nbsp;Creating database for <span class="emphasis"><em>QCG-Notification</em></span> - the
+      PostgreSQL example</h3></div></div></div><p><span class="emphasis"><em>QCG-Notification</em></span> can be run in two basic
       modes related to the database connection: without database or with
       database. Although the first option is sufficient for simple scenarios,
-      it reduces the overall functionality of the <span class="emphasis"><em>QCG
-      Notification</em></span> (e.g. disable PullPoints). Therefore using the
-      database is recomended and can be often essential.</p><p>You will find more detailed description of administrative tasks in
+      it reduces the overall functionality of the
+      <span class="emphasis"><em>QCG-Notification</em></span> (e.g. disable PullPoints).
+      Therefore using the database is recomended and can be often
+      essential.</p><p>You will find more detailed description of administrative tasks in
       PostgreSQL tutorial. However, the following basic steps are needed to
-      set up a database and appropriate tables for <span class="emphasis"><em>QCG
-      Notification</em></span> assuming that you have already setup a
-      PostgreSQL database:</p><p>By default, the first database user created will also be named
+      set up a database and appropriate tables for
+      <span class="emphasis"><em>QCG-Notification</em></span> assuming that you have already
+      setup a PostgreSQL database:</p><p>By default, the first database user created will also be named
       <code class="filename">postgres</code>. In order to create a user for
-      <span class="emphasis"><em>QCG Notification</em></span> usage, for instance
+      <span class="emphasis"><em>QCG-Notification</em></span> usage, for instance
       <code class="filename">qcg-ntf</code>, type the following:</p><pre class="programlisting">$ createuser -U postgres -W qcg-ntf -P</pre><p>If you use a password then remember to supply it in
       <code class="filename">qcg-ntfd.xml</code> configuration file. Create a database,
       for example <code class="filename">qcg-ntf</code>, by typing the following
       command:</p><pre class="programlisting">$ createdb qcg-ntf</pre><p>and set up a table structure using the
-      <code class="filename">qcg-ntf-psql.sql</code> file from <span class="emphasis"><em>QCG
-      Notification</em></span> distribution - it can be found in
+      <code class="filename">qcg-ntf-psql.sql</code> file from
+      <span class="emphasis"><em>QCG-Notification</em></span> distribution - it can be found in
       <code class="filename">/opt/qcg/share/tools</code> directory by default.</p><pre class="programlisting">$ psql -d qcg-ntf -U qcg-ntf &lt; qcg-ntf-psql.sql</pre><p>Eventually you need to add this database as the ODBC Data Source
       Name. You can do this by editing system-wide configuration file (e.g.
       <code class="filename">/etc/odbc.ini)</code> or <code class="filename">.odbc.ini</code> in
-      home directory of the user that will be used to start <span class="emphasis"><em>QCG
-      Notification</em></span>.</p><p>Assuming that ODBC are installed in /usr/local/lib and the choosed
-      name for <span class="emphasis"><em>QCG Notification</em></span> is
+      home directory of the user that will be used to start
+      <span class="emphasis"><em>QCG-Notification</em></span>.</p><p>Assuming that ODBC are installed in /usr/local/lib and the choosed
+      name for <span class="emphasis"><em>QCG-Notification</em></span> is
       <code class="filename">qcg-ntf</code> the configuration file should looks
       simmilar to the following:</p><pre class="programlisting">[qcg-ntf]
-Description     = QCG Notification database
+Description     = QCG-Notification database
 Driver        = /usr/local/lib/libodbcpsql.so
 Setup         = /usr/local/lib/libodbcpsqlS.so
@@ -1771 +1773 @@
 DebugFile       = odbc.debug</pre><p>You can also try some GUI tools to set up and manage ODBC and
       databases. Check out if the following tools are available on your
-      machine:</p><pre class="programlisting">$ DataManager</pre><pre class="programlisting">$ ODBCConfig</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuration"></a>5.&nbsp;Configuration of <span class="emphasis"><em>QCG Notification</em></span></h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e2506"></a>5.1.&nbsp;Configuration File: <code class="filename">qcg-ntfd.xml</code></h3></div></div></div><pre class="programlisting">&lt;sm:QCGCore
+      machine:</p><pre class="programlisting">$ DataManager</pre><pre class="programlisting">$ ODBCConfig</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuration"></a>5.&nbsp;Configuration of <span class="emphasis"><em>QCG-Notification</em></span></h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e2506"></a>5.1.&nbsp;Configuration File: <code class="filename">qcg-ntfd.xml</code></h3></div></div></div><pre class="programlisting">&lt;sm:QCGCore
   xmlns:sm="http://schemas.qoscosgrid.org/core/2011/04/config"
   xmlns="http://schemas.qoscosgrid.org/ntf/2011/04/config"
@@ -1783 +1785 @@
     &lt;/sm:ModuleManager&gt;
 
-    &lt;sm:Service xsi:type="ntfd" description="QCG Notification"&gt;
+    &lt;sm:Service xsi:type="ntfd" description="QCG-Notification"&gt;
       &lt;sm:Logger&gt;
         &lt;sm:Filename&gt;/opt/qcg/var/log/qcg-ntf/qcg-ntfd.log&lt;/sm:Filename&gt;
@@ -1881 +1883 @@
           anonymous communication and sm:atc_transport_https for SSL based
           communication).</p></li><li><p><span class="emphasis"><em>//sm:Service/sm:Module/[@type=smn:ntf-publisher*]</em></span></p><p>Initialization and configuration of the modules for the
-          Publisher side of <span class="emphasis"><em>QCG Notification</em></span>. The
+          Publisher side of <span class="emphasis"><em>QCG-Notification</em></span>. The
           following modules are currently supported:</p><div class="itemizedlist"><ul type="circle"><li><p>smn:ntf-publisher-gsoap-anonymous for anonymous SOAP
               communication;</p></li><li><p>smn:ntf-publisher-gsoap-ssl for SSL based SOAP
               communication;</p></li><li><p>smn:ntf-publisher-xmpp for XMPP communication;</p></li><li><p>smn:ntf-publisher-smtp for SMTP communication;</p></li></ul></div><p>For details see the <a class="link" href="#moduleoptions" title="5.2.&nbsp;Module configuration">Section
           5.2</a>.</p></li><li><p><span class="emphasis"><em>//smn:Core/smn:NotificationsVar
-          </em></span>[smn:NotificationsVarType]</p><p>Various notification settings closely related to QCG
-          Notification service implementation.</p></li><li><p><span class="emphasis"><em>//smn:Core/smn:NotificationsVar/smn:TopicNsDir
+          </em></span>[smn:NotificationsVarType]</p><p>Various notification settings closely related to
+          QCG-Notification service implementation.</p></li><li><p><span class="emphasis"><em>//smn:Core/smn:NotificationsVar/smn:TopicNsDir
           <span class="emphasis"><em>[string]</em></span></em></span></p><p>Location of the directory with files containing Topic
           definitions.</p></li><li><p><span class="emphasis"><em>//smn:Core/smn:NotificationsVar/smn:StrictCorrectnessCheckingEnabled</em></span>
@@ -1965 +1967 @@
           then this option is disabled. Default: 5</p></li><li><p><span class="emphasis"><em>//smn:Core/Database/DatabaseEnabled
           <span class="emphasis"><em>[boolean]</em></span></em></span></p><p>true, false - determines if a database should be enabled; in
-          the simplest configuration, <span class="emphasis"><em>QCG Notification</em></span>
+          the simplest configuration, <span class="emphasis"><em>QCG-Notification</em></span>
           can be used also without a database connection, however many options
           will be then unavailable. Default: true</p></li><li><p><span class="emphasis"><em>//smn:Core/Database/DSN
@@ -1973 +1975 @@
           <span class="emphasis"><em>[string]</em></span></em></span></p><p>A password for a database user.</p></li><li><p><span class="emphasis"><em>//smn:Core/Database/CleanAtStart
           <span class="emphasis"><em>[boolean]</em></span></em></span></p><p>true, false - determines whether all information stored in a
-          database should be cleaned at starting of the QCG Notification
+          database should be cleaned at starting of the QCG-Notification
           service.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="moduleoptions"></a>5.2.&nbsp;Module configuration</h3></div></div></div><p>Modules are located in the PREFIX/*/lib/modules directories and
-      are loaded during the<span class="emphasis"><em> QCG Notification</em></span> run time.
+      are loaded during the<span class="emphasis"><em> QCG-Notification</em></span> run time.
       Module definitions are specified in appropriate sections of the
       configuration file.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="d0e2838"></a>5.2.1.&nbsp;Publisher modules</h4></div></div></div><p>As it was discussed in the previous sections, in a typical
@@ -1981 +1983 @@
         and notification channels that need to be setup. The first one is a
         communication channel between Subscriber/Publisher clients and
-        <span class="emphasis"><em>QCG Notification. </em></span>This type of communication is
+        <span class="emphasis"><em>QCG-Notification. </em></span>This type of communication is
         currently completely based on QCG Core library.</p><p>The second type is an outgoing communication between
-        <span class="emphasis"><em>QCG Notification</em></span> and NotificationConsumers and it
-        is particular for <span class="emphasis"><em>QCG Notification</em></span>. In this
-        situation <span class="emphasis"><em>QCG Notification</em></span> plays a role of a
+        <span class="emphasis"><em>QCG-Notification</em></span> and NotificationConsumers and it
+        is particular for <span class="emphasis"><em>QCG-Notification</em></span>. In this
+        situation <span class="emphasis"><em>QCG-Notification</em></span> plays a role of a
         Notification Publisher. At this time, supported modules for this
         channel utilize a Web Service interface, XMPP interface and SMTP
@@ -2079 +2081 @@
                   <span class="emphasis"><em>[string]</em></span></em></span></p><p>Used to enable encryption. The only supported type of
                   encryption is "TLS". Optional element, if not present,
-                  encryption will be switched off. </p></li><li><p><span class="emphasis"><em>//smn:TrutedCAFile
+                  encryption will be switched off.</p></li><li><p><span class="emphasis"><em>//smn:TrutedCAFile
                   <span class="emphasis"><em>[string]</em></span></em></span></p><p>A path to the file with trusted CAs certificates.
                   Optional element.</p></li><li><p><span class="emphasis"><em>//smn:TrutedCAPath
@@ -2092 +2094 @@
                   false.</p></li><li><p><span class="emphasis"><em>//smn:SendTimeout
                   <span class="emphasis"><em>[int]</em></span></em></span></p><p>The timeout in seconds for stall on the send function.
-                  Optional element, default is 10.</p></li></ul></div></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e3097"></a>5.3.&nbsp;WS-Topics management</h3></div></div></div><p>In the current release, a topics management in <span class="emphasis"><em>QCG
-      Notification</em></span> is relatively simple. The first step is a
-      preparation of an XML document with a Topic Namespace definition. This
-      step can be done by one of the peers cooperating with <span class="emphasis"><em>QCG
-      Notification</em></span>. Then the document should be delivered to the
-      computer where <span class="emphasis"><em>QCG Notification</em></span> is installed. It
-      can be done in two ways: the document may be copied manually by QCG
-      Notification administrator to TopicNamespaces directory in prior to
-      <span class="emphasis"><em>a QCG Notification</em></span> startup or it can be send
-      through the <span class="emphasis"><em>QCG Notification</em></span> interface when
-      <span class="emphasis"><em>QCG Notification</em></span> is already runing. In the last
+                  Optional element, default is 10.</p></li></ul></div></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e3097"></a>5.3.&nbsp;WS-Topics management</h3></div></div></div><p>In the current release, a topics management in
+      <span class="emphasis"><em>QCG-Notification</em></span> is relatively simple. The first
+      step is a preparation of an XML document with a Topic Namespace
+      definition. This step can be done by one of the peers cooperating with
+      <span class="emphasis"><em>QCG-Notification</em></span>. Then the document should be
+      delivered to the computer where <span class="emphasis"><em>QCG-Notification</em></span> is
+      installed. It can be done in two ways: the document may be copied
+      manually by QCG-Notification administrator to TopicNamespaces directory
+      in prior to <span class="emphasis"><em>a QCG-Notification</em></span> startup or it can be
+      send through the <span class="emphasis"><em>QCG-Notification</em></span> interface when
+      <span class="emphasis"><em>QCG-Notification</em></span> is already runing. In the last
       case, the TopicNamespaces are stored also in a files in TopicNamespace
       directory so they can be automatically loaded after restart of the
@@ -2108 +2110 @@
       unwanted removal by unseting write permissions for a certain
       file.</p><p>An XML document describing a sample topic namespace is presented
-      in the <a class="link" href="#ted" title="3.3.&nbsp;Topics, TopicExpressions and Dialects">Section 3.3</a>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e3125"></a>5.4.&nbsp;Starting <span class="emphasis"><em>QCG Notification</em></span></h3></div></div></div><p>To start <span class="emphasis"><em>QCG Notification</em></span> as a daemon
-      type:</p><pre class="programlisting">$ ./qcg-ntfd</pre><p>If you start <span class="emphasis"><em>QCG Notification</em></span> with parameter
+      in the <a class="link" href="#ted" title="3.3.&nbsp;Topics, TopicExpressions and Dialects">Section 3.3</a>.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e3125"></a>5.4.&nbsp;Starting <span class="emphasis"><em>QCG-Notification</em></span></h3></div></div></div><p>To start <span class="emphasis"><em>QCG-Notification</em></span> as a daemon
+      type:</p><pre class="programlisting">$ ./qcg-ntfd</pre><p>If you start <span class="emphasis"><em>QCG-Notification</em></span> with parameter
       -h you will get an optional parameters list:</p><pre class="programlisting">$ ./qcg-ntfd -h
 usage: ./qcg-ntfd [-d] [-z config_file]
@@ -2117 +2119 @@
   -z config_file  configuration file, default is /opt/qcg/etc/qcg-ntfd.xml
   -v              print version information
-  -h              print this help</pre><p>Once you run <span class="emphasis"><em>QCG
-      Notification</em></span> as a daemon, a log file is created. Using
-      various log levels, you can log less or more details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e3148"></a>5.5.&nbsp;Stopping <span class="emphasis"><em>QCG Notification</em></span></h3></div></div></div><p>At the moment, shutdown is performed simply by sending
+  -h              print this help</pre><p>Once you run
+      <span class="emphasis"><em>QCG-Notification</em></span> as a daemon, a log file is
+      created. Using various log levels, you can log less or more
+      details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="d0e3148"></a>5.5.&nbsp;Stopping <span class="emphasis"><em>QCG-Notification</em></span></h3></div></div></div><p>At the moment, shutdown is performed simply by sending
       <code class="filename">SIGINT</code> signal to the service, e.g.:</p><pre class="programlisting">$ kill -SIGINT `pidof qcg-ntfd`</pre></div></div></div>
-
 }}}