1 <?xml version="1.0" encoding="iso-8859-1"?> 2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3 <html xmlns="http://www.w3.org/1999/xhtml"> 4 <head> 5 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type" /> 6 <title>Path Design and Interpretation</title> 7 <link href="styles.css" rel="stylesheet" type="text/css" /> 8 </head> 9 <body> 10 <h1>Path Design and Interpretation</h1> 11 <p>There are various differing approaches to the problem of 12 interpreting 13 paths to resources within Web applications, but these can mostly be 14 divided 15 into three categories:</p> 16 <table align="center" border="1" cellpadding="5" cellspacing="0" 17 width="80%"> 18 <tbody> 19 <tr> 20 <th>Approach</th> 21 <th>Examples</th> 22 </tr> 23 <tr> 24 <td><a href="paths-filesystem.html">Path as filesystem</a></td> 25 <td>WebDAV interface to a repository</td> 26 </tr> 27 <tr> 28 <td><a href="paths-services.html">Path as resource or service 29 identifier</a></td> 30 <td>A Web shop with very simple paths, eg. <code>/products</code>, 31 <code>/checkout</code>, <code>/orders</code></td> 32 </tr> 33 <tr> 34 <td><a href="paths-opaque.html">Path as opaque reference</a></td> 35 <td>An e-mail reader where the messages already have strange and 36 unreadable message identifiers</td> 37 </tr> 38 </tbody> 39 </table> 40 </body> 41 </html>