Appeal No. 2006-2354 Page 21
Application No. 09/877,157
for anticipation is the epitome of obviousness. In re Pearson, 494 F.2d 1399, 1402,
181 USPQ 641, 644 (CCPA 1974); see also In re Fracalossi, 681 F.2d 792, 794,
215 USPQ 569, 571 (CCPA 1982).
In particular, Figure 6 of Abraham shows a graphical user interface (70)
having a main window (84) with three portions. A first portion contains a list of
predefined data elements (user list 88) that identifies all users of the LAN.
Abraham, page 14, lines 14-15. A second portion displays groups of data elements
(group hierarchy 86). Abraham, page 14, line 32. In the example of Figure 5, the
root of the hierarchy is a group containing all of the users identified in the user list
88 and the subgroups contain users corresponding to various departments of a
corporation. Abraham, page 14, line 32 – page 15, line 4. As such, the users in the
root group and in the subgroups share at least one common property. In the case of
the root group, the common property is that all users are employees of the
corporation. In the case of subgroups, the common property is that the list users
are members of a particular corporate department. Finally, the interface (70)
includes a third portion that displays the policy generated from the groups of data
elements. In particular, Abraham teaches that the site policy tab 95 in the third
portion of the window 84 can be used by the administrator to set site policies for a
group in the group hierarchy 86. Abraham, page 41, lines 19-20. When the
administrator selects the site policy tab 95, a site policy tab window 145 is
generated by the interface (70), as shown in Figure 8O. Abraham, page 41, lines
20-21. When a system administrator sets a site policy that allows a group to access
all sites with the exception of specified sites, or denies access to the group to all
sites with the exception of specified sites, the generated policy is displayed to the
Page: Previous 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Next
Last modified: November 3, 2007