[Sommaire] [Imprimer]

   1  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3  <html>
   4   <head>
   5   <title>Test Content Document</title>
   6  
   7   <link href="kupucontentstyles.css" rel="stylesheet" type="text/css" />
   8  
   9   <!-- headers to prevent the browser from caching, these *must* be provided,
  10          either in meta-tag form or as HTTP headers -->
  11   <meta http-equiv="Pragma" content="no-cache" />
  12   <meta http-equiv="Cache-Control" content="no-cache, must-revalidate" />
  13  
  14   <!-- make sure the browser's charset is UTF-8 -->
  15   <meta http-equiv="Content-Type" content="text/html;charset=UTF-8" />
  16  
  17   <!-- some meta data, customizations could build property tools that
  18          edit more of them -->
  19   <meta name="Subject" content="" />
  20   <meta name="Publisher" content="No publisher" />
  21   <meta name="Description" content="Document-centric editing overview." />
  22   <meta name="Contributors" content="" />
  23   <meta name="Effective_date" content="None" />
  24   <meta name="Expiration_date" content="None" />
  25   <meta name="Type" content="Document" />
  26   <meta name="Format" content="text/html" />
  27   <meta name="Language" content="" />
  28   <meta name="Rights" content="" />
  29   </head>
  30  <body>
  31  
  32  <h1>Document-Centric Editing</h1>
  33  
  34  <p>There are two approaches to content editing in a web browser.  The
  35  first is a <em>data-oriented</em> approach, where the content is split into
  36  concrete parts.  The editing occurs in a <code>&lt;form&gt;</code> with various 
  37  fields. This approach fits best when there are specific pieces of information 
  38  needed for the resource.</p>
  39  <p>The second is a <em>document-oriented</em> approach, where the essence of 
  40  the resource is free-flowing. This does not mean that the content is 
  41  unstructured, but it is less rigid than fields. Often there are elements that
  42  provide metadata for the resource.</p>
  43  
  44  <p>Most information in organizations is free-flowing, as studies show.
  45  For these cases, a rich editor like Kupu makes sense.  Equally, these
  46  cases point towards a <em>document-centric</em> approach, rather than
  47  rigid <a title="HTML Specification" href="http://www.w3.org/Markup">HTML</a> 
  48  forms.</p>
  49  
  50  <p>The following table shows different aspects, and happens to give 
  51  us a chance to test table editing in Kupu:</p>
  52  
  53  <h4>Comparing Data- and Document-Centric</h4>
  54  <table border="0" class="plain" cellspacing="0">
  55  <tbody>
  56      <tr>
  57          <th>&nbsp;</th>
  58          <th>Data-centric</th>
  59          <th>Document-centric</th>
  60      </tr>
  61      <tr>
  62          <td>Implementation</td>
  63          <td>form fields</td>
  64          <td>iframe</td>
  65      </tr>
  66      <tr>
  67          <td>Metadata</td>
  68          <td>form elements</td>
  69          <td>iframe document "head"</td>
  70      </tr>
  71  </tbody>
  72  </table>
  73  
  74  
  75  </body>
  76  </html>