So, are you suggesting to provide a way to translate from URL-encoded
pairs into HTML?
Or, are you thinking about determining and documenting common patterns
of using URL-encoded key/value pairs?
Or is it something completely different?
I hope my last mail cleared up that question (btw, I am not sure what your a driving at, sounds interesting too).
My aim is to "enhance" a common html-form in such a way, that pre- and post-conditions are machine readable and as such become first-class citizens in a service-oriented environment.
I said conditions and not inputs/outputs as (for now) I am assuming them to be the same talking about state-less services.
_______________________________________________ microformats-rest mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-rest
