1.1 --- a/docs/paths-opaque.html Sat Sep 08 16:01:41 2007 +0000
1.2 +++ b/docs/paths-opaque.html Sat Sep 08 16:02:18 2007 +0000
1.3 @@ -1,27 +1,20 @@
1.4 +<?xml version="1.0" encoding="iso-8859-1"?>
1.5 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.6 <html xmlns="http://www.w3.org/1999/xhtml">
1.7 <head>
1.8 <title>Using the Path as an Opaque Reference into an Application</title>
1.9 - <meta name="generator"
1.10 - content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.11 <link href="styles.css" rel="stylesheet" type="text/css" />
1.12 </head>
1.13 <body>
1.14 <h1>Using the Path as an Opaque Reference into an Application</h1>
1.15 <p>Since many Web applications have complete control over how paths are
1.16 -interpreted, the form of the path doesn't necessarily have to follow
1.17 -any
1.18 -obvious structure as far as users of your application is concerned.
1.19 -Here's an
1.20 +interpreted, the form of the path doesn't necessarily have to follow any
1.21 +obvious structure as far as users of your application is concerned. Here's an
1.22 example:</p>
1.23 <pre>/000251923572ax-0015</pre>
1.24 -<p>Many people would argue that such obscure references, whilst
1.25 -perfectly
1.26 -acceptable to machines, would make any application counter-intuitive
1.27 -and very
1.28 -difficult to reference. However, application developers sometimes
1.29 -do not want people
1.30 -"bookmarking" resources or functions within an application, and so such
1.31 -concerns don't matter to them.</p>
1.32 +<p>Many people would argue that such obscure references, whilst perfectly
1.33 +acceptable to machines, would make any application counter-intuitive and very
1.34 +difficult to reference. However, application developers sometimes do not want people
1.35 +"bookmarking" resources or functions within an application, and so such concerns don't matter to them.</p>
1.36 </body>
1.37 </html>