Browse Prior Art Database

Multiple validation variants of a single format representation expressed in a single metadata representation

IP.com Disclosure Number: IPCOM000198683D
Publication Date: 2010-Aug-12
Document File: 2 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for representing multiple levels of validation in one metadata model while parsing-out the validation rules into separate models at design time; each generated model is deployed separately at run-time. This yields both the design and maintenance efficiencies of one model as well as the run-time efficiencies of separate models.

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

Page 1 of 2

Multiple validation variants of a single format representation expressed in a single metadata representation

When working with complex data formats, it is common to have multiple levels of validation requirements defined for a single format. This situation can be modeled in multiple ways using metdata model representations. The most common way to model this is to have one metadata representation for each variant of the format. From a run-time perspective this is most advantageous as it allows the model that represents the data to be as simple as possible (the model has the appropriate level of validation rules for the data that is being processed).

From a model development and maintenance perspective, this approach is not ideal as it requires that the core of the metadata representation be duplicated for each validation variant. The other common approach is to have one large metadata model that is used at run-time to include all the validation level rules. This is also not ideal as the model rules become complex and costly at run-time.

Traditionally, the metadata definitions for each level of validation are maintained, stored, and distributed as an individual component. However, when there are many levels of validation per structure this leads to a great amount of repetitive maintenance which leads to higher cost of maintenance and increased likelihood of user maintenance errors.

This disclosure discusses a methodology for representing multiple levels of validation in one metadata model but parsing-out the validation rules into separate models at design time; each generated model is deployed separately at run-time. This yields both the design and maintenance efficiencies of one model as well as the run-time efficiencies of separate models.

The concept of a Master Model is a way to represent multiple validation variants of one format as one metadata representation. The single metadata representation includes coded rules that express varying levels of validation rules. The method then incorporates a process to take the Master Model and create multiple Validation level specific models from it by extracting the hierarchical structure of the format, each component's cardinality, and appropriately coded validation rules.

This allows engineers to develop and maintain only one metadata representation whilst being able to distribute multiple physical representations. An alternative is to develop and maintain separate metadata representations - one per validation variant which would be costly from a design/maintenance standpoint. Another alternative is to design/maintain the rules on one representation and use that representation at run-time. This would be more costly from a run-time perspective.

Once engineers have a vision of how many distributable metadata re...