Appeal 2007-0937
Application 10/666,869
service that correlates to an administrative system supporting the web
services and invoking that data.
Appellants (Specification 5:13-15) define "provisioning" as
"[c]onfiguring a system with account and other information sufficient to
allow a particular consumer to access a particular web service." Nowhere in
the portions relied upon by the Examiner, nor in any other portions, of
Fletcher I do we find any mention of provisioning. Fletcher I refers to "[a]
content framework such as a portal platform [which] provides many built-in
services for content management and service hosting, such as persistence,
personalization, and transcoding" (see Fletcher I, para. 0040). Further, the
portal platform "perform[s] functions such as logging of events, billing, and
other types of administrative operations pertaining to execution of the web
service" (see Fletcher I, para. 0050). Thus, Fletcher I mentions the
administrative systems that support the web services and alludes to
provisioning by referring to personalization. However, we find no storing of
provisioning processes data for the web services that correspond to the
administrative systems. Therefore, we cannot sustain the anticipation
rejection of claim 1 and the claims grouped therewith, claims 2, 5, 8, 9, and
11 through 13.
The Examiner asserts (Answer 6) that claims 1 through 3, 8, 11, and
12 are anticipated by Fletcher II. Appellants contend (Br. 10-11) that
Fletcher II fails to disclose "provisioning processes data storage for storing
respective provisioning processes data … for each of a plurality of
provisioning web services that correlate to respective administrative systems
supporting the plurality of web services" and "invoking the respective
provisioning processes data for each provisioning web service that correlates
5
Page: Previous 1 2 3 4 5 6 7 8 9 Next
Last modified: September 9, 2013