doc: clarified Group/Client tag use in xml-common.txt

1 files changed, 1 insertions, 52 deletions

diff --git a/doc/unsorted/writing_specification.txt b/doc/unsorted/writing_specification.txt
index 378a5af0e..49b11af7b 100644
--- a/doc/unsorted/writing_specification.txt
+++ b/doc/unsorted/writing_specification.txt
@@ -26,7 +26,7 @@ that a client needs the Bcfg2 package with
 
 .. code-block:: xml
 
-    <Package name=bcfg2/>
+    <Package name="bcfg2"/>
 
 but this does not explicitly identify that an RPM package version
 0.9.2 should be loaded from http://rpm.repo.server/bcfg2-0.9.2-0.1.rpm.
@@ -69,23 +69,6 @@ be installed on hosts. These entities are independent from one another,
 and can be installed individually without worrying about the impact on
 other entities.
 
-Usage of Groups in Base and Bundles
------------------------------------
-
-Groups are used by the Base and Bundles plugins for selecting
-Configuration Entity Types for inclusion in a clients abstract
-configuration.  They can be thought of as::
-
-    if client is a member of group1 then
-        assign to abstract config
-
-Nested groups are conjunctive (logical and).::
-
-    if client is a member of group1 and group2 then
-        assign to abstract config
-
-Group membership maybe negated.  See "Writing Bundles" for an example.
-
 Configuration Entity Types
 --------------------------
 
@@ -143,17 +126,6 @@ processed.  Each bundle must be defined in its own file::
     atftp.xml
     ....
 
-Groups can be used inside of bundles to differentiate which entries
-particular clients will receive. This is useful for the case where
-entries are named differently across systems; for example, one linux
-distro may have a package called openssh while another uses the name ssh.
-Configuration entries nested inside of Group elements only apply to
-clients who are a member of those groups; multiply nested groups must
-all apply.
-
-Also, groups may be negated; entries included in such groups will only
-apply to clients who are not a member of said group.
-
 When packages in a bundle are verified by the client toolset, the Paths
 included in the same bundle are taken into consideration.  That is,
 a package will not fail verification from a Bcfg2 perspective if the
@@ -267,26 +239,3 @@ A Generator can take care of a particular configuration element. Any time
 this element is requested by the client, the server dynamically generates
 it either by crunching data and creating new information or by reading
 a file off of disk and passes it down to the client for installation.
-
-Usage of Groups in Generators
------------------------------
-
-Similar to Abstract Configuration plugins, groups are used by generator
-plugins for selecting Configuration Entities for inclusion in a clients
-literal configuration.  They can be thought of as::
-
-    if client is a member of group1 then
-        assign to abstract config
-
-Nested groups are conjunctive (logical and).::
-
-    if client is a member of group1 and group2 then
-        assign to abstract config
-
-How the groups are configured is specific to the plugin, but here are
-two common methods:
-
-* xml configuration file (Pkgmgr, Rules)
-* file name encoding (Cfg, SSHBase)
-
-Details are included on each plugin's page.