[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: DEXlib infrastructure issue - use of EXPRESS types as template parameters
Hi I have just raised and addressed this infrastructure issue
<!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> <issue id="RBN-63" type="infrastructure" status="closed" category="minor_technical" by="Rob Bodington" date="07-01-02"> <description> An input parameter can currently only be defined as a STRING | NUMBER | ENUMERATION| INTEGER | REAL | BOOLEAN | LOGICAL | CLASS | URN | URL | ENTITY | SELECT It should be possible to define the parameter as an EXPRESS defined type. E.g. TYPE year_number = INTEGER; END_TYPE; should be defined as: <param_in name="year" type="TYPE" defined_type="year_number"> </description>
<comment by="Rob Bodington" date="07-01-02"> <description> Updated the DTD (dexlib/dtd/dex/templates.ent) to allow this: <!ELEMENT param_in (classifications?, description?)> <!ATTLIST param_in name CDATA #REQUIRED type (STRING | NUMBER | ENUMERATION| INTEGER | REAL | BOOLEAN | LOGICAL | CLASS | URN | URL | ENTITY | SELECT | TYPE) #IMPLIED select_type CDATA #IMPLIED entity_type CDATA #IMPLIED defined_type CDATA #IMPLIED value CDATA #IMPLIED optional (yes | no) "no" default CDATA #IMPLIED
Updated the XSL: dexlib/xsl/dex/templates.xsl </description> </comment> </issue>
Regards -------------------------------------------
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]