[Checkins] SVN: zope3docs/ Define ZCML.

[Christian Theune]

Log message for revision 96778:
  Define ZCML.
  
  Reformatting, fix incorrect markup.
  

Changed:
  _U  zope3docs/
  U   zope3docs/source/codingstyle/glossary.rst

-=-

Property changes on: zope3docs
___________________________________________________________________
Modified: bzr:revision-info
   - timestamp: 2009-02-19 11:18:37.648999929 +0100
committer: Christian Theune <ct at gocept.com>
properties: 
	branch-nick: zope3docs.bzr

   + timestamp: 2009-02-19 11:47:45.329999924 +0100
committer: Christian Theune <ct at gocept.com>
properties: 
	branch-nick: zope3docs.bzr

Modified: bzr:file-ids
   - source/codingstyle/index.rst	96696 at 62d5b8a3-27da-0310-9561-8e5933582275:zope3docs:source%2Fcodingstyle%2Findex.rst
source/codingstyle/python-style.rst	96696 at 62d5b8a3-27da-0310-9561-8e5933582275:zope3docs:source%2Fcodingstyle%2Fpython-style.rst

   + source/codingstyle/glossary.rst	96696 at 62d5b8a3-27da-0310-9561-8e5933582275:zope3docs:source%2Fcodingstyle%2Fglossary.rst

Modified: bzr:revision-id:v3-single-zope3docs
   - 16 ct at gocept.com-20090219095131-k60befy2nrfx9q99
17 ct at gocept.com-20090219101837-g1g0cg0op0o8a104

   + 16 ct at gocept.com-20090219095131-k60befy2nrfx9q99
17 ct at gocept.com-20090219101837-g1g0cg0op0o8a104
18 ct at gocept.com-20090219104745-nh3531xbm8hsd2v9


Modified: zope3docs/source/codingstyle/glossary.rst
===================================================================
--- zope3docs/source/codingstyle/glossary.rst	2009-02-19 17:28:03 UTC (rev 96777)
+++ zope3docs/source/codingstyle/glossary.rst	2009-02-19 17:28:05 UTC (rev 96778)
@@ -1,13 +1,15 @@
 Glossary
 ========
 
-This is a list of some common words that should have the same meaning throughout Zope.  It is not exhaustive.
+This is a list of some common words that should have the same meaning
+throughout Zope.  It is not exhaustive.
 
 ID
-    The term 'id' should only be used when we are talking about an identifier
-    that is unique in the context of some particular id scheme. Examples include
+    The term 'id' should only be used when we are talking about an
+    identifier that is unique in the context of some particular id
+    scheme. Examples include
 
-    * A social security number, unique within a country's social secuity 
+    * A social security number, unique within a country's social secuity
       bureaucracy
 
     * A user id consisting of an NT Domain and a username, unique within
@@ -17,33 +19,46 @@
 
     * A Windows NT domain, unique within a Windows network
 
-    We could consider the name of an object within a container to be an id within
-    the id scheme of that container, but this is not a particularly useful
-    way of thinking. One reason is that to identify the container, we need to
-    consider it as having an id within the id scheme of *its* container.
+    We could consider the name of an object within a container to be an
+    id within the id scheme of that container, but this is not a
+    particularly useful way of thinking. One reason is that to identify
+    the container, we need to consider it as having an id within the id
+    scheme of *its* container.
 
-    Id schemes should really be well-known points of reference within a system.
-    So, the model of Services in Zope 3 fits; you look up a service by its
-    id within the service manager id scheme.
+    Id schemes should really be well-known points of reference within a
+    system.  So, the model of Services in Zope 3 fits; you look up a
+    service by its id within the service manager id scheme.
 
 Key
-    We use an object's name to get it from within a container.
-    The container sees these names as 'keys', so from a container's point
-    of view, a name functions as a key to look up an object.
+    We use an object's name to get it from within a container.  The
+    container sees these names as 'keys', so from a container's point of
+    view, a name functions as a key to look up an object.
 
     When we use the term 'key', we really mean "a name functioning as a
     key in the context of a container".
 
 Manager
-    1. A user that configures components, such as a SiteManager.  2. An object that performs through the web configuration, such as a ServiceManager (which allows site managers to configure services.)
+    1. A user that configures components, such as a SiteManager.
 
-    Generally, the word 'manager' is inappropriate for objects that don't perform through-the-web configuration.  For example, global "service services" are not configurable through the web, but they were once called "service managers", and have now been renamed, since the name caused confusion with through-the-web configurable service managers.
+    2. An object that performs through the web configuration, such as a
+       ServiceManager (which allows site managers to configure
+       services.)
 
+    Generally, the word 'manager' is inappropriate for objects that
+    don't perform through-the-web configuration.  For example, global
+    "service services" are not configurable through the web, but they
+    were once called "service managers", and have now been renamed,
+    since the name caused confusion with through-the-web configurable
+    service managers.
+
 Name
     Objects are given names to help us find them. An object may be found
     via more than one name. In Zope 3, we use names to guide the process
     of traversing from a container to a contained object.
 
+ZCML
+    Zope Configuration Markup Language. An XML-based language used to
+    configure software components.
 
 References
 ----------