W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2006

Re: why */* in inputSerialization of POST binding?

From: Dan Connolly <connolly@w3.org>
Date: Wed, 11 Jan 2006 11:16:56 -0600
To: Kendall Clark <kendall@monkeyfist.com>
Cc: dawg mailing list <public-rdf-dawg@w3.org>
Message-Id: <1136999816.19546.190.camel@dirk.w3.org>

On Wed, 2006-01-11 at 11:21 -0500, Kendall Clark wrote:
> Dan,
> 
> You seemed clear during Tues telcon that if I changed the  
> inputSerialization of the POST binding at all, I should add the */*  
> type specifier to application/x-www-form-urlencoded instead of what I  
> would have expected to add, namely, application/xml.

I meant to say */* for _output_ serialization; i.e. to say
that text/n3 is OK.


> I expected to add application/xml because the only other way to spell  
> SPARQL queries, formally or informally, is through XML serialization  
> of the abstract syntax. That's the only other way anyone's talked  
> about, as I recall.

Fair enough.

> 
> I'm confused about the use of */* here, and as a result, I'm not  
> going to add anything till I'm less confused. :>
> 
> Cheers,
> Kendall
-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E
Received on Wednesday, 11 January 2006 17:17:03 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:25 GMT