1.1 --- a/docs/paths-filesystem.html Thu Oct 20 15:43:51 2005 +0000
1.2 +++ b/docs/paths-filesystem.html Thu Oct 20 16:00:01 2005 +0000
1.3 @@ -1,11 +1,9 @@
1.4 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.5 -<html xmlns="http://www.w3.org/1999/xhtml">
1.6 -<head>
1.7 - <title>Treating the Path Like a Filesystem</title>
1.8 - <meta name="generator"
1.9 - content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.10 - <link href="styles.css" rel="stylesheet" type="text/css" />
1.11 -</head>
1.12 +<html xmlns="http://www.w3.org/1999/xhtml"><head>
1.13 +
1.14 + <title>Treating the Path Like a Filesystem</title><meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.15 + <link href="styles.css" rel="stylesheet" type="text/css" /></head>
1.16 +
1.17 <body>
1.18 <h1>Treating the Path Like a
1.19 Filesystem</h1>
1.20 @@ -111,7 +109,5 @@
1.21 objects is not the only way to support such
1.22 hierarchies. We could inspect paths and act dynamically on the supplied
1.23 information, either choosing to create resources or choosing to handle
1.24 -such paths in the same resource. See <a href="path-info.html">"Paths
1.25 -To and Within Applications"</a> for some other strategies.</p>
1.26 -</body>
1.27 -</html>
1.28 +such paths in the same resource.</p>
1.29 +</body></html>
1.30 \ No newline at end of file