W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > September 2005

fault serialization

From: Kendall Clark <kendall@monkeyfist.com>
Date: Wed, 14 Sep 2005 11:43:42 -0400
To: public-ws-desc-comments@w3.org
Cc: Dan Connolly <connolly@w3.org>
Message-ID: <20050914154342.GF17062@monkeyfist.com>


I'm writing on behalf of DAWG, which is using WSDL 2.0 to specify the SPARQL
Protocol for RDF [1]. We have a couple of LC comments about WSDL 2.0, and
I'll be sending each one in a separate message.

We'd like to avoid having to require a particular fault serialization type
in our HTTP bindings. That is, we anticipate SPARQL services being free to
serialize fault messages in several different Media Types: plain text, HTML,
XML, RDF, etc.

If whttp:faultSerialization is a required property and the default value
doesn't describe our service, what alternative do we have?

Hugo Haas responded to my initial comments thus:

  Maybe the fault serialization should be a property of the Binding Fault
  and Binding Fault Reference components, rather than of the Binding
  Operation, which would solve your problem.

There may be other design choices as well.

Kendall Clark

[1] http://www.w3.org/sw/2001/DataAccess/proto-wd/

In times of universal deceit, telling the truth is a revolutionary act.  
					  --George Orwell
Received on Wednesday, 14 September 2005 15:44:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:02 UTC