Updated 'XML and JSON' section of Rest Quick Tips page.

restquicktips.html

@@ -47,12 +47,12 @@
 					<p>Resource names should be nouns—avoid verbs as resource names.  It makes things more clear.  Use the HTTP methods to specify the verb portion of the request.</p>
 					<h2>XML and JSON</h2>
 					<p>Favor JSON support, but unless the costs of offering both JSON and XML are staggering, offer them both. Ideally, let consumers switch between them by just changing an extension from .xml to .json.  In addition, for supporting AJAX-style user interfaces, a wrapped response is very helpful.  Provide a wrapped response, either by default or for separate extensions, such as .wjson and .wxml to indicate the client is requesting a wrapped JSON or XML response.</p>
-					<p>JSON in regards to a "standard" has very few requirements.  And those requirements are only syntactical in nature, not about content format or layout.  In other words, the JSON response to a REST service call is very much part of the contract—not described in a standard.  More about the JSON data format can be found at http://www.json.org/.</p>
-					<p>Regarding XML use in REST services, XML standards and conventions are really not in play other than to utilize syntactically correct tags and text.  In particular, namespaces are not, nor should they be use in a RESTful service context.  XML that is returned is more JSON like—simple and easy to read, without the schema and namespace details present—just data and links.</p>
+					<p>JSON in regards to a "standard" has very few requirements.  And those requirements are only syntactical in nature, not about content format or layout.  In other words, the JSON response to a REST service call is very much part of the contract—not described in a standard.  More about the JSON data format can be found at <a href="http://www.json.org/">http://www.json.org/</a>.</p>
+					<p>Regarding XML use in REST services, XML standards and conventions are really not in play other than to utilize syntactically correct tags and text.  In particular, namespaces are not, nor should they be use in a RESTful service context.  XML that is returned is more JSON like—simple and easy to read, without the schema and namespace details present—just data and links.  If it ends up being more complex than this, see the first paragraph for this tip&mdash;the cost of XML will be staggering.  In our experience nobody uses the XML responses anyway.  It's just too expensive to process.</p>
 					<h2>Create Fine-Grained Resources</h2>
 					<p>When starting out, it's much easier to create APIs that mimic the underlying application domain or database architecture of your system.  Eventually, you'll want aggregate services—services that utilize multiple underlying resources to reduce chattiness.  But it's much easier to create larger resources later from individual resources than it is to create fine-grained or individual resources from larger aggregates.  Make it easy on yourself and start with small, easily defined resources, providing CRUD functionality on those.  You can create those use-case-oriented, chattiness-reducing resources later.</p>
 					<h2>Consider Connectedness</h2>
-					<p>One of the principles of REST is connectedness—via hypermedia links.  While services are still useful without them, APIs become more self-descriptive when links are returned in the response.  At the very least, a 'self' reference informs clients how the data was or can be retrieved.  Additionally, utilize the Location header to contain a link on resource creation via POST.</p>
+					<p>One of the principles of REST is connectedness—via hypermedia links.  While services are still useful without them, APIs become more self-descriptive when links are returned in the response.  At the very least, a 'self' reference informs clients how the data was or can be retrieved.  Additionally, utilize the Location header to contain a link on resource creation via POST.  For collections returned in a response that support pagination, 'first', 'last', 'next' and 'prev' links at a minimum are very helpful.</p>
 				</div>
 			</div>
 			<hr>