#79 DEX:BoM Class documentation should be taken from the BoM XMI

[Patrick Houbaux]

It would be better to take the documentation of the classes and properties directly from the XMI (mdxml) instead of having to fill another xml file : i.e. the biz_info_model_dfn.xml for instance.

[Rob Bodington]

They reason why it is not direct from the XMI is that teh XMI will only support HTML or direct text.

We want to be able to use the XML element available in PLCSlib for referencing ref data, template etc.

I guess a compromise would be to have a switch that allows both

[Rob Bodington]

One approach is to extract the definitions from the XMI.
So run

ant extract_defn -DMDIN="data/contexts/LifeCycleSupport/boms/Common/dvlp/LifeCycleSupportCommonBoM.mdxml" -DMDOUT="data/contexts/LifeCycleSupport/boms/Common/biz_info_model_dfn.xml" -DPACKAGE="Common"

This will produce:
data/contexts/LifeCycleSupport/boms/Common/biz_info_model_dfn.xml

which contains all the definitions extracted from the XMI

[Rob Bodington]

/cvsroot/plcslib/plcslib/xsl/utils/extract_model_definitions.xsl,v <-- extract_model_definitions.xsl
new revision: 1.4; previous revision: 1.3

[Rob Bodington]

Need to support enumerations as well

[Rob Bodington]

/cvsroot/plcslib/plcslib/xsl/boms/bom.xsl,v <-- bom.xsl
new revision: 1.2; previous revision: 1.1
done
Checking in xsl/models/model_definitions.xsl;
/cvsroot/plcslib/plcslib/xsl/models/model_definitions.xsl,v <-- model_definitions.xsl
new revision: 1.21; previous revision: 1.20
done
Checking in xsl/common.xsl;
/cvsroot/plcslib/plcslib/xsl/common.xsl,v <-- common.xsl
new revision: 1.54; previous revision: 1.53
done
Checking in xsl/magicdraw_diagrams.xsl;
/cvsroot/plcslib/plcslib/xsl/magicdraw_diagrams.xsl,v <-- magicdraw_diagrams.xsl
new revision: 1.15; previous revision: 1.14