RE: [plcs-tog] Summary of ap239 / dexlib issue

I have added option 5) which is convert dexlib to use ap239 ed2

Regards
Rob

--------------------------------------------------------------------------------
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1452 810 960
Mobile: +44 (0)7796 176 401
Skype: rbodington

Eurostep Limited. Registered in England and Wales No.03049099

Registered Office: Cwttir Lane, St. Asaph, Denbighshire LL17 0LQ.

From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 16 March 2009 06:48
To: plcs-tog@lists.oasis-open.org
Cc: Peter Bergström
Subject: [plcs-tog] Summary of ap239 / dexlib issue

Here is a summary of the points about AP239 ed2 made on the conf call

First some background:

1) AP239 ed1 published 2004 – call it ap239_iso_ed1_schema

2) DEXlib developed – some changes to ap239_iso_ed1_schema call it ap239_oasis_ed1_schema were made.

3) Av DEX + Task DEX has been published for ballot with ap239_oasis_ed1_schema

4) AP239 ed2 in development – call it ap239_iso_ed2_schema

5) Av DEX + Task DEX have been balloted, but not yet had all ballot issues addressed

The question is, at what point do the ed2 changes get rolled back in the schema.

On the call 4 approaches were described:

1) Remove the changes to ap239_oasis_ed1_schema and make DEXlib use ap239_iso_ed1_schema

· Existing templates will have to change

· Software implementation will have to be updated to reflect the changes

HGM> and all changed again to match ap239_iso_ed2_schema

HGM> Loss of capability for existing draft DEX

HGM> Only two standard schemas to manage across, plus one OASIS where already implemented

2) Allow no changes to ap239_oasis_ed1_schema and publish the completed Av DEX + Task DEX with ap239_oasis_ed1_schema. In parallel develop DEXlib2 that addresses some template issues, and brings in the changes from ap239_iso_ed2_schema

· No existing templates change – we ignore a number of the ballot comments

· No change to Software implementation at this stage. They continue to use some complex mapping and misuse reference data.

· DEXlib2 will change templates

· Future software implementation will have to change to use the new edition of dexlib - DEXlib2

HGM> Published DEX will need to be updated to new schema eventually

HGM> One OASIS and one standard schema to address

3) As part of the ballot resolution for the Av DEX + Task DEX, bring in some of the changes with no compatibility issues on a case by case basis:

· If the changes have no compatibility issues, i.e. new entities or select extensions, incorporate the change and create ap239_oasis_ed2_schema which is part of the Av DEX + Task DEX publication

· In parallel develop DEXlib2 that addresses some template issues, and brings in all the changes from ap239_iso_ed2_schema

· This should not impact existing templates. New business templates may be created, but no new OASIS templates.

· Software implementation will have to accommodate new entities i.e. read them, but as no new oasis templates, not be required to do anything with them.

· Future software implementation will have to change to use the new edition of dexlib - DEXlib2

HGM> Two OASIS and one standard schema to address

HGM> Published DEX and implementations will eventually need to be updated to DEXlib2

4) As part of the ballot resolution for the Av DEX + Task DEX, bring in some of the changes with compatibility issues

· change and create ap239_oasis_ed2_schema which is part of the Av DEX + Task DEX publication

· In parallel develop DEXlib2 that addresses some template issues, and brings in all the changes from ap239_iso_ed2_schema

· Some template changes

· Software implementations change – but will be more stable in the long run

HGM> Two OASIS and one standard schema to address

HGM> Published DEX and implementations will still need to be updated to DEXlib2

5) Make DEXlib use ap239_oasis_ed2_schema

· Rework of templates

HGM> I think you mean iso_ed2

HGM> One OASIS and one ISO schema to manage

HGM> must be some implementation rework here

Regards
Rob

Eurostep Limited. Registered in England and Wales No.03049099

Registered Office: Cwttir Lane, St. Asaph, Denbighshire LL17 0LQ.

plcs-tog message