Thus adding transformation capabilities to APEX that are supported by XSLT but not by the Architectural Form Definition Requirements is simple. The XSLToolbox distribution includes an APEX customization example. Since APEX does not read an architecture's DTD, it cannot pick up any DTD-specified information about the architecture. As a result APEX does not pick up defaulted architectural attribute values, nor does it allow architectures to inherit from other architectures. Also, because APEX cannot determine where an architecture allows character data, cArcIgnD causes APEX always to ignore data in non-architectural elements.
APEX permits only simple attribute renaming.
If the architecture specifies a default value for this attribute, removing the attribute from the architectural document has the effect of replacing the attribute's value with the default. Note This is a non-conforming addition. The architecture use declaration processing instruction is ignored. Information about an architecture is instead conveyed to APEX through stylesheet parameters.