Issue raised against: Parts_and_Parts_Lists

GENERAL issues

Open issue Issue: 1 by Trine Hansen (3 November 2005) architectural issue
Resolution: Accept. Status: open

Business DEX script. The script that generates the business DEXs require a context in put parameter. In this specific case the context 'NDLO' is applied. This business DEX is developed with the objective that it should be re-usable in other contexts as well. Proposal: remove the context level when generating business DEXs.
Comment: ( )
..(comment text goes here)..

Open issue Issue: 2 by Trine Hansen (3 November 2005) architectural issue
Resolution: Accept. Status: open

This business DEX applies capabilities that at this point of time (November 3, 2005) do not contain Template section, e.g. capabilities representing_properties_textually, representing_properties_numerically, assigning_product_property. The documentation assumes a minimum set of parameters for these capabilities that are mandatory for this specific business DEX.
Comment: ( )

Open issue Issue: 3 by Trine Hansen (3 November 2005) architectural issue
Resolution: Accept. Status: open

Assigning descriptor. This business DEX does not reflect the mapping approach documented in the capability assigning_descriptor. Reason for this is that the business DEX was implemented prior to stable solution was established in the capability.
Comment: ( )

Open issue Issue: 4 by Trine Hansen (3 November 2005) architectural issue
Resolution: Accept. Status: open

This business DEX assumes that the following issue has been taken into account in capability assigning_identifier: A parameter containing the name of the organization that provided the identifier should be included in the template.
Comment: ( )

Open issue Issue: 5 by Trine Hansen (3 November 2005) architectural issue
Resolution: Accept. Status: open

All reference data in this business DEX are provided in the files 'plcs-rdl-pmh.owl' and 'plcs-rdl-pmh.pprj'. The proposed locations in the class hierarchy have been through internal project review and the resulting issues have not been taken into account. The internal project issues will be handled in relation to a harmonization workshop with OASIS.
Comment: ( )

Open issue Issue: 6 by Trine Hansen (3 November 2005) architectural issue
Resolution: Accept. Status: open

The reference data classes used in this business DEX are only documented once, which means that the classes are not repeated in a separate section only in the tables supporting the instance diagrams.
Comment: ( )