From KPiroumian@protek.com  Sat May 18 14:21:00 2002
Return-Path: <KPiroumian@protek.com>
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 92462 invoked from network); 18 May 2002 14:21:00 -0000
Received: from relay.flagship.ru (213.221.9.5)
  by daedalus.apache.org with SMTP; 18 May 2002 14:21:00 -0000
Received: from POSTMAN.flagship.ru (postman.flagship.ru [213.221.9.130])
	by relay.flagship.ru (8.11.4/8.11.4) with ESMTP id g4IEL1J33130
	for <forrest-dev@xml.apache.org>; Sat, 18 May 2002 18:21:01 +0400 (MSD)
Received: by POSTMAN.flagship.ru with Internet Mail Service (5.5.2653.19)
	id <LFLXYVK0>; Sat, 18 May 2002 18:21:58 +0400
Message-ID: <C953AD4EA2709541B040E3683231B75408C0B1@POSTMAN.flagship.ru>
From: Piroumian Konstantin <KPiroumian@protek.com>
To: "'forrest-dev@xml.apache.org'" <forrest-dev@xml.apache.org>
Subject: RE: draft howto dtd
Date: Sat, 18 May 2002 18:21:57 +0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="koi8-r"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> 
> Konstantin, (;-))

What a strange mail server is that MS Exchange ;)

> 
> >
> > 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.

I think that you got me wrong. I don't speak about the functionalities and
interfaces of components or other Java classes. Almost all of the
transformers and logicsheets has some markup, e.g. i18n transformer has:
	i18n:text
	i18n:date
	i18n:date-time
etc. some other elements. Every element has its own attributes, and those
attributes has a set of allowed values. Say:
<i18n:date-time format="dd:MM:yyyy hh:mm:ss EEE" locale="en_GB" .../>.

So, my idea is to have Schema for every transformer or logicsheet. Some
generators also can have a defined format (e.g. Directory Generator). But
why I am saying all this, I'm sure you know it very well.

So, what is my idea: each of this markups could be transformed into HTML
(PDF, text) docs automatically if there were a Schema for them. Those docs
could be included into existing docs written by hand.

Though, I've almost finished the element/attribute description part of i18n
transformer xdoc that I've written without any automagics. After I finish it
I am going to create an XSD for it. ;)

I think that we all agreed that having XSDs for Forrest/docs is not
necessary now, didn't we? 

Konstantin.

> 
> </Steven>
>