From: Marc Hadley <Marc.Hadley_at_Sun.COM>
Date: Wed, 08 Nov 2006 14:26:51 -0500

On Nov 8, 2006, at 6:18 AM, Jerome Louvel wrote:
>
>> Perhaps it would be useful to be able to specify the media-type used
>> for the query component in the WADL description, defaulting to
>> application/x-www-form-urlencoded ? That way if a new format for
>> query components is desired it can be utilized without revising the
>> specification. Interop would, of course, depend on client and server
>> both understanding the query component format.
>
> Having profiles for the query part makes sense.

I've been working on a revision of the specification and code that
addresses some other issues and use cases that have been raised. I'll
add this to the specification and hopefully get something out for
people to review in the next couple of days.

Thanks,
Marc.

> I would see three initial
> one:
> 1) Web form (application/x-www-form-urlencoded)
> 2) Matrix (variant of Web form allowing parameters with no value)
> 3) Pattern (where parameters could be used like
> "{param1.name}={param1.value}") the advantage would be to leverage the
> parameters declaration/typing like in profile (1).
>
> Best regards,
> Jerome
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_wadl.dev.java.net
> For additional commands, e-mail: users-help_at_wadl.dev.java.net
>

---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.