- From: Hugo Haas <hugo@w3.org>
- Date: Tue, 16 Aug 2005 16:46:16 +0200
- To: Kendall Clark <kendall@monkeyfist.com>
- Cc: www-ws-desc@w3.org, Eric Prud'hommeaux <eric@w3.org>
- Message-ID: <20050816144616.GJ26437@w3.org>
* Kendall Clark <kendall@monkeyfist.com> [2005-08-16 09:58-0400] > On Tue, Aug 16, 2005 at 03:01:45PM +0200, Hugo Haas wrote: […] > > Correct me if I'm wrong, but I don't think that the specification > > prevents this, and I would interpret this as "you may get either one". > > But it's ugly in this case. > > Yes, as written, the spec prevents the above, near as I can tell. It does so > because *if* you have a binding that uses multipart/form-data as > inputSerialization, then you have to use multipart style for that binding. Oh, you're right, the multipart style is missing here, and it says: The localPart of the element's QName MUST be the same as the Interface Operation component's name. I am actually unsure about the motivation and need for this requirement of the style. > In which case the nice single operation, query, really does become two > separate operations: different styles and different output serializations. > But then you really need *four* operations: > > query1: GET, IRI style, application/sparql-results+xml > query2: GET, IRI style, application/rdf+xml > query3: POST, multipart style, application/sparql-results+xml > query4: POST, multipart style, application/rdf+xml > > Wow, now *that's* confusing. And ugly. Really, really ugly. Well, actually, you could have only 2 operations, and 2 bindings of those, one for GET and one for POST, supposing that query[1-4] are the same input message. -- Hugo Haas - W3C mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Tuesday, 16 August 2005 14:46:22 UTC