Captures Source content (mock-page) and final page URL, as well as template used by the page. It is also the overall parent for the set of descriptors for the page.
Captures page events, like load or pre-load actions, as well as events triggered by elements on the page. Such events like change, select or action events, or other platform specific events, as well as their handlers on the server side. Also captures handler name to handler class, or action path to action class specifications.
Captures all navigational paths that could be traversed from the page. These could be accumulated in global repository and provide symbolic names. Entries could be basis for page flow, navigation rule, and navigation control or restriction specifications.
Aggregation of elements on the page, from perspective of HTML data form, components and sub-element, or mere specification aggregation, like application of presentation attributes to set of elements. Also provides for group specification, like form level validation on client or server side, and wizard sequences.
Captures the data and presentation aspects of elements. Elements are the fundamental building block of web data entry forms. They are various in types and could have many attributes, like data or component bindings, validations, formatting, readable captions, groupings, as well as enable or visibility logic. The element descriptor defines a universal set of types, and provides place holders for the various attributes.
This captures the named objects and classes that are utilized by the view. These could be used for data or component binding, validations, formatting, or any other type of objects used on the page. These definitions could also be referred to by logic or repeat behaviors.
Whereas the behavior-define descriptor captures the objects exposed to the view tier, the behavior-logic captures the methods or attributes of such objects, possibly combined with expression, used as logic on the page. These logics could be applied by elements or segments for the determination of presentation states.
Combined with annotations in the source content, allowing the capture of the break down of pages into composition units. These units or segments could have presentation logic specifications, reuse, inheritance, etc.
Event invocations, composition directives and request query strings, are usually accompanied by parameters. This descriptor provides means of specifying these parameters in object form, collection, maps or fine grain key and attribute sets.
Technologies
