1 <?xml version="1.0" encoding="iso-8859-1"?> 2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 4 <html xmlns="http://www.w3.org/1999/xhtml"> 5 <head> 6 <title>Using the Path as an Opaque Reference into an Application</title> 7 <meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" /> 8 <link href="styles.css" rel="stylesheet" type="text/css" /> 9 </head> 10 11 <body> 12 <h1>Using the Path as an Opaque Reference into an Application</h1> 13 14 <p>Since many Web applications have complete control over how paths are 15 interpreted, the form of the path doesn't necessarily have to follow any 16 obvious structure as far as users of your application is concerned. Here's an 17 example:</p> 18 <pre>/000251923572ax-0015</pre> 19 20 <p>However, many would argue that such obscure references, whilst perfectly 21 acceptable to machines, would make any application counter-intuitive and very 22 difficult to reference. Sometimes, application developers do not want people 23 "bookmarking" resources or functions within an application, and so such 24 concerns don't matter to them.</p> 25 </body> 26 </html>