Exhibit D-20
`Chart for U.S. Patent No. 9,471,287 (“the ’287 patent”)
`U.S. Patent Appl. Publ. No. 2007/0118844 (“Huang”)
`As shown in the chart below, all asserted claims of the ’287 patent are invalid under (1) 35 U.S.C. § 1021 (a), (b), (e), and (g) because
`Huang meets each element of those claims, and (2) 35 U.S.C. § 103 because Huang renders those claims obvious either alone, or in
`combination with the knowledge of a person having ordinary skill in the art, and in further combination with the references
`specifically identified in the following claim chart and/or one or more references identified in Google’s Preliminary Invalidity
`Contentions. As used herein, “Huang” refers to U.S. Patent Appl. Publ. No. 2007/0118844 and includes material incorporated by
`reference, including without limitation U.S. Patent Appl. Ser. No. 11/241,073, subsequently published on April 5, 2007 as U.S. Patent
`Appl. Publ. No. 2007/0079282 to Nachnani (“Nachnani”). Huang constitutes prior art under 35 U.S.C. § 102(a), (b), (e) and (g)
`because it was published by the U.S. Patent Office on May 24, 2007, prior to the alleged priority date of the ’287 patent (January 12,
`2008).
`Motivations to combine the disclosures of Huang with disclosures of other systems available to the public and publications known in
`the art, as shown in this chart, include at least the similarity in subject matter between the references to the extent they concern
`information input devices. Insofar as the references cite other patents or publications, or suggest additional changes, one of ordinary
`skill in the art would look beyond a single reference to other references in the field. One of ordinary skill in the art would have been
`motivated to combine Huang with references and systems such as: U.S. Patent App. Pub. No. 2006/0271537 (“Chandrasekharan”),
`U.S. Patent Publication No. 2007/0067421 (“Angelov”), U.S. Patent Publication No. 2006/0129972 (“Tyburski”). Chandrasekharan,
`Angelov, and Tyburski are in the same or similar technical field as the Huang and the ’287 patent, and addresses the same or similar
`technical problem (e.g., providing software that interfaces to a web service) as the ’287 patent. Accordingly, a POSITA would have
`had reason to consider the teachings of Chandrasekharan, Angelov, and/or Tyburski when implementing the Huang’s system. A
`person of ordinary skill in the art would be motivated to combine Huang with any of these references in order to create more effective
`systems to create displays on devices..
`These invalidity contentions are based on Google’s present understanding of the ’287 patent claims and Express Mobile’s theories of
`infringement against Google. Google expressly does not agree that, under a correct construction or reading of the claims, that
`Google’s accused products meet the limitations of the asserted claims of the ’287 Patent or that the claims satisfy the requirements of
`35 U.S.C. § 112. Google’s contentions herein are not, and should in no way be seen as, admissions as to or adoptions of any particular
`claim scope or construction, or as an admission that any particular element is met by any accused product in any particular way.
`
`1 The ’287 patent is subject to pre-AIA 35 U.S.C. §102.
`
`1 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0001
`
`

`

`
`
`Google objects to any attempt to imply claim construction from this chart. Google’s invalidity contentions do not represent Google’s
`agreement or view as to the meaning, definiteness, written description support for, or enablement of any claim contained therein.
`However, at least under Express Mobile’s apparent application of the claims for the purposes of infringement (which Google
`expressly disagrees with), Huang would have rendered the asserted claims of the ’287 patent invalid.
`The following contentions are subject to revision and amendment pursuant to Federal Rule of Civil Procedure 26(e), the Local Rules
`of the Western District of Texas, and the Orders of record in this matter subject to further investigation and discovery regarding the
`prior art and the Court’s construction of the claims at issue. For example, discovery is ongoing, and Google reserves the right to
`supplement these contentions with references to additional materials and evidence obtained in discovery describing Huang.
`Chart for U.S. Patent 9,471,287 (“the ’287 patent”)
`
`Patent No. 9,471,287
`Claim 1
`[preamble] 1. A system for
`generating code to provide content
`on a display of a device, said
`system comprising:
`
`Exemplary citations to Huang
`
`
`To the extent the preamble is limiting, Huang discloses system for generating code to provide
`content on a display of a device.
`
`See, e.g., Huang at [0006] (“In one example the web services here are used with software objects
`such as software applications (i.e., programs) which carry out a business process. See commonly
`owned Patent Application entitled ‘Browser Based Designer and Player,’ filed Sep. 30, 2005,
`inventors Pawan Nachnani et al., Ser. No. 11/241,073, incorporated herein by reference in its
`entirety, which describes a method of building software applications.”).
`
`Id. at Title (““Designer and Player for Web Services Application.”).
`
`Id. at [0040] (““a computer program that provides a user interface which allows a user to create
`the application 111.”).
`
`Id. at at FIG. 1A (showing application designer 104 and application player 106, which executes
`application 111).
`
`2 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0002
`
`

`

`Patent No. 9,471,287
`
`Exemplary citations to Huang
`
`
`
`[a] computer memory storing a
`registry of:
`
`
`
`
`
`Huang discloses a computer memory storing a registry.
`
`See, e.g., Huang at [0043] (“The server 120 receives web service interaction requests from the
`Designer 104, e.g., a request for a list of objects provided by a web service, and interacts with
`web services provided by specific vendors, such as the Siebel Web Service 140 provided by
`
`3 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0003
`
`

`

`Patent No. 9,471,287
`
`
`
`Exemplary citations to Huang
`Oracle Corporation of Redwood Shores, Calif., and the Salesforce Web Service 142 provided by
`Salesforce.com of San Francisco, Calif.”).
`
`Id. at [0044] (“The components of the server 120 include a Generic Web Service Object Model
`130 (also referred to herein as a Genetic WS Object or a WS Object), and a Web Service Factory
`Application Programming Interface 132 (also referred to herein as a WS Factory API).”).
`
`Id. (“More specifically, the WS Object Mapping 123 generates the Generic WS Objects 130 for
`substantially all object types provided by a web service (e.g. an Opportunity object type that
`represents a sales opportunity). The mapping between the Generic WS Object Model 130 and
`the vendor-specific adapters, such as the Siebel WS (Web Services) Adapter 134, is represented
`as a WS Object XML definition 126, which is stored in the database 124.”).
`
`Id. at [0047] (““In the WS Factory API 132, web service data is represented as objects with
`attributes. In the user interfaces of the Designer 104 and Player 106, these objects are presented
`to the user as rows in a table. Each row has one or more columns, which correspond to the
`attributes of the object. For example, there could be an object named Opportunity with attributes
`named Opportunity Name and Opportunity Id. There could be any number of Opportunity object
`instances in the web service, and each Opportunity object would have an Opportunity Name and
`Opportunity Id. These objects can be retrieved by the query Object method, created or updated
`by the insert or Update Object method, and deleted by the delete Object method.”).
`
`Id. at [0082] (“The Designer 104 uses the XML file to decide the meaning of attributes for the
`generic WS object. The XML mapping file can be generated automatically from the vendor
`specific WS object and WSDL definition by using a program named WS Factory.”).
`
`Id. at [0006] (incorporating by reference Nachnani).
`
`Nachnani at [0016] (“Multiple components may be on the web browser, and some of the aspects
`
`4 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0004
`
`

`

`Patent No. 9,471,287
`
`
`
`Exemplary citations to Huang
`of the application may be implemented using the components. The client may include a library
`on the browser, and the library may be used as an intermediary between the defined aspects at
`the browser and the server. The computer network may include the Internet.”).
`
`Id. at [0092] (“FIG. 7 g is an illustrative drawing of an Application List user interface according
`to one embodiment of the invention. The Application List user interface 780 lists applications,
`templates, and lookups that have previously been created using the Application Designer. A user
`can select an application displayed on the Application List 780 for modification in the
`Application Designer or execution in the Application Player.”)
`
`To the extent Huang does not explicitly disclose that its computer system includes a computer
`memory storing a registry of symbolic names and the address of the web service as recited in
`limitation [1.a] (namely, “a registry of: a) symbolic names required for evoking one or more web
`components each related to a set of inputs and outputs of a web service obtainable over a
`network, where the symbolic names are character strings that do not contain either a persistent
`address or pointer to an output value accessible to the web service, and b) the address of the web
`service”), it would have been obvious in view of Chandrasekharan to modify Huang’s system to
`implement such features.
`
`Chandrasekhan, like Huang, relates to software programming in the context of interfacing with a
`web service. (Chandrasekharan at Title (“Apparatus, system, and method for automatically
`generating a reusable software component for interfacing with a web service”), Abstract (“An
`apparatus, system, and method are disclosed for automatically generating a reusable software
`component for interfacing with a web service.… Beneficially, such an apparatus, system, and
`method would facilitate creation, test, and integration of web service components in application
`code without requiring a substantial time and resource investment.”), [0002] (“This invention
`relates to object oriented software programming and more particularly relates to automatically
`generating a reusable software component for interfacing with a web service.”), [0004]-[0013]
`(discussing web services and programming an application to access a web service), [0014]-
`[0026] (disclosing techniques for generating a reusable software component for interfacing with
`a web service), FIGS. 1 (showing interaction between a software develop environment and a
`
`5 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0005
`
`

`

`
`
`Exemplary citations to Huang
`web service), 4A (showing implementation of accessing a web service in a software
`environment); Huang at Abstract (“allow use of [] web services as a data source for a software
`application”), FIGS. 1A (showing an application 111 in communication with web services 140
`and 142), FIGS. 1B-1F (showing techniques for interfacing between an application and a web
`service), ¶¶[0002] (“[Huang] relates to computers and the Internet, and more specifically to web
`services.”), [0003]-[0005] (discussing web services), [0006]-[0008] disclosing techniques for
`interfacing between a software application and a web service).)
`
`Thus, a POSITA would have recognized that Chandrasekharan is in the same or similar technical
`field as Huang and the ’287 patent, and addresses the same or similar technical problem (e.g.,
`providing software that interfaces to a web service) as the ’287 patent. Accordingly, a POSITA
`would have had reason to consider the teachings of Chandrasekharan when implementing
`Huang’s system.
`
`Having looked to Chandrasekharan, a POSITA would have seen that Chandrasekharan discloses
`web services that can be accessed by an application, and also discloses a registry of such web
`services. (Chandrasekharan at [0010] (“performing a search of a Universal Description,
`Discovery, and Integration (“UDDI”) registry of web services”) (emphasis added), [0063]
`(“[T]he search module 304 may search a UDDI registry of web services 110 for a valid URL
`associated with the web service search information provided by a user.”) (emphasis added),
`[0064] (“[T]he store module 306 registers the web service component 112 in a library
`registry…“) (emphasis added).) (See also id. at [0064] (“store module 306 may be connected to
`a storage device such as a storage disk, memory, or the like”) (emphasis added).) A POSITA
`would have understood that Chandraskeharan’s registry is stored in a computer memory.
`
` A
`
` POSITA would have found Chandrasekharan’s disclosures regarding a registry of web
`services to be relevant for implementing Huang’s system that enables an application to interface
`with a web service. A POSITA would have recognized that including a registry of a) the
`symbolic names disclosed in Huang, and b) the address of the web service would have been a
`predictable and beneficial modification of Huang’s system. For example, a POSITA would
`have been motivated to implement this modification because including a registry of the symbolic
`
`6 of 66
`
`Patent No. 9,471,287
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0006
`
`

`

`
`
`Exemplary citations to Huang
`names would have been a straightforward way to implement a system that interfaces with or
`accesses a web service. It was well known to a POSITA that symbolic names were used for
`accessing various types of data and services, so a POSITA would have found it foreseeable to
`implement a registry in the above manner. A POSITA would have known storing the symbolic
`names in a registry would have helped a developer and/or user keep track of web services and
`how to access them.
`
` A
`
` POSITA would have also been motivated to store a registry of the address of the web service,
`to facilitate access to the web service. This would have been predictable, because
`Chandrasekharan discloses using a registry to help find a web service URL. (Chandrasekharan
`at [0009]-[0010].) While Chandrasekharan describes the use of a registry as “requir[ing] an
`additional investment of time and possibly increased cost” (id. at [0010]), a POSITA would have
`recognized that these are simply design considerations and that a registry is nevertheless helpful
`and feasible in desirable in some circumstances, and would have found a registry worthwhile to
`use due to the convenient access it provides to contents stored therein. A POSITA would have
`been familiar with tradeoffs regarding benefits of implementing a feature (e.g., registry) in a
`system and concomitant time or cost requirements, and such a skilled person would have found a
`registry to be worth implementing.
`
`Indeed, Chandrasekharan discloses the use of a registry in its system and process. (Id. at [0063]
`(“In one embodiment, the search module 304 may search a UDDI registry of web services 110
`for a valid URL associated with the web service search information provided by a user.”)
`(emphasis added). [0064] (“In certain embodiments, the store module 306 registers the web
`service component 112 in a library registry and/or a software development environment 104. In
`this manner, the web service component 112 is readily usable by a developer.”) (emphasis
`added).) Thus, given that Chandrasekahran teaches the use of a registry for registering a web
`service component to enable that component to be readily usable by a developer, a POSITA
`would have been motivated to implement a registry in Huang’s system.
`
` A
`
` POSITA would have had a reasonable expectation of success regarding the above
`modification of Huang’s system. For example, given that Huang’s system includes a computer
`
`7 of 66
`
`Patent No. 9,471,287
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0007
`
`

`

`Patent No. 9,471,287
`
`
`
`Exemplary citations to Huang
`memory and web services and Chandrasekharan discloses a registry of web services, the above
`modification would have been a mere combination of known components and technologies,
`according to known principles, to produce predictable results.
`
`To the extent Huang does not explicitly disclose that its computer system includes a computer
`memory storing a registry of symbolic names and the address of the web service as recited in
`element [1.a], it would nevertheless have been obvious in view of Angelov to modify Huang’s
`system to implement such features.
`
`Angelov, like Huang, relates to web services. (Angelov at Title (“System and method for
`dynamic web services descriptor generation using templates”), [0002] (“[Angelov] relates to a
`system and method for improving Web services description generation and maintenance
`including the formation of [Web Services Definition Language] files.”), [0004] (“web services”),
`Abstract (“[A] visualizer process metadata from a configuration file [that] stores metadata about
`a service provided by a Web service.”), [0018] (“A system and method for generating a Web
`services description file is described. … [A] visualizer process metadata from a configuration
`file and applies the metadata to a predefined template to generate a portion of a Web services
`description file. The configuration file stores metadata about a service provided by a Web
`service. …”)); Huang at Abstract (“allow use of [] web services as a data source for a software
`application”), FIGS. 1A (showing an application 111 in communication with web services 140
`and 142), FIGS. 1B-1F (showing techniques for interfacing between an application and a web
`service), [0002] (“[Huang] relates to computers and the Internet, and more specifically to web
`services.”), [0003]-[0005] (discussing web services), [0006]-[0008] (disclosing techniques for
`interfacing between a software application and a web service))
`
`Thus, a POSITA would have recognized that Angelov is in the same or similar technical field
`(e.g., web services) as Huang and the ’287 patent, and addresses the same or similar technical
`problem (e.g., providing software relating to a web service) as the ’287 patent. Accordingly, a
`POSITA would have had reason to consider the teachings of Angelov when implementing
`Huang’s system.
`
`8 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0008
`
`

`

`Patent No. 9,471,287
`
`Exemplary citations to Huang
`
`
`
`
`Having looked to Angelov, a POSITA would have seen that Angelov discloses web services that
`can be accessed by an application, and also discloses a registry of such web services. For
`example, Angelov discloses in its “Description of the Related Art” section (indicating that such
`disclosure was already known by the time of Angelov) that “FIG. 1 shows a web services model
`100 that includes a registry 101, a service provider 102 and a service consumer 103,” where the
`“registry 101 includes listings of various ‘available’ services, and, may assist the service
`consumer 103 in searching for a suitable service provider based on the web servicing needs of
`the service consumer 103.” (Angelov at [0004]-[0005]; see also id., FIG. 1.)
`
`Angelov describes its registry with respect to the “Universal Discovery, Description and
`Integration (UDDI) specifications provided by uddi.org,” which a POSITA would have
`understood to be a standard relating to web services. (Angelov at [0006]; see also id. (“Presently,
`the responsibilities of the most prevalent registry function 101 that is associated with the web
`services effort are defined in various Universal Discovery, Description and Integration (UDDI)
`specifications provided by uddi.org. Besides providing listings of available services, a UDDI
`registry 101 may also make available to a service consumer 103 additional details that pertain to
`any particular web service such as: 1) the location of the web service (e.g., its URI specified by a
`specific network destination address or name); 2) the capabilities of the web service (e.g.,
`specific methods that are supported by the web service and that may be called upon by the
`service consumer), and, 3) communication semantics needed for invoking the web service
`through the network 104 (e.g., the structure of a messaging format and/or protocol needed to
`properly communicate with the web service).”), [0007] (“According to one widely adopted
`approach, such “additional details” are described in Web Services Definition Language (WSDL)
`text documents written in extensible Markup Language (XML). Here, for example, for each web
`service that the registry 101 maintains a listing of, the registry 101 also maintains a WSDL
`document that describes the location, capabilities and communication semantics of the web
`service.”), [0008]-[0014] (describing additional known details regarding web services and
`WSDL documents))
`
`Angelov discloses that storing a registry of names for accessing web services. For example,
`
`9 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0009
`
`

`

`
`
`Exemplary citations to Huang
`Angelov discloses “providing listings of available services,” which a POSITA would have
`understood to include the names of services, and further discloses that “a UDDI registry 101
`may also make available to a service consumer 103 additional details that pertain to any
`particular web service such as: 1) the location of the web service (e.g., its URI specified by a
`specific network destination address or name).” (Angelov at [0006].) Moreover, a POSITA
`would have understood that a registry in accordance with the UDDI standard described in
`Angelov (Angelov at [0006]) includes a name of a web service.)
`
` A
`
` POSITA would have found Angelov’s disclosures regarding a registry of web services to be
`relevant for implementing Huang’s system that enables an application to interface with Huang’s
`web service 156. For example, such a skilled person would have recognized that including a
`registry of a) the symbolic names disclosed in Huang, and b) the address of the web service,
`would have been a predictable and beneficial modification of Huang’s system, to assist with
`maintaining pertinent information regarding web service 156.
`
` A
`
` POSITA would have been motivated to implement this modification because, for example,
`including a registry of the symbolic names would have been a straightforward, conventional way
`to implement a system that interfaces with or accesses a web service. It was well known to a
`POSITA that symbolic names were used for accessing various types of data and services.
`Therefore, a POSITA would have found it foreseeable to implement a registry in the above
`manner, in order to simplify and streamline data processing and recordkeeping relating to
`Huang’s web services. For example, a POSITA would have known storing Huang’s symbolic
`names in a registry would have helped a developer and/or user keep track of web services and
`how to access them.
`
`Angelov discloses storing a registry of the address of a web service. (Angelov at [0006]
`(“[R]egistry 101 may also make available to a service consumer 103 additional details that
`pertain to any particular web service such as: 1) the location of the web service (e.g., its URI
`specified by a specific network destination address or name)[.]”) In light of Angelov’s teachings,
`a POSITA would have been motivated to configure Huang’s system to store a registry of the
`address of Huang’s web service 156, to facilitate access to the web service. (Angelov at [0006])
`
`10 of 66
`
`Patent No. 9,471,287
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0010
`
`

`

`
`
`Patent No. 9,471,287
`
`Exemplary citations to Huang
`This would have been predictable, e.g., because a POSITA would have known that a web service
`such as that described in Huang must be located (e.g., by its address) before it can be used.
`
` A
`
` POSITA would have known how to make any needed adaptations to Huang’s system to
`implement the registry, and the above modification would not have detracted from the
`operability of the system. A POSITA would have been skilled at implementing web services,
`including programming a registry as discussed above, and thus would have found such a
`modification to be simple to implement.
`
`Similarly, a POSITA would have had a reasonable expectation of success regarding the above
`modification of Huang’s system, because the use of a registry in the context of web services was
`well known. (Chandrasekharan at [0010] (“performing a search of a Universal Description,
`Discovery, and Integration (“UDDI”) registry of web services”), [0063] (“[T]he search module
`304 may search a UDDI registry of web services 110 for a valid URL associated with the web
`service search information provided by a user.”), [0064] (“[T]he store module 306 registers the
`web service component 112 in a library registry…”).) Indeed, given that Huang’s system
`includes a computer memory and web services and Angelov discloses a registry of web services,
`the above modification would have been a mere combination of known components and
`technologies (e.g., web services as in Huang, and a registry as in Angelov, according to known
`principles (e.g., a POSITA would have had the knowledge to implement the above combination
`and would have found it to be feasible, as demonstrated by Chandrasekharan), to produce
`predictable results (e.g., a registry of web services to keep track of them and make them easier to
`access).
`Huang discloses a computer memory storing a registry of symbolic names required for evoking
`one or more web components each related to a set of inputs and outputs of a web service
`obtainable over a network, where the symbolic names are character strings that do not contain
`either a persistent address or pointer to an output value accessible to the web service, where each
`symbolic name has an associated data format class type corresponding to a subclass of User
`Interface (UI) objects that support the data format type of the symbolic name, and has a
`preferred UI object.
`
`11 of 66
`
`[b] a) symbolic names required for
`evoking one or more web
`components each related to a set of
`inputs and outputs of a web service
`obtainable over a network, where
`the symbolic names are character
`strings that do not contain either a
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0011
`
`

`

`Patent No. 9,471,287
`persistent address or pointer to an
`output value accessible to the web
`service, where each symbolic name
`has an associated data format class
`type corresponding to a subclass of
`User Interface (UI) objects that
`support the data format type of the
`symbolic name, and has a preferred
`UI object, and
`
`
`
`Exemplary citations to Huang
`
`
`See, e.g., Huang at [0008] (“The present method accesses a WSDL (Web Service Definition
`Language) description for each vendor, this description being a standard metadata type well
`known in the field for describing web service interfaces. Typically there is one such WSDL
`description for each object or entity (enterprise or organization).”).
`
`Id. at [0042] (“Applications created by the Designer 104 are stored in Extensible Markup
`Language (XML) format as XML definitions 122 in a database 124, and loaded into the Player
`106 as the application 111. The XML definitions are described in the aforementioned
`commonly-assigned patent application, and are described in more detail herein with respect to
`web services-related portions of applications. For the web services-based applications described
`herein, the XML definitions include bindings 102 which associate application components with
`web service object attributes.”).
`
`Id. at [0044] (“More specifically, the WS Object Mapping 123 generates the Generic WS
`Objects 130 for substantially all object types provided by a web service (e.g. an Opportunity
`object type that represents a sales opportunity). The mapping between the Generic WS Object
`Model 130 and the vendor-specific adapters, such as the Siebel WS (Web Services) Adapter
`134, is represented as a WS Object XML definition 126, which is stored in the database 124.”).
`
`Id. at [0045] (“The adapters, e.g., the Siebel WS Adapter 134, interact with the vendor specific
`objects 138 generated by, e.g., Apache Axis. Apache Axis is a programming tool available from
`the Apache Software Foundation. The vendor specific objects 138 are generated by a software
`tool, such as the Axis WSDL2Java command line tool, from vendor specific web service
`interface descriptions, as is known to those skilled in the art. The web service interface
`descriptions are typically provided by the web service vendor in a format such as WSDL.”).
`
`Id. at [0047] (“In the WS Factory API 132, web service data is represented as objects with
`attributes. In the user interfaces of the Designer 104 and Player 106, these objects are presented
`to the user as rows in a table. Each row has one or more columns, which correspond to the
`
`12 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0012
`
`

`

`Patent No. 9,471,287
`
`
`
`Exemplary citations to Huang
`attributes of the object. For example, there could be an object named Opportunity with attributes
`named Opportunity Name and Opportunity Id. There could be any number of Opportunity object
`instances in the web service, and each Opportunity object would have an Opportunity Name and
`Opportunity Id. These objects can be retrieved by the query Object method, created or updated
`by the insert or Update Object method, and deleted by the delete Object method.”).
`
`Id. at [0056] (“FIG. 1B is an illustrative drawing of a binding between an application component
`and a web service according to one example. The binding 193 associates a value 192 of an
`application component 170 with an attribute 155 of a web service 156. The binding 193 is a two-
`way mapping which specifies that a particular web service attribute 155 can be set to the value
`192 of the application component 170, and, conversely, that the value of the application
`component 170 can be set to the value of the attribute 155.”).
`
`Id. at [0067] (“Those web services interactions can be defined using the web services builder
`110 of the application designer 104, typically by using the web service builder 110 to associate
`web service bindings 175 with a button component of the application 111. The web services
`builder 110 can be used to bind an application component to an attribute of a web service, and
`specify whether the interaction type is lookup, insert, modify, or delete.”).
`
`Id. at [0070] (“For lookup interactions, when an application is executed in the Player 106, a user
`may press a button component previously associated with a web service binding to query the
`web service and display a list of one or more values returned by the web service according to the
`binding. The user can then select a value from the list, and the selected value will appear in the
`corresponding application component. The list of values is referred to herein as a Selection
`Lookup Table.”)
`
`Id. at [0081] (“defines a mapping between each attribute of a generic class such as the Account
`class shown above, and a class or classes in the specific web service vendor’s interface.”).
`
`Id. at [0082] (“The Designer 104 uses the XML file to decide the meaning of attributes for the
`
`13 of 66
`
`Adobe v. Express Mobile - IPR2021-01227
`PO_EM287_2005-0013
`
`

`

`Patent No. 9,471,287
`
`
`
`Exemplary citations to Huang
`generic WS object. The XML mapping file can be generated automatically from the vendor
`specific WS object and WSDL definition by using a program named WS Factory.”).
`
`Id. at [0087] (“The structure of the XML mapping file is described by the XML schema shown
`in Appendix A. As specified by the schema, the WS Object definition includes a set of WS
`Object Mapping and WS Attribute Mapping XML elements.”).
`
`Id. at [0106]-[0108] (“FIGS. 4A-4D are illustrative drawings of binding an application
`component in a web services builder. With reference to FIG. 4A, the application can bind an
`application component to a web service to perform any type of operation provided by the web
`service. In particular, an application component can perform Query, Update, Insert, Delete, and
`other types of operations on web services. Query, Update, Insert, and Delete operations can be
`specified using the web services builder. The Data Source Mappings screen 4