Comments on: Error Messages in a RESTful API http://www.jrandolph.com/blog/2005/11/11/error-messages-in-a-restful-api/ software development and testing Thu, 24 Apr 2008 12:51:01 -0400 http://wordpress.org/?v=2.9.2 hourly 1 By: Josh http://www.jrandolph.com/blog/2005/11/11/error-messages-in-a-restful-api/comment-page-1/#comment-186 Josh Mon, 14 Nov 2005 00:19:30 +0000 http://www.jrandolph.com/blog/?p=13#comment-186 Or just don't use a RESTful API. Nobody wants to bind to it anyway :) Or just don’t use a RESTful API. Nobody wants to bind to it anyway :)

]]> By: Nat http://www.jrandolph.com/blog/2005/11/11/error-messages-in-a-restful-api/comment-page-1/#comment-185 Nat Fri, 11 Nov 2005 22:35:48 +0000 http://www.jrandolph.com/blog/?p=13#comment-185 This would require the error attribute to be included in the schema or DTD of every validatable XML file sent back. Also, the message cannot contain rich information such as links. It might be better to define an error namespace and allow some subset of XHTML or similar markup to be used in the error message, like: <expense-item xmlns:error="http://www.jrandolph.com/xmlns/error/1,0"> <project><error:report>Project not a <a href="valid_codes.html">valid code</a></error> ... This would require the error attribute to be included in the schema or DTD of every validatable XML file sent back. Also, the message cannot contain rich information such as links. It might be better to define an error namespace and allow some subset of XHTML or similar markup to be used in the error message, like:

<expense-item xmlns:error=”http://www.jrandolph.com/xmlns/error/1,0″>
<project><error:report>Project not a <a href=”valid_codes.html”>valid code</a></error>
…

]]>