DEX000 "DEX Template"

[<Trine.Hansen@dnv.com>]

Title: DEX000 "DEX Template"

All.
Some backgroud information for the proposed DEX template D000:
Business objective
The current DEXLib documentation may be interpreted and implemented as configurable systems or translators. It is suited for a business scenario that relies on the use of Exchange Agreements and tailoring of translators. Exchange of precise business data must be defined as local solutions between exchange parties. The precise business data solutions should be standardized as they are developed.

The DEX 000 template for development of DEXes is a proposed extension of the DEXLib documentation intended to minimize, and eventually eliminate, the need for detailed Exchange Agreements, and the need for translator tailoring. When adding business data precision as exemplified in DEX 000, DEXLib will precisely define interpretations and requirements to implementations and to business data for a DEX. The standardized documentation will become extensive and will be subject to continuous control.

Trade-off considerations apply when deciding whether to put implementation constraints on Exchange Agreements and translator tailoring, or on standardization and DEXLib. Such considerations apply e.g. to

• cost to develop the standard,
• cost to implement the standard,
• time and cost to negotiate and define Exchange Agreements.
• time to establish a new exchange,
• extent of usage of the standard,
• will to control and maintain the standard.

In our opinion, none of the two alternative approaches represent the ultimate answer. However, both solutions are a move in the right direction. Our preference is clearly in the direction of increased presicion as this will improve quality and facilitates reuse and centralized maintenance; Exchange Agreements are not standardized, and may exist in several languages.

Technical
The recommendations in DEX 000 will increase the documentation precision for a DEX, require added functionality to the DEXLib tools, and increase the quantity of objects to be standardized. On the other hand, the components developed will be reusable as they are, the room for interpretation will be eliminated, and data validation will be facilitated.

The growth of documentation is mainly caused by the addition of new layers to capabilities and DEXes, and by facilitating availability for reuse of standardized objects.

The capabilities in DEXLib are in the DEX 000 template tailored to specific business constraints by specializations, and specialized capabilities are instantiated for the specific business data to be exchanged. The added documentation consists, in addition to the added level of granularity, of constraints, rules and reference data.

The specific DEXes are populated by instantiated capabilities, and are instantiations of the more generic DEXes at the level currently defined in DEXLib. Hence, DEX 000 when expanded to satisfy an agreed business domain will become an instantiation of OASIS DEX 001.

Specialized and instantiated capabilities and DEXs are subject to standardization.

Best Regards
Trine Hansen
UCTNO940, Information Quality Management
Det Norske Veritas AS
( + 47 67 57 96 38 (office)
( + 47 90 83 44 24 (mobile)
* trine.hansen@dnv.com
http://www.dnv.com

**************************************************************
Neither the confidentiality nor the integrity of this message can be vouched for following transmission on the Internet. All messages sent to a DNV email addressee are swept by Sybari Antigen for the presence of malicious code. DNV acknowledges that unsolicited email represents a potential security risk, and DNVs filters to block unwanted emails are therefore continuously adjusted. DNV has disabled "out of office" replies to Internet transmitted e-mail. 
**************************************************************