--- a/paq/css/prov-aq.css Mon Nov 19 12:58:42 2012 +0000
+++ b/paq/css/prov-aq.css Mon Nov 19 13:06:44 2012 +0000
@@ -4,6 +4,12 @@
color: #224433;
}
+p code {
+ /* Above override doesn't work */
+ font-family: monospace;
+ color: #224433;
+}
+
/* --- PATTERNS --- */
pre.pattern {
--- a/paq/prov-aq.html Mon Nov 19 12:58:42 2012 +0000
+++ b/paq/prov-aq.html Mon Nov 19 13:06:44 2012 +0000
@@ -415,38 +415,33 @@
An example transaction using content negotiation and redirection might look like this (where <code>C:</code> and <code>S:</code> prefixes indicate client and server emitted data respectively):
</p>
<pre class="pattern">
- C: GET /resource/
- C: Host: http://example.com/
- C: Accept: text/html
-
- S: 302 Found
- S: Location: /resource/content.html
- S: Vary: Accept
- S:
- S: HTML content for http://example.com/resource/
- S: is available at http://example.com/resource/content.html
-
- C: GET /resource/content.rdf
- C: Host: http://example.com/
- C: Accept: text/html
-
- S: 200 OK
- S: Content-type: text/html
- S: Vary: Accept
- S: Link: <http://example.com/resource/provenance/>;
- rel="http://www.w3.org/ns/prov#hasProvenance";
- anchor="http://example.com/resource/"
- S:
- S: <html ...>
- S: :
- S: </html>
- </pre>
+ C: GET /resource/
+ C: Host: http://example.com/
+ C: Accept: text/html
+
+ S: 302 Found
+ S: Location: /resource/content.html
+ S: Vary: Accept
+ S:
+ S: HTML content for http://example.com/resource/
+ S: is available at http://example.com/resource/content.html
+
+ C: GET /resource/content.rdf
+ C: Host: http://example.com/
+ C: Accept: text/html
+
+ S: 200 OK
+ S: Content-type: text/html
+ S: Vary: Accept
+ S: Link: <http://example.com/resource/provenance/>;
+ rel="http://www.w3.org/ns/prov#hasProvenance";
+ anchor="http://example.com/resource/"
+ S:
+ S: <html ...>
+ S: :
+ S: </html></pre>
</section>
-
-
-
-
</section>
<section>