Form Filling

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Introduction

This document describes how the Persona Data Model 2.0 can be used to support a Javascript form filling application (app-card) supported by an active client. We will illustrate by walking through the following scenario rom a cold start (i.e. a clean install of a browser-integrated active client):

1. Alice points her browser at staples.com and proceeds to try to buy a stapler. She eventually arrives at a checkout page
2. Active client attempts to fill the form (this will fail as the active client has no data about Alice at this point)
3. Alice fills in the form and submits it
4. Active client builds persona structures from what it has observed
5. Alice points her browser at bestbuy.com and proceeds to buy a new CD
6. Active client attempts to assist Alice in filling the form from persona data
7. Alice edits/corrects form elements and submits it
8. Active client builds persona structures from what it has observed

Data structures at start

RootContext

Contents of the RootContext:

Note: no other contexts exist!

Step 1

Alice eventually ends up at this form:

The form filling Javascript will make a getExAttributes() call into the PDS Client API (of the active client) passing (among other parameters) the above form's submit URL. This causes the PDS Client to instantiate a new ProfileContext whose name is derived from the form submit URL (and Alice's id) and whose schema (ontology) is "staples.com.owl" (which in turn is based on PDM (persona.owl)). This staples.com.owl ontology includes the mapping rules to map staples-specific HTML form elements into the PDM.

Alice's staples ProfileContext is (other than the ontology definitions) empty.