Stefano Mazzocchi wrote:
I would do
http://apache.org/cocoon/cforms/1.0#definition
so that in the future there is an algorithmical way to get to the version.
Hehe, looks like RDF really has infected your mind ;-)
good eye :-)
But I like this notation, which makes definition, binding, etc children of the more global forms/1.0 entity.
BTW, does this fit with RDDL (I guess yes)?
what's behind the # sign is supposed to be meaningful on the client side. This means that an RDDL document for cocoon forms would have to include specifics for everything that it's included in that particular namespace, then it would have XML IDs that map those defintions and the client would have to reach those and make sense out of them.
in short, yes, it does fit, it imposes a little bit more practice on the client side and forces the server side to glue all definitions in one response.
-- Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
