Browse Prior Art Database

Applying Vocabulary Mappings During Form Generation

IP.com Disclosure Number: IPCOM000132061D
Original Publication Date: 2005-Nov-30
Included in the Prior Art Database: 2005-Nov-30
Document File: 2 page(s) / 29K

Publishing Venue

IBM

Abstract

Data-driven form-generation techniques do not take into account the possible existence of "vocabulary mappings" (sometimes called "code lists" or simply "vocabularies") within the data model from which forms may be generated. A "vocabulary mapping" is a set of pairs of data items, in which the two items in a given pair are: a string containing text for the item, intended to identify the item in a human-readable fashion that would allow an end-user to uniquely and properly identify the item within a list of all items in the set, and a corresponding data item (of any data type), which contains the value for the item that is consumable by a processor (or "service" or "server"). These vocabularies, often surfaced in XML, are key to data models and business processes used by a variety of organizations.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Applying Vocabulary Mappings During Form Generation

An example of a commonly-used industry vocabulary is the Public Health Information Network (PHIN) vocabulary set for health care and disease management ( http://www.cdc.gov/phin/vocabulary/). Furthermore, an organization may use multiple vocabularies, and each of those vocabularies may be provided by a different third-party organization that may change the vocabularies without the using organization's foreknowledge or control. Current solutions include the cumbersome techniques of manual insertion of vocabulary mapping values directly into a form, or the manual creation of a reference to an existing code list.

Therefore, a way to include vocabularies in form generation while allowing them to remain de-coupled from the form itself, and even decoupled from other instance data and metadata describing the form, is required. The XForms standard ( http://www.w3.org/TR/xforms/) provides for such de-coupling mechanisms, and also provides for the specification of a set of values for display and a corresponding set of values to be submitted. The technology described herein assumes that such functionality will be available in the generated form.

A solution involves a methodology whereby vocabularies may be applied to a form through the use of mappings between instance nodes that permit the generation of references to the vocabulary data itself. The mechanisms described herein assume the previous existence of form-generation technology.

The following system components are involved in the process of discovering code lists and referencing them from a control during form generation"

Form Generator Controller: The component/process...