Glossary


A   B   C   D   E   F   G   H    I   J    K    L   M   N   O    P   Q   R   S    T   U   V   W   X   Y   Z

Integrator
The integrator produces code to be executed in the environment of the deployment server. It gathers the respective information from the various repositories and combines them accordingly.

Interaction Templates
A template that includes the basic interaction between the delivered service and the end user. The interaction template may specify:
  • Style of navigation between forms in multi-form services (back-next-finish, index form with references to individual forms etc.)
  • Use of confirmation screens (every form, once before final submittal, never)
  • Style of error presentations (separate window, within the form etc)

Interaction Templates Repository
A repository containing all available Interaction Templates.

Knowledge Repository
The knowledge repository will contain all the knowledge items (examples, best practices, legislation, guidelines) along with structures facilitating access to it, such as knowledge maps. Items within the knowledge repository may reference or be referenced from items in other repositories; e.g. an example on filling in a TSE may reference the specific TSE and/or be referenced from it.

Layout
Contains static attributes of presentation of a Transaction Service. These static attributes will include colour schemes, font families and sizes, border designations etc. A layout may also contain guidelines to the designer about style of placement of elements on the form, pieces of advice regarding form size, or even automated checks that scan for guideline violations.

Layout Repository
A repository containing all available Layouts.

Process Management Information
Information about flow control, data control/integrity constraints, user profiles/roles and preconditions/postconditions.

Transaction Service
A set of forms that implement a specific service. It contains TSEs, validation constraints, pre- and post-conditions and the layout to be used.

Transaction Service Elements (TSEs)
Transaction Service Elements (TSEs) are considered as the basic building block of an e-service. They are used to represent basic data types used within the organization. TSEs are not to be confused with basic data types as handled by programming languages. They are not just strings, integers, floats etc: TSEs are conceptual constructs that map onto the organization\'s practices. A TSE represents a real-world entity and its attributes model this entity\'s characteristics in a self-contained manner. TSEs are defined in an XML format and could contain the following properties:
  • Unique identifier
  • Machine-oriented data type, e.g. integer, string, float etc.
  • Data type format rules
  • Presentational info, possibly according to dissemination channel, e.g. length of data, number of decimals, colour, etc.
  • Interface definitions for transforming the TSE values from and to different formats and for communicating with the SmartGov agent they refer to (for exchange of data with third-party systems)
  • Generic name and/or service specific aliases (or handles)
  • Generic validation constraints/conditions. Service specific constraints and/or more detailed ones are considered to belong to the Knowledge Repository.
TSEs are "cloned" when the time comes to implement a new service. The properties of the cloned TSEs can be overridden with service-specific properties. These properties are expected to be specialized versions of the properties offered by the generic TSE they clone, suitable for the service they refer to.

Transaction Service Repository
A repository containing all available Transaction Services.

TSE group
TSEs can be grouped arbitrarily forming TSE groups. TSE groups like TSEs are defined in an XML format and could contain the following properties:
  • Unique identifier
  • Presentational info, possibly according to dissemination channel
  • Interface definitions for communicating with the SmartGov agent they refer to (for exchange of data with third-party systems)
  • Generic name and/or service specific aliases (or handles)
  • Generic validation constraints/conditions
  • Active code to be executed when they are instantiated
A TSE group cannot be used as an element to form another TSE group.

TSE Repository
A repository containing all available TSEs and TSE groups. A TSE repository is needed to coordinate access and to ensure overall consistency, e.g. that referenced items are not deleted in a later stage.



Last updated: November 2002

















Smart Gov logo
A Governmental Knowledge - based Platform for Public Sector Online Services

Languages:
greek english spanish
german
裂咨是 优松牧

门蜕是 信焉醚林

辛逝粤 叛昧由劣

诱团衙猎庞

团 柿 难劣郧焉显窃庞

列显潘庞塘粤

那滔由耪优捎

盟儆恿焉

诱湍庞滔


判墒仙唾蜕

信焉涎捎膛颓 醒嫌铝忧

ist logo
IST 5th Framework Programme Key Action Line: On-line support for democratic processes.

Design by  
Archetypon logo
Programming and Hosting by 
e-Gov Lab Logo
bobby