Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by AndreasHartmann: http://wiki.apache.org/lenya/Glossary ------------------------------------------------------------------------------ deactivate:: The act of removing a document from the '''=>live''' '''=>area'''. See also: '''=>workflow'''. - document:: The set of '''=>language versions''' and other '''=>assets''' of a piece of information grouped under a common '''document id''', with potentially multiple representations (e.g., HTML and PDF formats). + document:: The set of '''=>language versions''' and other '''=>assets''' of a piece of information grouped under a common '''document id''', with potentially multiple representations (e.g., HTML and PDF formats). In Lenya 1.2, the term document refers to a single language version. ''[This is awkward. There is an ongoing debate about the proper terms and about unifying asset and document handling.]'' @@ -71, +71 @@ fallback mechanism:: A key concept for '''=>publication templating'''. Resources requested using the fallback '''=>protocol''' are first searched in the current publication; if not found, the template is searched, then the template's template, etc. If all sitemaps etc. of a publication (including used modules) use the fallback protocol constistently, the publication will completely support templating. group:: see '''=>access control''' + + identity:: An object storing information about a client that accesses a Lenya server. The identity contains a reference to the '''user''', to the '''machine''' and to the '''world'''. If you don't log in, the identity only contains your machine IP address and the world. info:: see '''=>area''' @@ -143, +145 @@ ''(see also JcrConfiguration)'' - role:: The capabilities and privileges of a user as part of a '''=>workflow'''. By default, Lenya defines three basic roles that a lenya user can have. An '''admin''' can control all aspects of a publication and create, delete or modify users and groups. An '''editor''' can modify and create new content, but cannot publish it; for this, s/he hands the work to a '''reviewer''', who does the final check and decides whether the page can go live. + role:: The capabilities and privileges of an '''=>identity''' on a certain URL. Roles are used to define conditions for '''=>workflow''' transitions, and to restrict access to '''=>usecases'''. The default publication defines four basic roles that a lenya user can have. An '''admin''' can control all aspects of a publication and create, delete or modify users and groups. An '''editor''' can modify and create new content, but cannot publish it; for this, s/he hands the work to a '''reviewer''', who does the final check and decides whether the page can go live. The '''visitor''' is just allowed to view pages. You can define custom roles and workflows. Roles are frequently assigned via '''=>group''' membership, but do not confuse roles and groups. OverviewAccessControl has a good explanation of how different they are. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
