Appeal No. 2006-2936
Application No. 10/013,714
2. At column 4, lines 12 through 34, Britton states the
following:
Embodiments of the present invention may
include a property access control list 300 as
shown in FIG. 3. The property access control list
300 may permit access based on, for example, a
variable object-property approach. In one
embodiment, the variable object-property approach
may provide property level security for those
properties in an object that require permissions
different from the object itself. For example, if
only property 210-1a has permissions different
from its corresponding object 210-1, then the
property access control list 300 may contain at
least the name of property 210-1a. All of the
other properties 210-1b to 210-1m may retain the
permissions of the object 210-1. Thus, the
property names for properties 210-1b to 210-1m may
not be included in the property access control
list 300 under this embodiment. Accordingly, the
size of the property access control list 300 may
vary between zero entries and the number of
properties having permission different from the
object, up to `z`. Property level access may be
provided by using a property level permissions
control number. In alternative embodiments of the
present invention, the object may contain an
object level permissions control number (not
shown), that contains the permissions for the
objects 210-1 to 210-N.
3. Further, at column 6, lines 52 through 64, Britton
states the following:
[T]he Unix file system security approach,
which specifies read, write, and execute
permissions for different users, may be utilized.
Under the Unix approach, read, write and execute
permissions are specified by a permissions set
and/or permissions control number. The permissions
control number for each property or object may
10
Page: Previous 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Next
Last modified: November 3, 2007