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

5- 51
The security for any occurrence depends on the following:
* The access rights of the current scope to that occurrence.
* The sensitivity of the occurrence.
Access Rights
The access rights of a scope to an occurrence are determined by whether the scope owns the occurrence or
is just associated with it. Association and ownership are discussed below.
Occurrence Ownership.
When a scope owns an occurrence, it has all rights to that occurrence, and can therefore read it, modify it,
transfer its ownership to another scope, or even delete it. It can also allow another scope access to the
occurrence by associating the occurrence with that scope. Note that the DA scope always has all rights to
all occurrences.
The security of an occurrence applies to all versions of that occurrence. When you create an occurrence, if
no other version of that occurrence exists, the current scope becomes the owner scope. If another version of
that occurrence already exists, then the current scope must be the DA scope or the owner scope of the
existing version of the occurrence.
Occurrence/Scope Association.
An association between an entity or relationship occurrence and a scope is an explicit access capability
granted to that scope by the owner scope of that occurrence. When a scope is associated with an occurrence,
its rights to that occurrence are dependent upon the type of association it has. Associations between
scopes and occurrences can be either of two types:
• ReadAccess,which gives the associated scopethecapabilityto read the occurrence. Furtherinformation
about retrieving information about occurrences is located in Chapter 4 of the HP System Dictionary/XL
Intrinsics Reference Manual. Refer to the intrinsics SDGetEnt, SDGetEntList, SDGetRel, and SDGe-
tRelList, which are used to retrieve information about occurrences.
• Modify Access, which not only gives the associated scope the capability to read the occurrence, but also
allows it to change the values of most of its attributes.
To modify an occurrence, the associated scope must also have create capability, and if creating links,
mustalso have read access tothe common domain entity orcommon domain relationship involved inthe
link.
When an occurrence is associated to a scope, all versions of that occurrence are associated with the scope.
A scope can delete occurrence associations it has created from any occurrence/scope association. It can also
delete occurrence/scope associations from itself. For a local domain occurrence to be linked to a common
domain occurrence, the owner scope must have at least read access to the common domain occurrence.
Only the owner scope or DA scope can modify the link to a common domain occurrence. Note that a scope
that has access to a common domain occurrence can also read the names of all of the local domain
occurrences that are linked to that common domain occurrence.
A two step process is required to modify an occurrence/scope association (change the association between
an occurrence and a scope).
• Delete the current association.
• Create a new association.
Further details on associations are located in the descriptions of intrinsics SDAddEntScope,
SDAddRelScope, SDDeleteEntScope and SDDeleteRelScope in Chapter 4 of the HP System Dictionary/XL
Intrinsics Reference Manual.