[Zope-Checkins] CVS: Zope3/doc/zcml/namespaces.zope.org/zope - adapter.stx:1.2 allow.stx:1.2 content.stx:1.2 defaultPrincipal.stx:1.2 defaultView.stx:1.2 factory.stx:1.2 grant.stx:1.2 hook.stx:1.2 hookable.stx:1.2 implements.stx:1.2 permission.stx:1.2 principal.stx:1.2 require.stx:1.2 resource.stx:1.2 role.stx:1.2 securityPolicy.stx:1.2 service.stx:1.2 serviceType.stx:1.2 skin.stx:1.2 utility.stx:1.2 view.stx:1.2

Jim Fulton jim@zope.com
Mon, 10 Jun 2002 19:28:40 -0400


Update of /cvs-repository/Zope3/doc/zcml/namespaces.zope.org/zope
In directory cvs.zope.org:/tmp/cvs-serv17445/doc/zcml/namespaces.zope.org/zope

Added Files:
	adapter.stx allow.stx content.stx defaultPrincipal.stx 
	defaultView.stx factory.stx grant.stx hook.stx hookable.stx 
	implements.stx permission.stx principal.stx require.stx 
	resource.stx role.stx securityPolicy.stx service.stx 
	serviceType.stx skin.stx utility.stx view.stx 
Log Message:
Merged Zope-3x-branch into newly forked Zope3 CVS Tree.


=== Zope3/doc/zcml/namespaces.zope.org/zope/adapter.stx 1.1 => 1.2 ===
+
+See lib/python/Zope/App/ComponentArchitecture/component-meta.zcml
+
+Attributes
+
+  * factory, a callable or list of callables, that realises the adaption
+  
+  * provides, the interface this adapter adapts to
+  
+  * for, optional, the interface this adapter adapts from.
+  
+  * permission, optional, the permission required to use this adapter
+  
+  If the 'for' attribute is not present, the adapter can adapt from any
+  component.
+  
+  
+  


=== Zope3/doc/zcml/namespaces.zope.org/zope/allow.stx 1.1 => 1.2 ===


=== Zope3/doc/zcml/namespaces.zope.org/zope/content.stx 1.1 => 1.2 ===
+
+Subdirectives
+
+  implements
+
+  require
+  
+  allow
+  
+  zmi:factory
+  
+
+Examples
+
+  An empty content directive::
+  
+    <content class=".Contact."/>
+    
+  A content directive that contains security assertions::
+  
+    <content class=".Contact.">
+      <allow interface=".IContact.IViewContact" />
+      <require permission="Zope.ManageContent" interface=".IContact." />
+    </content>
+    
+  A content directive that makes an interface implementation assertion::
+  
+    <content class=".Contact.">
+      <implements interface=".IContact." />
+    </content>
+    
+  A rather full content directive::
+  
+    <content class=".Contact.">
+      <implements interface=".IContact." />
+      <zmi:factory
+          permission="ZopeProducts.Contact.ManageContacts"
+          title="Personal Contact Information" />
+
+      <security:require
+          permission="Zope.View"
+          interface=".IContact.IContactInfo." />
+
+      <security:require
+          permission="ZopeProducts.Contact.ManageContacts"
+          attributes="update"/>
+    </content>


=== Zope3/doc/zcml/namespaces.zope.org/zope/defaultPrincipal.stx 1.1 => 1.2 ===
+


=== Zope3/doc/zcml/namespaces.zope.org/zope/defaultView.stx 1.1 => 1.2 ===
+
+Assuming the MinimalDefaultViewDirectives proposal is accepted, the following
+will hold.
+
+Attributes
+
+  * for, a component
+  
+  * name, the name of the view that is to be the default
+
+
+References
+
+  http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/MinimalDefaultViewDirectives


=== Zope3/doc/zcml/namespaces.zope.org/zope/factory.stx 1.1 => 1.2 ===
+
+See lib/python/Zope/App/ComponentArchitecture/component-meta.zcml
+
+Attributes
+
+  * component
+  
+  * id, optional
+  


=== Zope3/doc/zcml/namespaces.zope.org/zope/grant.stx 1.1 => 1.2 ===
+
+Overview
+
+  It is used to do the following:
+
+    * grant permissions to principals
+
+    * associate permissions with roles
+
+    * assign roles to principals
+
+  Ultimately, this is all to do with granting permissions, so the grant
+  directive is used for all of these.
+
+Attributes
+
+  The grant directive has three possible attributes
+  
+    * permission, a permission's id
+  
+    * principal, a principal's id
+  
+    * role, a role's id
+  
+  However, only these combinations are valid
+  
+    * permission - role
+    
+    * permission - principal
+    
+    * role - principal
+
+  Note that the permissions, principals and roles need to be defined
+  elsewhere using the permission, role and principal directives.
+
+Examples
+
+  Here are some examples of using the grant directive::
+  
+    <grant permission="Zope.View" principal="Bob" />
+  
+    <grant role="Zope.Manager" principal="Bob" />
+    


=== Zope3/doc/zcml/namespaces.zope.org/zope/hook.stx 1.1 => 1.2 ===
+
+See lib/python/Zope/Configuration/configuration-meta.zcml


=== Zope3/doc/zcml/namespaces.zope.org/zope/hookable.stx 1.1 => 1.2 ===
+
+See lib/python/Zope/Configuration/configuration-meta.zcml


=== Zope3/doc/zcml/namespaces.zope.org/zope/implements.stx 1.1 => 1.2 ===
+
+See lib/python/Zope/App/ComponentArchitecture/component-meta.zcml
+
+Overview
+
+  The implements subdirective lets you assert that a component
+  implements a given interface.
+  
+Attributes
+
+  * interface, the interface that is implemented
+  
+Example::
+
+  <content class=".Contact.">
+    <implements interface=".IContact." />
+  </content>
+
+
+  


=== Zope3/doc/zcml/namespaces.zope.org/zope/permission.stx 1.1 => 1.2 ===


=== Zope3/doc/zcml/namespaces.zope.org/zope/principal.stx 1.1 => 1.2 ===
+     


=== Zope3/doc/zcml/namespaces.zope.org/zope/require.stx 1.1 => 1.2 ===


=== Zope3/doc/zcml/namespaces.zope.org/zope/resource.stx 1.1 => 1.2 ===


=== Zope3/doc/zcml/namespaces.zope.org/zope/role.stx 1.1 => 1.2 ===


=== Zope3/doc/zcml/namespaces.zope.org/zope/securityPolicy.stx 1.1 => 1.2 ===
+
+Overview
+
+  Sets the security policy that Zope will use.
+  
+  XXX: Explain what this means.
+  
+Attributes
+
+  The securityPolicy directive takes these attributes
+  
+    * component, the component that implements the security policy
+    
+    * factory, a callable that returns a security policy
+    
+    
+  The security policy component should implement the interface
+  "Zope.Security.ISecurityPolicy."
+  
+  
+  
+  
+  


=== Zope3/doc/zcml/namespaces.zope.org/zope/service.stx 1.1 => 1.2 ===


=== Zope3/doc/zcml/namespaces.zope.org/zope/serviceType.stx 1.1 => 1.2 ===


=== Zope3/doc/zcml/namespaces.zope.org/zope/skin.stx 1.1 => 1.2 ===


=== Zope3/doc/zcml/namespaces.zope.org/zope/utility.stx 1.1 => 1.2 ===
+
+See lib/python/Zope/App/ComponentArchitecture/component-meta.zcml
+
+Attributes
+
+  * factory
+  
+  * component
+  
+  * provides, the interface this utility provides
+  
+  * permission, optional, the permission id required to use this utility
+  
+  
+  Either component or factory must be given, not both.
+  If component is given, it is a resolvable name to an object.
+  If factory is given, it is a callable object that provides a component.
+  


=== Zope3/doc/zcml/namespaces.zope.org/zope/view.stx 1.1 => 1.2 ===