forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Noels" <stev...@outerthought.org>
Subject RE: draft howto dtd
Date Sat, 18 May 2002 13:50:43 GMT
Konstantin, (;-))

>
> Having Schemas first and implementation next for all the
> transformers/logicsheets would allow to keep in sync either
> the source code
> and the docs. I can imagine something like this in a transformer docs:
>
> <section>
>   <title>Markup</title>
>   <cinclude:include href="cocoon:/dtd/i18n.xsd" />
> </section>
>
> And a pipeline like:
> <match pattern="*.xsd">
>       <generate src="{1}.xsd" />
>       <transform src="xsd2table.xsl" />
>       <serialize />
> </match>
>
> A stylesheet can generate a table like: "element |
> description | attributes"
> and even have jumps to details like:
> - Element
>       - Description
>       [- Attributes
>               - Descriptions]*
>
> Am I dreaming too much? ;)
>

I guess so ;-)

Problem is that most components need code at some level, and apparently
people are happier describing functionalities & interfaces using code
instead of declarative XML grammars.

</Steven>


Mime
View raw message