FMV agrees with Rob’s
suggested approach to; ” fix the schema
and document the changes”.
Regards,
Mats
|
____________________________________________________ |
|
|
|
Mats Nilsson Telephone: +46 8 782 47 24 |
|
____________________________________________________ |
|
Från: Rob Bodington
[mailto:rob.bodington@eurostep.com]
Skickat: den 2 februari 2009 12:41
Till:
plcs-tog@lists.oasis-open.org
Kopia:
LogOps-PolLogInfoJtArch2C1@mod.uk
Ämne: [plcs-tog] PLCS backward
compatability
Hi
During our analysis of the changes made by other APS to the underlying
modules of AP239 we have identified that they have change the assemblies
modules.
In doing this change they have “lost “ 3 inherited
attributes from next_assembly_usage
We do not explicitly use these attributes in PLCS perspective ….
However, the change will make all existing P21 files invalid.
We have also identified that the product-category module should be
removed from the AP as we are using reference data for this categorizing parts.
When discussing this with AP210, AP233, AP203 we agreed that we should remove
product-category completely.
This is desirable, but again, will make existing Part21 and Part 28
file incompatible.
The ap239 ed2 development team would like some guidance from the TOG as
to what the position should be wrt to backward compatibility.
Do we insist on backward compatibility, or do we fix the schema?
My view is that we should fix the schema and document the changes.
We need to make a decision quite quickly as that will influence our discussions
with the other APs.
I have also not raised this issue with the wider TC – should we?
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
Skype: rbodington
Eurostep Limited. Registered
in
Registered Office: