Michael Kay wrote:
>> I would like to support variable content in certain elements
>> of my schema based on the elements belonging to a common type
>> hierarchy. I want to make sure that the approach I take is:
>>
>>
...
>> * Well suited for processing instance documents by XSLT such that
>> adding new types to the variable content hierarchy does not
>> require modifying the XSLT for processing the common elements and
>> attributes of the variable content base type
>>
>>
> XSLT 2.0 with schema-awareness can handle both type hierarchies and
> substitution groups. For example you can match all elements in the
> substitution group of event using
>
> <xsl:template match="schema-element(event)">
>
> and you can match all elements of type event-type using
>
> <xsl:template match="element(*, event-type)">
>
> and of course in both cases you can match any name at any level of the
> hierarchy.
>
On XSLT support... Am I correct that element substitution will not work
well unless XSLT processor is schema aware but type substitution will?
AFIK, there are *NO* open source, royalty free schema aware XSLT
processors available. It seems that this would make type substitution a
better fit for open source, royalty free non-schema-aware XSLT
processors available.
--
Regards,
Farrukh Najmi
Web: http://www.wellfleetsoftware.com
