Appeal No. 2002-0275
Application No. 09/215,752
attributes in the meta definition” and “prompting a user to input data values
corresponding to the object attributes.” (Brief at 5-6.)
According to the statement of the rejection (Answer at 3), “prompting a user” to
input data values corresponding to object attributes is taught at column 9, line 38 of
Maruyama. Further, according to the examiner, interaction using view manager 101
“inherently” requires displaying command and data entry fields that prompt the user for
input. (Id. at 8.)
Maruyama discloses a view manager 101 (Fig. 1) which converts an object
defined by the user into a viewable structure such that the user may enter commands
and data. A parts object manager 102 manages a parts object to be held in database
107 when a characteristic based on a new definition is prescribed for an object which
has already been defined. Database 107 thus holds objects and parts objects. Col. 3,
ll. 41-59. Figures 6A to 6F show examples of a type definition object and a relation
definition object which are present in a schema (i.e., a set of definitions of data). Col. 1,
ll. 8-11; col. 5, ll. 42-46. Figures 7A and 7B show examples of parts objects that are
appended to the definitions of Figures 6A to 6F when an object attribute is changed or
added. Col. 6, ll. 14-20.
Figure 13 shows how a change in type definition is performed when restructuring
the database. The user designates an object identifier of a type definition object to the
object manager 103 through view manager 101. If a type definition needs to be
changed because of information contained in a parts attribute object, then the attribute
-4-
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 Next
Last modified: November 3, 2007