Ah, re-reading your question, I think maybe you are talking about the format of the arguments, not the concept of simple vs formal schemes. Apologies.
So, in which case, no... there isn't a direct way, but the server can attempt to unmarshal the query string as if formal argument (ie a URL encoded json string), otherwise fallback to attempting to treat as a set of key=value pairs. The Isis implementation also has (proprietary) support that combines these; the special query param "x-isis-query-string" can be used whose value is the URL encoded json string. I added this mostly for my own testing... my recollection is that when using the "Postman" extension (in Chrome) for a post/put, it used to assume foo=bar syntax. (since been generalized to accept anything as the post/put body). HTH Dan On 16 June 2016 at 16:56, Dan Haywood <[email protected]> wrote: > Hi Kevin, > > sorry not to reply sooner on this. > > The simple vs formal scheme relates to the representations that are > returned from a resource, not the representations of the arguments sent to > the resource. So, the format should be the same irrespective of which > scheme type your RO implementation supports. > > The relevant sections (of RO v1.0 spec) is 2.9 and 2.10. > > HTH > Dan > > > > On 28 May 2016 at 19:15, Kevin Lewandowski <[email protected]> > wrote: > >> Hi, all. I'm working on an early python implementation of RO and had a >> question about passing arguments. >> >> In an Action Invoke resource, is there a way to tell if the client is >> sending arguments in the Simple scheme vs Formal Scheme? I can't find this >> anywhere in the spec. >> >> thanks, >> >> Kevin >> > >
