Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-Id: <200304021327.FAA24879@s5.servlets.net>
From: "Robert Koberg" <rob@koberg.com>
To: <cocoon-dev@xml.apache.org>
Subject: RE: [RT] Towards a new/another Forms Framework
Date: Wed, 2 Apr 2003 05:27:07 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3E8AC89D.6030001@apache.org>
Thread-Index: AcL5Cngdb0vxL0siSkW/vkG2MhPpBQAD64WQ

Hi,

> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org]
> Sent: Wednesday, April 02, 2003 3:25 AM
> To: cocoon-dev@xml.apache.org


> But I also want to point out something that I'll need a lot in the
> future: the XML datatype in a form.
> 
> I would like to be able to submit an entire XML island into a form
> textarea and have the server-side form handler be able to validate it
> against a particular schema.

But that would be invalid markup. It would be better to use a PUT (I am
still using a POST with a hidden INPUT...). We do the XML Schema validation
client-side and just send the updated XML back to the server for storage.

> 
> That would be *KILLER* for serious content management solutions where
> all the data aggregation from the document can be done via javascript on
> the client side directly (and it's pretty dead easy also to make
> transparently portable for 6th generation browsers!).

I am confused. In the previous paragraph you say you want to submit it to
the server for validation. But in the above para you talk about client-side
validation?

Why not use some schema dialect (XML Schema seems to have achieved critical
mass???) and add a form namespace that indicates the widgets. You get
datatyping for free.

?
-Rob

> 
> This is also why I'm happy to see XMLForm to move into a block: the
> XForm-inflicted mindset is too limiting for what I'm going to need in
> the future for roundtrippable data.
> 
> Stefano.