Hi Trine
I agree with Mats - I am not sure what is
meant by “allowance”.
We could propose a better title once we
have seen the scope and business introduction of the DEX.
I was wondering why you are proposing to document
the rules in Word – why not include them in the capability or DEX XML?
Also, what do you mean by mapping tables?
Mapping of what to what?
Are you suggesting that we incorporate the
ARM to MIM mappings here?
-----Original Message-----
From: mats.nilsson@fmv.se
[mailto:mats.nilsson@fmv.se]
Sent: 14 February 2005 06:55
To: Trine.Hansen@dnv.com;
plcs@lists.oasis-open.org
Cc: Leif.Tonning@dnv.com
Subject: SV: [plcs] Coming upload
of proposed DEX template to DEXLib
I'm not an expert in english, but
'allowance' is to me something including the passing of money from one person
to another (often a parent to a child). How does this match with the 'part
list'? Any opinions from anyone more familiar with english than me?
Looking forward to the coming upload!
-----Ursprungligt meddelande-----
Från: Trine.Hansen@dnv.com
[mailto:Trine.Hansen@dnv.com]
Skickat: den 11 februari 2005
16:34
Till: plcs@lists.oasis-open.org
Kopia: Leif.Tonning@dnv.com
Ämne: [plcs] Coming upload of
proposed DEX template to DEXLib
Dear
all.
Based
on agreements made and solutions found during the Synchronization worshops, and
in accordance with decisions of the OASIS TC meetings in Norfolk and Bristol,
the NDLO pilot project will upload a sample DEX 010 to DEXLib. The intention is
that 'DEX 010 Allowance part list' will become a template for documentation of
future DEX specializations and uploadings.
The
main reason for the additional documentation that will be proposed, is the need
to add precision for DEX implementation and data validation.
It
is appreciated that an Exchange Agreement between data exchange parties may be
implemented to add the needed precision to the current documentation in DEXLib,
but time and effort to negotiate and develop Exchange Agreeements and the
related translators may for some scenarios be prohibitive in a fast changing
business environment. The intent of the added precision in DEXLib is with
reasonable effort to minimize time and cost to connect with new data exchange
parties.
DEX
010 is not intended to be correct nor complete from a business domain
perspective. The main focus is to define the level of detail, and the extent of
documentation needed for a DEX that shall fullfill the above objectives. DEX
010 may later be enhanced to meet business objectives once the template is
agreed. It is therefore of interest that experts offer their opinion and advice
on the uploaded DEX 010 so that an agreed template may be derived for use as
soon as feasible.
The
main new features to DEXLib that are added with DEX 010 are
- Existing capabilities are specialized and instantiated
to meet business objectives.
- DEX 010 may be considered as a specialization of OASIS
DEX 001, but this has will not be done for the current upload.
- Mapping tables are added to the specialized
capabilities.
- Reference data are added to the specialized
capabilities.
- Different rule types are added in Word and in Express
to the capabilities, and to DEX 010.
- A DEX 010 instantiation
diagram is part of the DEX documentation.
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.
**************************************************************