Maria,

Antony Scott wrote:
> Rather than going straight from XSD to HTML, you may want to think
> in terms of a step wise approach which allowed you to specify the
> form structure in a separate (presentation-independent) XML
> document, then populate that document with data from the schema,
> then apply a styling XSLT to render it in HTML. This gives you a
> process which is not bound to any specific schema or output device.
> You may find this is also easier to develop and maintain, in that
> changes to the form design or styling can be expressed in the 'form
> specification' XML or the final XSLT respectively, instead of in a
> single complex XSLT file. You've also got more control over which
> form objects are used for each XSD component.

And if you go this route, you might want to consider XForms from W3C
as your form representation language (http://www.w3.org/TR/xforms/).

Cheers,

Jeni

---
Jeni Tennison
http://www.jenitennison.com/


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list