Appeal No. 2006-2936
Application No. 10/013,714
comprise a plurality of three bit binary fields so
that any number between 0 and 7 may be
represented. Each three bit field may represent
property level or object level access control for,
for example, the owner of the object (e.g., owner
access), each group in the object's group access
list (e.g., group access) and/or any user who is
not the owner and is not in any group access list
(e.g., other user access).
4. Additionally, at column 7, line 57 through column 8,
line 5, Britton states the following:
The property access control list 300 may be
checked each time a request is made to read or
write data within the corresponding object to
determine the level of access the users may have
for the desired property. In alternative
embodiments of the present invention, the object
may have an object level permissions control
number that may contain permissions for access to
the object. The user may be the owner of the
object, or a member of a group in the group access
list or another user and may have access to the
object based on the object level permissions
control number. The user may have the same level
of access for each property within the object
except for those properties having permissions
different from the object. For properties having
different permissions, the property access control
list 300 may be accessed to determine the level of
access the user may be given based on the property
level permissions control number.
With the above discussion in mind, we find that with regard to
representative claim 1, Britton teaches a method for controlling
users’ access to an object-oriented database based on property
level security. Particularly, Britton teaches a UNIX module for
11
Page: Previous 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Next
Last modified: November 3, 2007