Appeal 2007-0474
Application 10/692,885
1 2. Preferences (e.g., conditions, actions) can,…be boiled down into
2 three categories, preferences that take action on a users’ behalf…,
3 preferences that control the content of folders…and a combination of the
4 first two… . (Specification 5:27 to 6:4).
5 3. Appellants state that an end-user writes preferences in accordance
6 with a provided schema. The preferences can be in any form but according
7 to one aspect of the invention they comprise a plurality of IF-THEN
8 statements separated by Boolean operators. The schema can be provided by
9 an application developer to constrain and thereby simplify end-user
10 programming. …the preference is executed on the occurrence of an
11 event….an action is taken based on a conditionally valid preference.
12 (Specification 113:19-27).
13 4. Appellants disclose that the system can execute a SQL query
14 statement in lieu of the user declaration… (Specification 46:9-11).
15 5. Preferences are specified by an end-user based on a developer
16 schema (e.g., XML schema) and stored in tables in a data store, for example.
17 (Specification 112:2-4).
18
19 Relating to Anticipation
20 Knutson
21 6. Knutson describes a system and method for “allowing a user to
22 segment and partition a database based upon attributes associated with the
23 data in the database…” (col. 2, ll. 22-25).
24 7. Knutson describes that “[t]he application program allows a user to
25 define predetermined data types, to define relationships between the data
26 types…” (col. 2, ll. 32-34: Abstract).
5
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Next
Last modified: September 9, 2013