Appeal 2007-1505
Application 10/279,481
Rather, the article discusses evolving the schema such that an application
that does not support the new schema can view a document in the evolved
schema, as any unknown fields are simply ignored. See third to last
paragraph under heading “12. Schema Evolution using Refinement (Derive
by Extension).”
Sarkar teaches a system to formulate queries (in SQL) to navigate
through multiple XML documents. Abstract, col. 5, ll. 53-59. We are
unable to find where Sarkar discusses performing schema manipulations.
Nor are we able to find that Sarkar teaches or suggests validating the schema
manipulations based upon a determination of whether one set of valid XML
documents of one schema contain all of the valid XML documents of
another schema.
Su teaches a system for transforming data from one XML schema to
another XML schema. Abstract. The system takes the source and target
schema and creates respective tree structures for the schemas. See figure 1
(item 110), flow chart figure 8 (steps 810, 820), and paragraph 0036. The
system then generates a series of operations that when implemented will
transform an XML document in the source schema into an XML document
in the target XML schema. See figure 1 (item 140), flow chart figure 8 (step
830), and paragraphs 0031 and 0092. The operations to transform from one
schema to another are determined by finding matching nodes and analyzing
how they should be transformed. See paragraphs 0039 and 0082. The
system makes use of a series of transformations to match nodes of the
respective schema. See paragraph 0092. The transformations including
we have identified are dispositive of the Examiner’s rejection.
7
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next
Last modified: September 9, 2013