[Phoenix-commits] rev 13000 - in public/phoenix/deliverables:
analysis planning
andi at wyona.com
andi at wyona.com
Tue May 2 23:27:16 CEST 2006
Author: andi
Date: 2006-05-02 23:27:13 +0200 (Tue, 02 May 2006)
New Revision: 13000
Modified:
public/phoenix/deliverables/analysis/specification.xhtml
public/phoenix/deliverables/analysis/specification.xml
public/phoenix/deliverables/planning/roadmap.xhtml
public/phoenix/deliverables/planning/roadmap.xml
Log:
Refined the specification by adding use cases, and breaking them down into features.
Modified: public/phoenix/deliverables/analysis/specification.xhtml
===================================================================
--- public/phoenix/deliverables/analysis/specification.xhtml 2006-05-02 16:15:56 UTC (rev 12999)
+++ public/phoenix/deliverables/analysis/specification.xhtml 2006-05-02 21:27:13 UTC (rev 13000)
@@ -38,7 +38,7 @@
</div>
</div>
<div>
- <p class="pubdate">2006-04-28</p>
+ <p class="pubdate">2006-05-02</p>
</div>
<div>
<div class="revhistory">
@@ -49,6 +49,14 @@
</th>
</tr>
<tr>
+ <td align="left">Revision 1.1</td>
+ <td align="left">2006-05-02</td>
+ <td align="left">AW</td>
+ </tr>
+ <tr>
+ <td align="left" colspan="3">Project decomposition and features.</td>
+ </tr>
+ <tr>
<td align="left">Revision 1.0</td>
<td align="left">2006-04-28</td>
<td align="left">AW</td>
@@ -77,46 +85,97 @@
<dl>
<dt>
<span class="section">
- <a href="#id342776">1. Usecases</a>
+ <a href="#id342793">1. Usecases</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="section">
- <a href="#id342782">1.1. Using Phoenix as a Browser</a>
+ <a href="#id342798">1.1. Using Phoenix as a Browser</a>
</span>
</dt>
<dt>
<span class="section">
- <a href="#id342797">1.2. Using Phoenix as an Editing Tool</a>
+ <a href="#id342814">1.2. Using Phoenix as an Editing Tool</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="section">
- <a href="#id342867">2. More than XML ...</a>
+ <a href="#id342953">2. More than XML ...</a>
</span>
</dt>
<dt>
<span class="section">
- <a href="#id342966">3. Reasoning</a>
+ <a href="#id343118">3. General Features</a>
</span>
</dt>
<dt>
<span class="section">
- <a href="#id343004">4. General Features</a>
+ <a href="#id343191">4. Project Decomposition</a>
</span>
</dt>
+ <dd>
+ <dl>
+ <dt>
+ <span class="section">
+ <a href="#id343199">4.1. Components and Variants</a>
+ </span>
+ </dt>
+ <dd>
+ <dl>
+ <dt>
+ <span class="section">
+ <a href="#id343213">4.1.1. Front End Component (FRONTEND)</a>
+ </span>
+ </dt>
+ <dd>
+ <dl>
+ <dt>
+ <span class="section">
+ <a href="#id344016">4.1.1.1. Browser Integrated Variant (BROWSER)</a>
+ </span>
+ </dt>
+ <dt>
+ <span class="section">
+ <a href="#id344031">4.1.1.2. Standalone Variant (STANDALONE)</a>
+ </span>
+ </dt>
+ </dl>
+ </dd>
+ <dt>
+ <span class="section">
+ <a href="#id344045">4.1.2. Back End Component (BACKEND)</a>
+ </span>
+ </dt>
+ <dd>
+ <dl>
+ <dt>
+ <span class="section">
+ <a href="#id344133">4.1.2.1. Client Based Variant (CLIENT)</a>
+ </span>
+ </dt>
+ <dt>
+ <span class="section">
+ <a href="#id344220">4.1.2.2. Server Based (SERVER)</a>
+ </span>
+ </dt>
+ </dl>
+ </dd>
+ </dl>
+ </dd>
+ </dl>
+ </dd>
<dt>
<span class="section">
- <a href="#id343083">5. Special Features</a>
+ <a href="#id344316">5. Open Issues/To be discussed</a>
</span>
</dt>
<dt>
<span class="section">
- <a href="#id343130">6. Open Issues/To be discussed</a>
+ <a href="#id344369">6. Reasoning</a>
</span>
</dt>
</dl>
@@ -125,7 +184,7 @@
<div class="titlepage">
<div>
<div>
- <h2 class="title"><a id="id342776"/>1. Usecases</h2>
+ <h2 class="title"><a id="id342793"/>1. Usecases</h2>
</div>
</div>
</div>
@@ -133,7 +192,7 @@
<div class="titlepage">
<div>
<div>
- <h3 class="title"><a id="id342782"/>1.1. Using Phoenix as a Browser</h3>
+ <h3 class="title"><a id="id342798"/>1.1. Using Phoenix as a Browser</h3>
</div>
</div>
</div>
@@ -145,7 +204,7 @@
<div class="titlepage">
<div>
<div>
- <h3 class="title"><a id="id342797"/>1.2. Using Phoenix as an Editing Tool</h3>
+ <h3 class="title"><a id="id342814"/>1.2. Using Phoenix as an Editing Tool</h3>
</div>
</div>
</div>
@@ -155,25 +214,50 @@
<div class="itemizedlist">
<ul>
<li>
- <p><b>Usecase 1. </b>
+ <p><b>Usecase UC1. </b>
Open File from your desktop and Save to your desktop.
</p>
</li>
<li>
- <p><b>Usecase 2. </b>
+ <p><b>Usecase UC2. </b>
Browse to webpage, Open webpage from Server (e.g. WebDAV and checkout/lock on server, depending on server functionality), Disconnect from internet, Keep editing, Save local version (meta: server URL, schema/RelaxNG, style, ...), Re-connect to internet and Save to server (checkin/unlock ...).
</p>
</li>
<li>
- <p><b>Usecase 3. </b>
+ <p><b>Usecase UC3. </b>
Open local file, Save/New to server.
</p>
</li>
<li>
- <p><b>Usecase 4. </b>
- New webpage (from template on server) on server
+ <p><b>Usecase UC4. </b>
+ New webpage (from template on server) on server.
</p>
</li>
+ <li>
+ <p><b>Usecase UC5. </b>
+ Edit whilst being on-line.
+ </p>
+ </li>
+ <li>
+ <p><b>Usecase UC6. </b>
+ Edit whilst being off-line.
+ </p>
+ </li>
+ <li>
+ <p><b>Usecase UC7. </b>
+ Edit in Source Mode. Add/delete text, add/delete elements, add/remove Schema-specific styling (like <code class="code"><b></code> or <code class="code"><tt></code> in XHTML), add/remove CSS styling.
+ </p>
+ </li>
+ <li>
+ <p><b>Usecase UC8. </b>
+ Edit in WYSIWYG Mode. Add/delete text, add/delete elements, add/remove Schema-specific styling (like <code class="code"><b></code> or <code class="code"><tt></code> in XHTML), add/remove CSS styling.
+ </p>
+ </li>
+ <li>
+ <p><b>Usecase UC9. </b>
+ Validate document.
+ </p>
+ </li>
</ul>
</div>
<p>
@@ -185,7 +269,7 @@
<div class="titlepage">
<div>
<div>
- <h2 class="title"><a id="id342867"/>2. More than XML ...</h2>
+ <h2 class="title"><a id="id342953"/>2. More than XML ...</h2>
</div>
</div>
</div>
@@ -195,11 +279,11 @@
<div class="itemizedlist">
<ul>
<li>
- <p><b>Usecase 1. </b>
- Start with XML and additonal <span class="emphasis"><em>common</em></span> formatting.
- </p>
+ <p><b>Usecase UC10. </b>
+ Start with XML and additonal <span class="emphasis"><em>common</em></span> formatting.
+ </p>
<div class="example">
- <a id="id342890"/>
+ <a id="id342976"/>
<p class="title">
<b>Example 1. Add <span class="emphasis"><em>common</em></span> formatting</b>
</p>
@@ -219,62 +303,54 @@
<i>cy at wyona.org</i>
</p>
- </pre>
+ </pre>
</div>
</li>
<li>
- <p><b>Usecase 2. </b>
- Start with plain text resp. semi-structured and add tags according to selected schema, but retain style or allow to select style according to schema in case such a style exists (Similarto CSS ...!).
- </p>
+ <p><b>Usecase UC11. </b>
+ Start with plain text resp. semi-structured and add tags according to selected schema, but retain style or allow to select style according to schema in case such a style exists (Similar to CSS ...!).
+ </p>
</li>
<li>
- <p><b>Usecase 3. </b>
- Apply multiple schemas allowing <span class="emphasis"><em>entanglement</em></span> for internal representation.
- </p>
+ <p><b>Usecase UC12. </b>
+ Add/remove "common" styling derived from Schema (e.g. <code class="code"><i></code> in XHTML and <code class="code"><emphasis></code> in DocBook). Requires a mapping from these "common" styles to the specific Schema in use.
+ </p>
</li>
<li>
- <p><b>Usecase 4. </b>
- Automatic recognition of tags through training, derived from style ... more sophisticated by stepping through the document ...
- </p>
+ <p><b>Usecase UC13. </b>
+ Apply multiple schemas allowing <span class="emphasis"><em>entanglement</em></span> for internal representation.
+ </p>
</li>
<li>
- <p><b>Usecase 5. </b>
- Copy/Paste ...
- </p>
+ <p><b>Usecase UC14. </b>
+ Automatic insertion of tags through training, derived from style. Insertion controllable by stepping through the document.
+ </p>
</li>
- </ul>
- </div>
- <p>
- </p>
- </div>
- <div class="section" lang="en">
- <div class="titlepage">
- <div>
- <div>
- <h2 class="title"><a id="id342966"/>3. Reasoning</h2>
- </div>
- </div>
- </div>
- <p>
- Why do we want to use the Mozilla platform for Phoenix:
- </p>
- <div class="itemizedlist">
- <ul>
<li>
- <p>
- No gap between browser and editing tool (e.g. OpenOffice, ...)!
+ <p><b>Usecase UC15. </b>
+ Insertion (e.g. by Copy and Paste or Drag and Drop) of links to other assets.
</p>
</li>
<li>
- <p>
- Platform independence (Windows, Linux, MacOS, UNIX, ...)!
+ <p><b>Usecase UC16. </b>
+ Insertion (e.g. by Copy and Paste or Drag and Drop) of blobs (e.g. images, ...). (NOTE: mapping between input and schema!)
</p>
</li>
<li>
- <p>
- Offline/Online editing ...
+ <p><b>Usecase UC17. </b>
+ Insertion (e.g. by Copy and Paste or Drag and Drop) of Schema-foreign elements.
</p>
</li>
+ <li>
+ <p><b>Usecase UC18. </b>
+ Insertion (e.g. by Copy and Paste or Drag and Drop) of (semi-)structured text (e.g. from Word, OpenOffice, ...) or pre-formatted clobs (e.g. program listings). (NOTE: mapping between input and schema!)
+ </p>
+ </li>
+ <li>
+ <p><b>Usecase UC19. </b>
+ Word/OpenOffice functionality/usability (return means new paragraph!)
+ </p>
+ </li>
</ul>
</div>
<p>
@@ -284,7 +360,7 @@
<div class="titlepage">
<div>
<div>
- <h2 class="title"><a id="id343004"/>4. General Features</h2>
+ <h2 class="title"><a id="id343118"/>3. General Features</h2>
</div>
</div>
</div>
@@ -329,11 +405,6 @@
</li>
<li>
<p>
- Word/OpenOffice functionality/usability (return means new paragraph!)
- </p>
- </li>
- <li>
- <p>
Word/OpenOffice interoperability: ODT, WordXML, ... (import/export)
</p>
</li>
@@ -346,34 +417,640 @@
<div class="titlepage">
<div>
<div>
- <h2 class="title"><a id="id343083"/>5. Special Features</h2>
+ <h2 class="title"><a id="id343191"/>4. Project Decomposition</h2>
</div>
</div>
</div>
<p>
+ This decomposition serves the purpose of partitioning the project into implementable features. Note that a single usecase may need support from the front end as well as the back end, therefore a usecase may consist of several features in different components. It follows that in order to implement a usecase, features in the front as well as the back end must be implemented; the implementation though only has to be done in one variant of a component to have the usecase working for this variant. Therefore, the variants of a component are independent.
+ </p>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h3 class="title"><a id="id343199"/>4.1. Components and Variants</h3>
+ </div>
+ </div>
+ </div>
+ <p>
+ The project consists of two components: the front end, and the back end. The front end component is divided into two variants: the editor integrated in a web browser, and a standalone editor. The back end component is divided into two variants as well: a client based variant and a server based variant.
</p>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h4 class="title"><a id="id343213"/>4.1.1. Front End Component (FRONTEND)</h4>
+ </div>
+ </div>
+ </div>
+ <p>
+ The front end component is responsible for the handling the view. FRONTEND performs tasks like rendering the document, supplying user interaction facilities, etc.
+ </p>
+ <h5><a id="id343225"/>Common Feature Set</h5>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F1 (UC1, UC2, UC3, UC6). </b>
+ Open document from file system (<code class="code">file://</code>).
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F1.1 (UC1, UC3, UC6). </b>
+ Open well-formed XML document from file system.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F1.2 (UC2, UC6, UC10). </b>
+ Open potentially associated meta-data from file system. Meta-data may be CMS information, XSLT, CSS and Schemas.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F1.3 (UC11). </b>
+ Open ill-formed XML document from file system.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F1.4 (UC13). </b>
+ Open entangled XML document from file system.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F2 (UC1, UC2, UC6). </b>
+ Save document to file system (<code class="code">file://</code>).
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F2.1 (UC1, UC6). </b>
+ Save XML document to file system.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F2.2 (UC2, UC6, UC10). </b>
+ Save potentially associated meta-data to file system. Meta-data may be CMS information, XSLT, CSS and Schemas.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F2.3 (UC11). </b>
+ Save ill-formed XML document to file system.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F2.4 (UC13). </b>
+ Save entangled XML document to file system.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F3 (UC2, UC10, UC11, UC13). </b>
+ Open document from CMS.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F3.1 (UC2). </b>
+ Using HTTP protocol.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F3.2 (UC2). </b>
+ Using WebDAV protocol.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F3.3 (UC2). </b>
+ Using OSR-101 protocol.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F4 (UC2, UC3, UC10, UC11, UC13). </b>
+ Save document to CMS.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F4.1 (UC2, UC3). </b>
+ Using HTTP protocol.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F4.2 (UC2, UC3). </b>
+ Using WebDAV protocol.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F4.3 (UC2, UC3). </b>
+ Using OSR-101 protocol.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F5 (UC4). </b>
+ Fetch document template from CMS.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F5.1 (UC4). </b>
+ Using HTTP protocol.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F5.2 (UC4). </b>
+ Using WebDAV protocol.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F5.3 (UC4). </b>
+ Using OSR-101 protocol.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F6 (UC7). </b>
+ Edit in Source Mode.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F6.1 (UC7). </b>
+ Add/edit/delete text nodes.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F6.2 (UC7). </b>
+ Add/edit/delete elements.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F6.3 (UC7). </b>
+ Add/edit/delete element attributes.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F7 (UC8, UC12, UC15, UC16, UC17, UC18, UC19). </b>
+ Edit in WYSIWYG Mode.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.1 (UC8). </b>
+ Add/edit/delete text nodes.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.2 (UC8). </b>
+ Add/edit/delete elements.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.3 (UC8). </b>
+ Add/remove Schema-specific styling.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.3.1 (UC8). </b>
+ Provide toolbar to select from Schema-specific styles.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.3.2 (UC8). </b>
+ Provide list of Schema-specific elements which represent styling (e.g. <code class="code"><i></code>, <code class="code"><tt></code> or <code class="code"><b></code> elements in XHTML) for each Schema in use. A "styling-element" is an XML element which is usually employed to solely convey styling information.
+ </p>
+ <p>
+ Following is a list of Schema-specific styling-elements considered useful to be added to the FRONTEND. Extend this list if you find more useful Schemas.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.3.2.1 (UC8). </b>
+ XHTML styling-elements list.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.3.2.2 (UC8). </b>
+ DocBook styling-elements list.
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F7.4 (UC8). </b>
+ Add/remove CSS styling.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.4.1 (UC8). </b>
+ Provide toolbar to select from predefined CSS styles.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.4.2 (UC8). </b>
+ Provide list of predefined CSS styles. These lists may be independent or associated with a given Schema.
+ </p>
+ <p>
+ Following is a list of CSS styles considered useful to be added to the FRONTEND. Extend this list if you find more useful styles.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.4.2.1 (UC8). </b>
+ Independent common CSS styles.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.4.2.2 (UC8). </b>
+ Common CSS styles normally used in conjunction with XHTML.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.4.2.3 (UC8). </b>
+ Common CSS styles normally used in conjunction with DocBook.
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F7.5 (UC12). </b>
+ Add/remove "common" styling derived from Schema in use.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.5.1 (UC12). </b>
+ Provide toolbar to select from Schema-derived "common" styles.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.5.2 (UC12). </b>
+ Provide a mapping between a set of "common" styles and the corresponding elements of the Schema in use.
+ </p>
+ <p>
+ Following is a list of mappings from a "common" style set to specific elements of Schemas which are considered useful to be added to the FRONTEND. Extend this list if you want more mappings available.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.5.2.1 (UC12). </b>
+ Mapping between the "common" style and XHTML elements.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.5.2.2 (UC12). </b>
+ Mapping between the "common" style and DocBook elements.
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F7.6 (UC15). </b>
+ Insertion of links to other assets.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.7 (UC16). </b>
+ Insertion of blobs. Requires a mapping between "common" blobs and the the Schema-specific elements which represent such blobs (e.g. <code class="code"><img></code> in XHTMl and <code class="code"><imageobject></code> in DocBook).
+ </p>
+ <p>
+ Following is a list of mappings from "common" blobs to Schema-specific elements which are considered useful to be added to the FRONTEND. Extend this list if you want more mappings available.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.7.1 (UC16). </b>
+ Mapping between "common" blobs and XHTML elements.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.7.2 (UC16). </b>
+ Mapping between the "common" blobs and DocBook elements.
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.8 (UC17). </b>
+ Insertion of Schema-foreign elements.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.9 (UC18). </b>
+ Insertion of (semi-)structured text or pre-formatted clobs. Requires a mapping between every input source and the Schema in use.
+ </p>
+ <p>
+ Following is a list of mappings from input sources to Schemas considered useful to be added to the FRONTEND. Extend this list if you want more mappings available.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature F7.9.1 (UC18). </b>
+ Mapping between WordXML clobs and XHTML elements.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.9.2 (UC18). </b>
+ Mapping between ODT clobs and XHTML elements.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.9.3 (UC18). </b>
+ Mapping between WordXML clobs and DocBook elements.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.9.4 (UC18). </b>
+ Mapping between ODT clobs and DocBook elements.
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F7.10 (UC19). </b>
+ Word-processor style usage.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ <li>
+ <p><b>Feature F8 (UC7, UC8). </b>
+ Content Assist, providing suggestions for element names, attributes names and attribute content.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F9 (UC9). </b>
+ Visualise results of Schema validation.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F10 (UC14). </b>
+ Toolbar to train automatic tag inserter.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature F11 (UC14). </b>
+ Toolbar to guide step-wise automatic tag inserter.
+ </p>
+ </li>
+ </ul>
+ </div>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h5 class="title"><a id="id344016"/>4.1.1.1. Browser Integrated Variant (BROWSER)</h5>
+ </div>
+ </div>
+ </div>
+ <p>
+ The browser integrated variant of FRONTEND is a XUL widget which integrates seamlessly into web browsers based on the Mozilla Platform. BROWSER must be able to work with up-to-date versions of Firefox and SeaMonkey (formerly Mozilla Suite).
+ </p>
+ </div>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h5 class="title"><a id="id344031"/>4.1.1.2. Standalone Variant (STANDALONE)</h5>
+ </div>
+ </div>
+ </div>
+ <p>
+ The standalone variant of the FRONTEND can be used as a standalone editor, independent of a web browser. Like the browser integrated version, STANDALONE is based on XUL.
+ </p>
+ </div>
+ </div>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h4 class="title"><a id="id344045"/>4.1.2. Back End Component (BACKEND)</h4>
+ </div>
+ </div>
+ </div>
+ <p>
+ The back end component comprises the controller and the model. BACKEND performs tasks like ID Tagging, XSLT processing, validation, etc.
+ </p>
+ <h5><a id="id344056"/>Common Feature Set</h5>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature B1 (UC8). </b>
+ Retrieve XSLT from CMS.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature B2 (UC8, UC10, UC11). </b>
+ Retrieve CSS from CMS.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature B3 (UC9). </b>
+ Retrieve Schema from Schema server. Note that the Schema server may be the CMS or some other unrelated host on the network.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature B3.1 (UC9). </b>
+ Retrieve RelaxNG Schema from Schema server.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature B3.2 (UC9). </b>
+ Retrieve W3C XML Schema from Schema server.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature B3.3 (UC9). </b>
+ Retrieve DTD from Schema server.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ </ul>
+ </div>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h5 class="title"><a id="id344133"/>4.1.2.1. Client Based Variant (CLIENT)</h5>
+ </div>
+ </div>
+ </div>
+ <p>
+ The client based variant of BACKEND places the back end logic on the client side.
+ </p>
+ <h6><a id="id344143"/>Feature Set</h6>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature BC1 (UC8). </b>
+ Retrieve XSLT from local file system.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature BC2 (UC8, UC10, UC11). </b>
+ Retrieve CSS from local file system.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature BC3 (UC9). </b>
+ Retrieve Schema from local file system.
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature BC3.1 (UC9). </b>
+ Retrieve RelaxNG Schema from local file system.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature BC3.2 (UC9). </b>
+ Retrieve W3C XML Schema from local file system.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature BC3.3 (UC9). </b>
+ Retrieve DTD from local file system.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ </ul>
+ </div>
+ </div>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h5 class="title"><a id="id344220"/>4.1.2.2. Server Based (SERVER)</h5>
+ </div>
+ </div>
+ </div>
+ <p>
+ The server based variant of BACKEND places the back end logic on the server side. SERVER additionally provides logic for FRONTEND to be able to communicate with the server side code.
+ </p>
+ <p>
+ Note that offline editing may not be fully functional with variant SERVER.
+ </p>
+ <h6><a id="id344237"/>Feature Set</h6>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature BS1 (UC8). </b>
+ Upload XSLT from local file system to SERVER. Since the XSLT processor resides on SERVER, we first have to upload the XSLT we want to use for rendering if we started off with a document on the local file system. Otherwise, SERVER can retrieve the XSLT directly from the CMS (feature B1).
+ </p>
+ </li>
+ <li>
+ <p><b>Feature BS2 (UC9). </b>
+ Upload Schema from local file system to SERVER. Since the validation logic resides on SERVER, we first have to upload the Schema we want to use for validation if we started off with a document on the local file system. Otherwise, SERVER can retrieve the Schema directly from the Schema server (feature B3).
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p><b>Feature BS2.1 (UC9). </b>
+ Upload RelaxNG Schema from local file system to SERVER.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature BS2.2 (UC9). </b>
+ Upload W3C XML Schema from local file system to SERVER.
+ </p>
+ </li>
+ <li>
+ <p><b>Feature BS2.3 (UC9). </b>
+ Upload DTD from local file system to SERVER.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </li>
+ </ul>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h2 class="title"><a id="id344316"/>5. Open Issues/To be discussed</h2>
+ </div>
+ </div>
+ </div>
+ <p>
+ </p>
<div class="itemizedlist">
<ul>
<li>
<p>
- Content Assist
+ Should we keep the source editing mode simple and stupid (i.e. only have the trivial operations of add/edit/delete of text nodes, elements and attributes), or should we add features like link insertion, etc.?
</p>
</li>
<li>
<p>
- Drag and Drop of images/links/... (NOTE: Mapping between image and schema!)
+ Implementation language (Java (also interesting for SERVER), C++, etc.)
</p>
</li>
<li>
<p>
- Copy and Paste of (semi-)structured text (e.g. Word, ...) (NOTE: mapping between input and schema!)
+ Amount of reuse (Etna project, Mozilla Platform, etc.)
</p>
</li>
<li>
<p>
- Drag and Drop of <span class="emphasis"><em>elements</em></span> ...
+ License (GPL, GPL+Commercial, LGPL, MPL, etc.)
</p>
</li>
+ <li>
+ <p>
+ Date of going public
+ </p>
+ </li>
</ul>
</div>
<p>
@@ -383,39 +1060,30 @@
<div class="titlepage">
<div>
<div>
- <h2 class="title"><a id="id343130"/>6. Open Issues/To be discussed</h2>
+ <h2 class="title"><a id="id344369"/>6. Reasoning</h2>
</div>
</div>
</div>
<p>
+ Why do we want to use the Mozilla platform for Phoenix:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
- Used language (Java, also interesting for server version)
+ No gap between browser and editing tool (e.g. OpenOffice, ...)!
</p>
</li>
<li>
<p>
- Server based solution
+ Platform independence (Windows, Linux, MacOS, UNIX, ...)!
</p>
</li>
<li>
<p>
- Standanlone solution
+ Offline/Online editing ...
</p>
</li>
- <li>
- <p>
- License (GPL, GPL+Commercial, LGPL, etc.)
- </p>
- </li>
- <li>
- <p>
- Date of going public
- </p>
- </li>
</ul>
</div>
<p>
Modified: public/phoenix/deliverables/analysis/specification.xml
===================================================================
--- public/phoenix/deliverables/analysis/specification.xml 2006-05-02 16:15:56 UTC (rev 12999)
+++ public/phoenix/deliverables/analysis/specification.xml 2006-05-02 21:27:13 UTC (rev 13000)
@@ -32,10 +32,16 @@
</author>
</authorgroup>
<!-- All dates specified in ISO "YYYY-MM-DD" format -->
- <pubdate>2006-04-28</pubdate>
+ <pubdate>2006-05-02</pubdate>
<!-- Most recent revision goes at the top; list in descending order -->
<revhistory>
<revision>
+ <revnumber>1.1</revnumber>
+ <date>2006-05-02</date>
+ <authorinitials>AW</authorinitials>
+ <revremark>Project decomposition and features.</revremark>
+ </revision>
+ <revision>
<revnumber>1.0</revnumber>
<date>2006-04-28</date>
<authorinitials>AW</authorinitials>
@@ -62,113 +68,149 @@
<itemizedlist>
<listitem>
<formalpara>
- <title>Usecase 1</title>
+ <title>Usecase UC1</title>
Open File from your desktop and Save to your desktop.
</formalpara>
</listitem>
<listitem>
<formalpara>
- <title>Usecase 2</title>
+ <title>Usecase UC2</title>
Browse to webpage, Open webpage from Server (e.g. WebDAV and checkout/lock on server, depending on server functionality), Disconnect from internet, Keep editing, Save local version (meta: server URL, schema/RelaxNG, style, ...), Re-connect to internet and Save to server (checkin/unlock ...).
</formalpara>
</listitem>
<listitem>
<formalpara>
- <title>Usecase 3</title>
+ <title>Usecase UC3</title>
Open local file, Save/New to server.
</formalpara>
</listitem>
<listitem>
<formalpara>
- <title>Usecase 4</title>
- New webpage (from template on server) on server
+ <title>Usecase UC4</title>
+ New webpage (from template on server) on server.
</formalpara>
</listitem>
- </itemizedlist>
- Generally speaking one has the possibility to edit existing "documents", either from a remote server or from the local desktop, or to create a new document based on a template provided by the remote server or located on the local desktop.
- </para>
- </section>
- </section>
-
- <section>
- <title>More than XML ...</title>
- <para>
- Phoenix should allow plain/semi-structured text editing with a "common" formatting, which means no XML Schema attached.
- <itemizedlist>
<listitem>
<formalpara>
- <title>Usecase 1</title>
- Start with XML and additonal <emphasis>common</emphasis> formatting.
- <example>
- <title>Add <emphasis>common</emphasis> formatting</title>
- <programlisting>
-<![CDATA[
-<person>
- <firstname>Caleb</firstname>
- <lastname>Yeanan</lastname>
- <email>cy at wyona.org</email>
-</person>
-
-<p>
- Address:
- <br/>
- <b>Caleb Yeanan</b>
- <br/>
- <i>cy at wyona.org</i>
-</p>
-]]>
- </programlisting>
- </example>
+ <title>Usecase UC5</title>
+ Edit whilst being on-line.
</formalpara>
</listitem>
<listitem>
<formalpara>
- <title>Usecase 2</title>
- Start with plain text resp. semi-structured and add tags according to selected schema, but retain style or allow to select style according to schema in case such a style exists (Similarto CSS ...!).
+ <title>Usecase UC6</title>
+ Edit whilst being off-line.
</formalpara>
</listitem>
<listitem>
<formalpara>
- <title>Usecase 3</title>
- Apply multiple schemas allowing <emphasis>entanglement</emphasis> for internal representation.
+ <title>Usecase UC7</title>
+ Edit in Source Mode. Add/delete text, add/delete elements, add/remove Schema-specific styling (like <code><b></code> or <code><tt></code> in XHTML), add/remove CSS styling.
</formalpara>
</listitem>
<listitem>
<formalpara>
- <title>Usecase 4</title>
- Automatic recognition of tags through training, derived from style ... more sophisticated by stepping through the document ...
+ <title>Usecase UC8</title>
+ Edit in WYSIWYG Mode. Add/delete text, add/delete elements, add/remove Schema-specific styling (like <code><b></code> or <code><tt></code> in XHTML), add/remove CSS styling.
</formalpara>
</listitem>
<listitem>
<formalpara>
- <title>Usecase 5</title>
- Copy/Paste ...
+ <title>Usecase UC9</title>
+ Validate document.
</formalpara>
</listitem>
</itemizedlist>
- </para>
+ Generally speaking one has the possibility to edit existing "documents", either from a remote server or from the local desktop, or to create a new document based on a template provided by the remote server or located on the local desktop.
+ </para>
+ </section>
</section>
<section>
- <title>Reasoning</title>
+ <title>More than XML ...</title>
<para>
- Why do we want to use the Mozilla platform for Phoenix:
+ Phoenix should allow plain/semi-structured text editing with a "common" formatting, which means no XML Schema attached.
<itemizedlist>
<listitem>
- <para>
- No gap between browser and editing tool (e.g. OpenOffice, ...)!
- </para>
+ <formalpara>
+ <title>Usecase UC10</title>
+ Start with XML and additonal <emphasis>common</emphasis> formatting.
+ <example>
+ <title>Add <emphasis>common</emphasis> formatting</title>
+ <programlisting>
+<![CDATA[
+<person>
+ <firstname>Caleb</firstname>
+ <lastname>Yeanan</lastname>
+ <email>cy at wyona.org</email>
+</person>
+
+<p>
+ Address:
+ <br/>
+ <b>Caleb Yeanan</b>
+ <br/>
+ <i>cy at wyona.org</i>
+</p>
+]]>
+ </programlisting>
+ </example>
+ </formalpara>
</listitem>
<listitem>
- <para>
- Platform independence (Windows, Linux, MacOS, UNIX, ...)!
- </para>
+ <formalpara>
+ <title>Usecase UC11</title>
+ Start with plain text resp. semi-structured and add tags according to selected schema, but retain style or allow to select style according to schema in case such a style exists (Similar to CSS ...!).
+ </formalpara>
</listitem>
<listitem>
- <para>
- Offline/Online editing ...
- </para>
+ <formalpara>
+ <title>Usecase UC12</title>
+ Add/remove "common" styling derived from Schema (e.g. <code><i></code> in XHTML and <code><emphasis></code> in DocBook). Requires a mapping from these "common" styles to the specific Schema in use.
+ </formalpara>
</listitem>
+ <listitem>
+ <formalpara>
+ <title>Usecase UC13</title>
+ Apply multiple schemas allowing <emphasis>entanglement</emphasis> for internal representation.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Usecase UC14</title>
+ Automatic insertion of tags through training, derived from style. Insertion controllable by stepping through the document.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Usecase UC15</title>
+ Insertion (e.g. by Copy and Paste or Drag and Drop) of links to other assets.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Usecase UC16</title>
+ Insertion (e.g. by Copy and Paste or Drag and Drop) of blobs (e.g. images, ...). (NOTE: mapping between input and schema!)
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Usecase UC17</title>
+ Insertion (e.g. by Copy and Paste or Drag and Drop) of Schema-foreign elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Usecase UC18</title>
+ Insertion (e.g. by Copy and Paste or Drag and Drop) of (semi-)structured text (e.g. from Word, OpenOffice, ...) or pre-formatted clobs (e.g. program listings). (NOTE: mapping between input and schema!)
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Usecase UC19</title>
+ Word/OpenOffice functionality/usability (return means new paragraph!)
+ </formalpara>
+ </listitem>
</itemizedlist>
</para>
</section>
@@ -214,11 +256,6 @@
</listitem>
<listitem>
<para>
- Word/OpenOffice functionality/usability (return means new paragraph!)
- </para>
- </listitem>
- <listitem>
- <para>
Word/OpenOffice interoperability: ODT, WordXML, ... (import/export)
</para>
</listitem>
@@ -227,62 +264,635 @@
</section>
<section>
- <title>Special Features</title>
+ <title>Project Decomposition</title>
<para>
+ This decomposition serves the purpose of partitioning the project into implementable features. Note that a single usecase may need support from the front end as well as the back end, therefore a usecase may consist of several features in different components. It follows that in order to implement a usecase, features in the front as well as the back end must be implemented; the implementation though only has to be done in one variant of a component to have the usecase working for this variant. Therefore, the variants of a component are independent.
+ </para>
+ <section>
+ <title>Components and Variants</title>
+ <para>
+ The project consists of two components: the front end, and the back end. The front end component is divided into two variants: the editor integrated in a web browser, and a standalone editor. The back end component is divided into two variants as well: a client based variant and a server based variant.
+ </para>
+ <section>
+ <title>Front End Component (FRONTEND)</title>
+ <para>
+ The front end component is responsible for the handling the view. FRONTEND performs tasks like rendering the document, supplying user interaction facilities, etc.
+ </para>
+ <bridgehead>Common Feature Set</bridgehead>
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F1 (UC1, UC2, UC3, UC6)</title>
+ Open document from file system (<code>file://</code>).
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F1.1 (UC1, UC3, UC6)</title>
+ Open well-formed XML document from file system.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F1.2 (UC2, UC6, UC10)</title>
+ Open potentially associated meta-data from file system. Meta-data may be CMS information, XSLT, CSS and Schemas.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F1.3 (UC11)</title>
+ Open ill-formed XML document from file system.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F1.4 (UC13)</title>
+ Open entangled XML document from file system.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F2 (UC1, UC2, UC6)</title>
+ Save document to file system (<code>file://</code>).
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F2.1 (UC1, UC6)</title>
+ Save XML document to file system.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F2.2 (UC2, UC6, UC10)</title>
+ Save potentially associated meta-data to file system. Meta-data may be CMS information, XSLT, CSS and Schemas.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F2.3 (UC11)</title>
+ Save ill-formed XML document to file system.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F2.4 (UC13)</title>
+ Save entangled XML document to file system.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F3 (UC2, UC10, UC11, UC13)</title>
+ Open document from CMS.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F3.1 (UC2)</title>
+ Using HTTP protocol.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F3.2 (UC2)</title>
+ Using WebDAV protocol.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F3.3 (UC2)</title>
+ Using OSR-101 protocol.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F4 (UC2, UC3, UC10, UC11, UC13)</title>
+ Save document to CMS.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F4.1 (UC2, UC3)</title>
+ Using HTTP protocol.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F4.2 (UC2, UC3)</title>
+ Using WebDAV protocol.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F4.3 (UC2, UC3)</title>
+ Using OSR-101 protocol.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F5 (UC4)</title>
+ Fetch document template from CMS.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F5.1 (UC4)</title>
+ Using HTTP protocol.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F5.2 (UC4)</title>
+ Using WebDAV protocol.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F5.3 (UC4)</title>
+ Using OSR-101 protocol.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F6 (UC7)</title>
+ Edit in Source Mode.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F6.1 (UC7)</title>
+ Add/edit/delete text nodes.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F6.2 (UC7)</title>
+ Add/edit/delete elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F6.3 (UC7)</title>
+ Add/edit/delete element attributes.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7 (UC8, UC12, UC15, UC16, UC17, UC18, UC19)</title>
+ Edit in WYSIWYG Mode.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.1 (UC8)</title>
+ Add/edit/delete text nodes.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.2 (UC8)</title>
+ Add/edit/delete elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.3 (UC8)</title>
+ Add/remove Schema-specific styling.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.3.1 (UC8)</title>
+ Provide toolbar to select from Schema-specific styles.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.3.2 (UC8)</title>
+ Provide list of Schema-specific elements which represent styling (e.g. <code><i></code>, <code><tt></code> or <code><b></code> elements in XHTML) for each Schema in use. A "styling-element" is an XML element which is usually employed to solely convey styling information.
+ </formalpara>
+ <para>
+ Following is a list of Schema-specific styling-elements considered useful to be added to the FRONTEND. Extend this list if you find more useful Schemas.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.3.2.1 (UC8)</title>
+ XHTML styling-elements list.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.3.2.2 (UC8)</title>
+ DocBook styling-elements list.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.4 (UC8)</title>
+ Add/remove CSS styling.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.4.1 (UC8)</title>
+ Provide toolbar to select from predefined CSS styles.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.4.2 (UC8)</title>
+ Provide list of predefined CSS styles. These lists may be independent or associated with a given Schema.
+ </formalpara>
+ <para>
+ Following is a list of CSS styles considered useful to be added to the FRONTEND. Extend this list if you find more useful styles.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.4.2.1 (UC8)</title>
+ Independent common CSS styles.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.4.2.2 (UC8)</title>
+ Common CSS styles normally used in conjunction with XHTML.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.4.2.3 (UC8)</title>
+ Common CSS styles normally used in conjunction with DocBook.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.5 (UC12)</title>
+ Add/remove "common" styling derived from Schema in use.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.5.1 (UC12)</title>
+ Provide toolbar to select from Schema-derived "common" styles.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.5.2 (UC12)</title>
+ Provide a mapping between a set of "common" styles and the corresponding elements of the Schema in use.
+ </formalpara>
+ <para>
+ Following is a list of mappings from a "common" style set to specific elements of Schemas which are considered useful to be added to the FRONTEND. Extend this list if you want more mappings available.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.5.2.1 (UC12)</title>
+ Mapping between the "common" style and XHTML elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.5.2.2 (UC12)</title>
+ Mapping between the "common" style and DocBook elements.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.6 (UC15)</title>
+ Insertion of links to other assets.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.7 (UC16)</title>
+ Insertion of blobs. Requires a mapping between "common" blobs and the the Schema-specific elements which represent such blobs (e.g. <code><img></code> in XHTMl and <code><imageobject></code> in DocBook).
+ </formalpara>
+ <para>
+ Following is a list of mappings from "common" blobs to Schema-specific elements which are considered useful to be added to the FRONTEND. Extend this list if you want more mappings available.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.7.1 (UC16)</title>
+ Mapping between "common" blobs and XHTML elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.7.2 (UC16)</title>
+ Mapping between the "common" blobs and DocBook elements.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.8 (UC17)</title>
+ Insertion of Schema-foreign elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.9 (UC18)</title>
+ Insertion of (semi-)structured text or pre-formatted clobs. Requires a mapping between every input source and the Schema in use.
+ </formalpara>
+ <para>
+ Following is a list of mappings from input sources to Schemas considered useful to be added to the FRONTEND. Extend this list if you want more mappings available.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.9.1 (UC18)</title>
+ Mapping between WordXML clobs and XHTML elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.9.2 (UC18)</title>
+ Mapping between ODT clobs and XHTML elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.9.3 (UC18)</title>
+ Mapping between WordXML clobs and DocBook elements.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.9.4 (UC18)</title>
+ Mapping between ODT clobs and DocBook elements.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F7.10 (UC19)</title>
+ Word-processor style usage.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F8 (UC7, UC8)</title>
+ Content Assist, providing suggestions for element names, attributes names and attribute content.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F9 (UC9)</title>
+ Visualise results of Schema validation.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F10 (UC14)</title>
+ Toolbar to train automatic tag inserter.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature F11 (UC14)</title>
+ Toolbar to guide step-wise automatic tag inserter.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ <section>
+ <title>Browser Integrated Variant (BROWSER)</title>
+ <para>
+ The browser integrated variant of FRONTEND is a XUL widget which integrates seamlessly into web browsers based on the Mozilla Platform. BROWSER must be able to work with up-to-date versions of Firefox and SeaMonkey (formerly Mozilla Suite).
+ </para>
+ </section>
+ <section>
+ <title>Standalone Variant (STANDALONE)</title>
+ <para>
+ The standalone variant of the FRONTEND can be used as a standalone editor, independent of a web browser. Like the browser integrated version, STANDALONE is based on XUL.
+ </para>
+ </section>
+ </section>
+ <section>
+ <title>Back End Component (BACKEND)</title>
+ <para>
+ The back end component comprises the controller and the model. BACKEND performs tasks like ID Tagging, XSLT processing, validation, etc.
+ </para>
+ <bridgehead>Common Feature Set</bridgehead>
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature B1 (UC8)</title>
+ Retrieve XSLT from CMS.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature B2 (UC8, UC10, UC11)</title>
+ Retrieve CSS from CMS.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature B3 (UC9)</title>
+ Retrieve Schema from Schema server. Note that the Schema server may be the CMS or some other unrelated host on the network.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature B3.1 (UC9)</title>
+ Retrieve RelaxNG Schema from Schema server.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature B3.2 (UC9)</title>
+ Retrieve W3C XML Schema from Schema server.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature B3.3 (UC9)</title>
+ Retrieve DTD from Schema server.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ <section>
+ <title>Client Based Variant (CLIENT)</title>
+ <para>
+ The client based variant of BACKEND places the back end logic on the client side.
+ </para>
+ <bridgehead>Feature Set</bridgehead>
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature BC1 (UC8)</title>
+ Retrieve XSLT from local file system.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature BC2 (UC8, UC10, UC11)</title>
+ Retrieve CSS from local file system.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature BC3 (UC9)</title>
+ Retrieve Schema from local file system.
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature BC3.1 (UC9)</title>
+ Retrieve RelaxNG Schema from local file system.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature BC3.2 (UC9)</title>
+ Retrieve W3C XML Schema from local file system.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature BC3.3 (UC9)</title>
+ Retrieve DTD from local file system.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>Server Based (SERVER)</title>
+ <para>
+ The server based variant of BACKEND places the back end logic on the server side. SERVER additionally provides logic for FRONTEND to be able to communicate with the server side code.
+ </para>
+ <para>
+ Note that offline editing may not be fully functional with variant SERVER.
+ </para>
+ <bridgehead>Feature Set</bridgehead>
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature BS1 (UC8)</title>
+ Upload XSLT from local file system to SERVER. Since the XSLT processor resides on SERVER, we first have to upload the XSLT we want to use for rendering if we started off with a document on the local file system. Otherwise, SERVER can retrieve the XSLT directly from the CMS (feature B1).
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature BS2 (UC9)</title>
+ Upload Schema from local file system to SERVER. Since the validation logic resides on SERVER, we first have to upload the Schema we want to use for validation if we started off with a document on the local file system. Otherwise, SERVER can retrieve the Schema directly from the Schema server (feature B3).
+ <itemizedlist>
+ <listitem>
+ <formalpara>
+ <title>Feature BS2.1 (UC9)</title>
+ Upload RelaxNG Schema from local file system to SERVER.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature BS2.2 (UC9)</title>
+ Upload W3C XML Schema from local file system to SERVER.
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara>
+ <title>Feature BS2.3 (UC9)</title>
+ Upload DTD from local file system to SERVER.
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+ </section>
+ </section>
+
+ <section>
+ <title>Open Issues/To be discussed</title>
+ <para>
<itemizedlist>
<listitem>
<para>
- Content Assist
+ Should we keep the source editing mode simple and stupid (i.e. only have the trivial operations of add/edit/delete of text nodes, elements and attributes), or should we add features like link insertion, etc.?
</para>
</listitem>
<listitem>
<para>
- Drag and Drop of images/links/... (NOTE: Mapping between image and schema!)
+ Implementation language (Java (also interesting for SERVER), C++, etc.)
</para>
</listitem>
<listitem>
<para>
- Copy and Paste of (semi-)structured text (e.g. Word, ...) (NOTE: mapping between input and schema!)
+ Amount of reuse (Etna project, Mozilla Platform, etc.)
</para>
</listitem>
<listitem>
<para>
- Drag and Drop of <emphasis>elements</emphasis> ...
+ License (GPL, GPL+Commercial, LGPL, MPL, etc.)
</para>
</listitem>
+ <listitem>
+ <para>
+ Date of going public
+ </para>
+ </listitem>
</itemizedlist>
</para>
</section>
<section>
- <title>Open Issues/To be discussed</title>
+ <title>Reasoning</title>
<para>
+ Why do we want to use the Mozilla platform for Phoenix:
<itemizedlist>
<listitem>
<para>
- Used language (Java, also interesting for server version)
+ No gap between browser and editing tool (e.g. OpenOffice, ...)!
</para>
</listitem>
<listitem>
<para>
- Server based solution
+ Platform independence (Windows, Linux, MacOS, UNIX, ...)!
</para>
</listitem>
<listitem>
<para>
- Standanlone solution
+ Offline/Online editing ...
</para>
</listitem>
- <listitem>
- <para>
- License (GPL, GPL+Commercial, LGPL, etc.)
- </para>
- </listitem>
- <listitem>
- <para>
- Date of going public
- </para>
- </listitem>
</itemizedlist>
</para>
</section>
Modified: public/phoenix/deliverables/planning/roadmap.xhtml
===================================================================
--- public/phoenix/deliverables/planning/roadmap.xhtml 2006-05-02 16:15:56 UTC (rev 12999)
+++ public/phoenix/deliverables/planning/roadmap.xhtml 2006-05-02 21:27:13 UTC (rev 13000)
@@ -14,19 +14,21 @@
<h1 class="title"><a id="id52598"/>Phoenix Roadmap</h1>
</div>
<div>
- <div class="author">
- <h3 class="author"><span class="firstname">Andreas</span> <span class="surname">Wuest</span></h3>
- <div class="affiliation">
- <div class="address">
- <p><br/>
- <code class="email"><<a href="mailto:awuest at student.ethz.ch">awuest at student.ethz.ch</a>></code><br/>
- </p>
+ <div class="authorgroup">
+ <div class="author">
+ <h3 class="author"><span class="firstname">Andreas</span> <span class="surname">Wuest</span></h3>
+ <div class="affiliation">
+ <div class="address">
+ <p><br/>
+ <code class="email"><<a href="mailto:awuest at student.ethz.ch">awuest at student.ethz.ch</a>></code><br/>
+ </p>
+ </div>
</div>
</div>
</div>
</div>
<div>
- <p class="pubdate">2006-04-28</p>
+ <p class="pubdate">2006-05-02</p>
</div>
<div>
<div class="revhistory">
@@ -38,7 +40,7 @@
</tr>
<tr>
<td align="left">Revision 1.0</td>
- <td align="left">2006-04-28</td>
+ <td align="left">2006-05-02</td>
<td align="left">AW</td>
</tr>
<tr>
@@ -65,52 +67,52 @@
<dl>
<dt>
<span class="section">
- <a href="#id342752">1. Project Overview</a>
+ <a href="#id342756">1. Project Overview</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="section">
- <a href="#id342761">1.1. Components and Variants</a>
+ <a href="#id342764">1.1. Components and Variants</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="section">
- <a href="#id342775">1.1.1. Front End Component (FRONTEND)</a>
+ <a href="#id342778">1.1.1. Front End Component (FRONTEND)</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="section">
- <a href="#id342786">1.1.1.1. Browser Integrated Variant (BROWSER)</a>
+ <a href="#id342790">1.1.1.1. Browser Integrated Variant (BROWSER)</a>
</span>
</dt>
<dt>
<span class="section">
- <a href="#id342801">1.1.1.2. Standalone Variant (STANDALONE)</a>
+ <a href="#id342804">1.1.1.2. Standalone Variant (STANDALONE)</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="section">
- <a href="#id342815">1.1.2. Back End Component (BACKEND)</a>
+ <a href="#id342818">1.1.2. Back End Component (BACKEND)</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="section">
- <a href="#id342826">1.1.2.1. Client Based Variant (CLIENT)</a>
+ <a href="#id342829">1.1.2.1. Client Based Variant (CLIENT)</a>
</span>
</dt>
<dt>
<span class="section">
- <a href="#id342836">1.1.2.2. Server Based (SERVER)</a>
+ <a href="#id342839">1.1.2.2. Server Based (SERVER)</a>
</span>
</dt>
</dl>
@@ -119,13 +121,27 @@
</dd>
</dl>
</dd>
+ <dt>
+ <span class="section">
+ <a href="#id342855">2. Schedule</a>
+ </span>
+ </dt>
+ <dd>
+ <dl>
+ <dt>
+ <span class="section">
+ <a href="#id342866">2.1. Milestone 1 (M1)</a>
+ </span>
+ </dt>
+ </dl>
+ </dd>
</dl>
</div>
<div class="section" lang="en">
<div class="titlepage">
<div>
<div>
- <h2 class="title"><a id="id342752"/>1. Project Overview</h2>
+ <h2 class="title"><a id="id342756"/>1. Project Overview</h2>
</div>
</div>
</div>
@@ -135,7 +151,7 @@
<div class="titlepage">
<div>
<div>
- <h3 class="title"><a id="id342761"/>1.1. Components and Variants</h3>
+ <h3 class="title"><a id="id342764"/>1.1. Components and Variants</h3>
</div>
</div>
</div>
@@ -146,7 +162,7 @@
<div class="titlepage">
<div>
<div>
- <h4 class="title"><a id="id342775"/>1.1.1. Front End Component (FRONTEND)</h4>
+ <h4 class="title"><a id="id342778"/>1.1.1. Front End Component (FRONTEND)</h4>
</div>
</div>
</div>
@@ -157,7 +173,7 @@
<div class="titlepage">
<div>
<div>
- <h5 class="title"><a id="id342786"/>1.1.1.1. Browser Integrated Variant (BROWSER)</h5>
+ <h5 class="title"><a id="id342790"/>1.1.1.1. Browser Integrated Variant (BROWSER)</h5>
</div>
</div>
</div>
@@ -169,7 +185,7 @@
<div class="titlepage">
<div>
<div>
- <h5 class="title"><a id="id342801"/>1.1.1.2. Standalone Variant (STANDALONE)</h5>
+ <h5 class="title"><a id="id342804"/>1.1.1.2. Standalone Variant (STANDALONE)</h5>
</div>
</div>
</div>
@@ -182,7 +198,7 @@
<div class="titlepage">
<div>
<div>
- <h4 class="title"><a id="id342815"/>1.1.2. Back End Component (BACKEND)</h4>
+ <h4 class="title"><a id="id342818"/>1.1.2. Back End Component (BACKEND)</h4>
</div>
</div>
</div>
@@ -193,7 +209,7 @@
<div class="titlepage">
<div>
<div>
- <h5 class="title"><a id="id342826"/>1.1.2.1. Client Based Variant (CLIENT)</h5>
+ <h5 class="title"><a id="id342829"/>1.1.2.1. Client Based Variant (CLIENT)</h5>
</div>
</div>
</div>
@@ -205,7 +221,7 @@
<div class="titlepage">
<div>
<div>
- <h5 class="title"><a id="id342836"/>1.1.2.2. Server Based (SERVER)</h5>
+ <h5 class="title"><a id="id342839"/>1.1.2.2. Server Based (SERVER)</h5>
</div>
</div>
</div>
@@ -216,6 +232,122 @@
</div>
</div>
</div>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h2 class="title"><a id="id342855"/>2. Schedule</h2>
+ </div>
+ </div>
+ </div>
+ <p>
+ The schedule consists of multiple mile stones, which are defined by the set of features which are to be implemented by this point.
+ </p>
+ <div class="section" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h3 class="title"><a id="id342866"/>2.1. Milestone 1 (M1)</h3>
+ </div>
+ </div>
+ </div>
+ <p>
+ Features:
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p>
+ FRONTEND
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p>
+ BROWSER
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p>
+
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ <li>
+ <p>
+ STANDALONE
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p>
+ A standalone front end is not planned for this mile stone.
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ <li>
+ <p>
+ BACKEND
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p>
+ CLIENT
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p>
+
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ <li>
+ <p>
+ SERVER
+ </p>
+ <div class="itemizedlist">
+ <ul>
+ <li>
+ <p>
+ A server back end is not planned for htis mile stone.
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </li>
+ </ul>
+ </div>
+ <p>
+ </p>
+ </div>
+ </div>
</div>
</body>
</html>
Modified: public/phoenix/deliverables/planning/roadmap.xml
===================================================================
--- public/phoenix/deliverables/planning/roadmap.xml 2006-05-02 16:15:56 UTC (rev 12999)
+++ public/phoenix/deliverables/planning/roadmap.xml 2006-05-02 21:27:13 UTC (rev 13000)
@@ -10,22 +10,24 @@
<article>
<articleinfo>
<title>&project; Roadmap</title>
- <author>
- <firstname>Andreas</firstname>
- <surname>Wuest</surname>
- <affiliation>
- <address>
- <email>awuest at student.ethz.ch</email>
- </address>
- </affiliation>
- </author>
+ <authorgroup>
+ <author>
+ <firstname>Andreas</firstname>
+ <surname>Wuest</surname>
+ <affiliation>
+ <address>
+ <email>awuest at student.ethz.ch</email>
+ </address>
+ </affiliation>
+ </author>
+ </authorgroup>
<!-- All dates specified in ISO "YYYY-MM-DD" format -->
- <pubdate>2006-04-28</pubdate>
+ <pubdate>2006-05-02</pubdate>
<!-- Most recent revision goes at the top; list in descending order -->
<revhistory>
<revision>
<revnumber>1.0</revnumber>
- <date>2006-04-28</date>
+ <date>2006-05-02</date>
<authorinitials>AW</authorinitials>
<revremark>First initial draft.</revremark>
</revision>
@@ -83,4 +85,81 @@
</section>
</section>
+ <section>
+ <title>Schedule</title>
+ <para>
+ The schedule consists of multiple mile stones, which are defined by the set of features which are to be implemented by this point.
+ </para>
+ <section>
+ <title>Milestone 1 (M1)</title>
+ <para>
+ Features:
+ <itemizedlist>
+ <listitem>
+ <para>
+ FRONTEND
+ <itemizedlist>
+ <listitem>
+ <para>
+ BROWSER
+ <itemizedlist>
+ <listitem>
+ <para>
+
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ STANDALONE
+ <itemizedlist>
+ <listitem>
+ <para>
+ A standalone front end is not planned for this mile stone.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ BACKEND
+ <itemizedlist>
+ <listitem>
+ <para>
+ CLIENT
+ <itemizedlist>
+ <listitem>
+ <para>
+
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ SERVER
+ <itemizedlist>
+ <listitem>
+ <para>
+ A server back end is not planned for htis mile stone.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </section>
+ </section>
+
</article>
More information about the Phoenix-commits
mailing list