Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Schema value restriction scoping

IP.com Disclosure Number: IPCOM000239029D
Publication Date: 2014-Oct-02
Document File: 2 page(s) / 23K

Publishing Venue

The IP.com Prior Art Database


This article details the methods to provide scope to restrictions within schema definitions of message data and enabling the restrictions imposed to limit the available options for child elements.

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

Page 01 of 2

Schema value restriction scoping

Messaging systems use schemas to describe message data - there are multiple languages in which to model data (i.e. XSD etc.) and each enable the developer to impose constraints on message contents - for instance defining the character range or pattern for a particular data type.


These message definitions fall short of providing a method to simply identify possible character sets within a message structure without examining all data types or providing a scope / constraint globally or at different scopes.

    The proposed solution enables constraints to be placed on parent / complex elements - which are propagated to any child elements. For instance, a global constraint can be placed on a top level data structure element to enforce only characters a-z are allowed. This constraint can apply to any child elements of the top level / complex element.

    Existing technology allows a developer to set restrictions on content for an element, the following example restricting the element "initials" to only allow exactly 3 of the lower-case or upper-case letters from a-z:

The proposed solution enables a complex / enclosing element to make restrictions on all child / enclosed elements. The example below defines complex element "employee" with 2 child elements ("firstname" and "lastname"), there is also a restriction placed at the "employee" level that any values of any child elements must conform to...