HP System Dictionary/XL General Reference Manual Vol 1 (32256-90004)

5- 50
• Only the DA scope or a scope with version capability is allowed to create new versions.
• When a scope creates a new version, it becomes the owner of that version.
• Only the DA scope or the owner scope can delete or rename a version or change its owner scope.
• Only the DA scope or a scope with version capability can set the status of a version, or copy all occur-
rences of an existing version and assign them to a new version.
Note that when a version is copied, all occurrences of the existing version are copied to another version.
The owner for each occurrence will be the same across all versions.
Occurrence Security
The security scheme for entities is exactly the same as that for relationships, and is accomplished by two
parallel sets of operations, one for entities and one for relationships. In the following paragraphs,
therefore, occurrence can mean either entity or relationship.
Figure 5-1 outlines the security scheme for occurrences. Note that the boxed text in the sections labeled
’Scope Capability’ and ’Linked Scope Access’ lists the capability of the scope. The text in parentheses
shows the actual access the scope has to an occurrence. This access is determined by the combination of
occurrence sensitivity and scope access rights, which are explained in detail on the following pages, and
illustrated below.
In the example, note that a scope having create capability can read or modify an occurrence whose
sensitivity is set to public modify, but cannot modify an occurrence whose sensitivity is set to public read,
unless that scope is either the owner of the occurrence or has been given modify access to the occurrence by
its owner.
Figure 5-1. Occurrence Security