incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksch...@apache.org
Subject svn commit: r1175554 [1/2] - /incubator/ooo/ooo-site/trunk/content/xml/
Date Sun, 25 Sep 2011 19:43:42 GMT
Author: kschenk
Date: Sun Sep 25 19:43:42 2011
New Revision: 1175554

URL: http://svn.apache.org/viewvc?rev=1175554&view=rev
Log:
KLS - added xml repository

Added:
    incubator/ooo/ooo-site/trunk/content/xml/
    incubator/ooo/ooo-site/trunk/content/xml/faq.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/faq.xml   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/faq.xsl   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/filters.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/general.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/index.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/index2.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/modules.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/opendocument-cropped_0.jpg   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/package.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/project_tools.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/research.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/robots.txt   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/uses.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/xfilter.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/xml_advocacy.html   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/xml_specification.pdf   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/xml_specification_draft.pdf   (with props)
    incubator/ooo/ooo-site/trunk/content/xml/xmloff.css   (with props)

Added: incubator/ooo/ooo-site/trunk/content/xml/faq.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/faq.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/faq.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/faq.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,293 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+	<p><strong>Note:</strong>This FAQ is for the OpenOffice.org XML file format only. OASIS OpenDocument/ISO/IEC 26300 FAQs are available at <a href="http://www.oasis-open.org/committees/office/faq.php">OASIS</a> and <a href="http://opendocument.xml.org/faq">opendocument.xml.org</a>.<p>
+<a name="top"></a><p><img alt="" src="http://www.openoffice.org/branding/images/start_blue_bar.gif">&nbsp;&nbsp;<font size="-1"><b>MOST FREQUENTLY ASKED QUESTIONS: QUESTIONS</b></font>&nbsp;&nbsp;<img alt="" src="http://www.openoffice.org/branding/images/end_blue_bar.gif"></p><ol>
+
+ <li><a href="#1">
+    Which OpenOffice.org application uses XML-based file formats?
+  </a></li>
+
+ <li><a href="#2">
+    What are the default file extensions for XML-based documents?
+  </a></li>
+
+ <li><a href="#3">
+    What is all that binary goo I see in your files?
+  </a></li>
+
+ <li><a href="#4">
+    What package format do you use, and what do I find inside?    
+  </a></li>
+
+ <li><a href="#5">
+    How can I put additional information into an XML file?
+  </a></li>
+
+ <li><a href="#6">
+    But I really, really want plain XML. No compression, no binary
+    data, no nothing. Just plain XML. Can I have that, please?
+  </a></li>
+
+ <li><a href="#7">
+    Why are so many styles written out?
+  </a></li>
+
+ <li><a href="#8">
+    How are embedded images and binary data handled?
+  </a></li>
+
+ <li><a href="#9">
+    Why didn't you use XHTML, XSL-FO, SVG, etc. ?
+  </a></li>
+
+ <li><a href="#10">
+    Can I write an XML translation from or into  ...?
+  </a></li>
+
+ <li><a href="#11">
+    I found a bug. What do I do?
+  </a></li>
+
+ <li><a href="#12">
+    Hey, I like your XML format. How can I help?
+  </a></li>
+
+ <li><a href="#13">
+    But what about ...? And why isn't
+    my favorite question in here?
+  </a></li>
+
+ 
+
+</ol><p><img alt="" src="http://www.openoffice.org/branding/images/start_blue_bar.gif">&nbsp;&nbsp;<font size="-1"><b>MOST FREQUENTLY ASKED QUESTIONS: ANSWERS</b></font>&nbsp;&nbsp;<img alt="" src="http://www.openoffice.org/branding/images/end_blue_bar.gif"></p>
+
+ <ol><a name="1"></a><li value="1"><b>
+    Which OpenOffice.org application uses XML-based file formats?
+  </b><p><answer>
+    All OpenOffice.org applications use XML-based file formats. All
+    applications (except Math) use the same format as defined in our <a href="xml_specification.pdf">specification</a>. 
+    The Math component uses our package structure and format (see
+    below), but uses <a href="http://www.w3.org/Math/">MathML</a>
+    inside the package.
+  </answer></p><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="2"></a><li value="2"><b>
+    What are the default file extensions for XML-based documents?
+  </b><answer>
+    <table summary="OpenOffice.org XML file types">
+     <tr> <th>Writer</th> <td>sxw</td> </tr>
+     <tr> <th>Calc</th> <td>sxc</td> </tr>
+     <tr> <th>Draw</th> <td>sxd</td> </tr>
+     <tr> <th>Impress</th> <td>sxi</td> </tr>
+     <tr> <th>Math</th> <td>sxm</td> </tr>
+     <tr> <th>Writer<br>global document</th> <td>sxg</td> </tr>
+    </table>
+    <p>XML is also used in other OpenOffice.org files
+    (e.g. configuration) which are not covered in the <tt>xmloff</tt> 
+    project.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="3"></a><li value="3"><b>
+    What is all that binary goo I see in your files?
+  </b><answer>
+    <p>Our documents use packages that contain the XML data alongside
+    binary data such as images. The packages use the well known ZIP format. 
+    Just open an sxw/sxc/... file with a ZIP-tool of your choice, and 
+    you get access to the unadulterated XML.</p>
+    <p>The document meta data (in the meta.xml stream) is not
+    compressed. This allows for easy searching and extraction of the
+    meta data.</p>
+    <p> For more information on our packages, see the next question. </p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="4"></a><li value="4"><b>
+    What package format do you use, and what do I find inside?    
+  </b><answer>
+
+    <p>We use the well-known ZIP file format as a package format. In
+    addition, we store an XML-based manifest file that describes the
+    package content and may supply additional information about the
+    included files (e.g. encryption method). Since we use ZIP, most
+    archive programs can already handle our files.</p>
+
+    <p>Inside the package, you generally find several streams that
+    make up the full office document. These are: </p>
+
+    <table>
+     <tr> 
+      <th>meta.xml</th> 
+      <td>information about the document (author, time of last save, ...)</td>
+     </tr>
+     <tr>
+      <th>styles.xml</th>
+      <td>styles that are used in the document</td>
+     </tr>
+     <tr>
+      <th>content.xml</th>
+      <td>main document content (text, tables, graphical elements)</td>
+     </tr>
+     <tr>
+      <th>settings.xml</th>
+      <td>document and view settings (such as magnification level and 
+          selected printer); these are usually application specific </td>
+     </tr>
+     <tr>
+      <th>META-INF/manifest.xml</th>
+      <td>provides additional information about the other files (such
+      as MIME type or encryption method)</td>
+     </tr>
+     <tr>
+      <th>Pictures/</th>
+      <td>directory containing images (in their native, binary formats)</td>
+     </tr>
+     <tr>
+      <th>Dialogs/</th>
+      <td>directory containing dialogs used by document macros</td>
+     </tr>
+     <tr>
+      <th>Basic/</th>
+      <td>directory containing StarBasic macros</td>
+     </tr>
+     <tr>
+      <th>Obj.../</th>
+      <td>directories containing embedded objects, such as charts;
+      each directory contains one such object, stored in its native format.
+      For OpenOffice.org objects that is its XML representation, for other
+      objects it's usually a binary format.</td>
+     </tr>
+    </table>
+
+    <p>For more information on why we chose ZIP, please read <a href="package.html">package.html</a>. For more information on the
+    ZIP format itself, please look <a href="http://www.wotsit.org/">here</a>.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="5"></a><li value="5"><b>
+    How can I put additional information into an XML file?
+  </b><answer>
+    <p><em>Alien</em> attributes, i.e. attributes not defined in the
+    OpenOffice.org DTD, will be preserved if they are attached to
+    <code>&lt;style:properties&gt;</code> elements in style
+    definitions. All other alien content will be discarded by the
+    OpenOffice.org import filters.</p>
+    <p>Since you can attach styles to arbitrary text ranges, you can
+    use this mechanism to attach your information to arbitrary text
+    ranges, too.</p>
+    <p><strong>Note:</strong> The above mechanism seems to only work
+    in Writer. The issue is under investigation.</p>
+    <p>It is planned that you can also put additional files with your
+    own content into the packages. However, this doesn't work yet.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="6"></a><li value="6"><b>
+    But I really, really want plain XML. No compression, no binary
+    data, no nothing. Just plain XML. Can I have that, please?
+  </b><answer>
+    <p>For purposes of import and export, we provide <a href="http://udk.openoffice.org/">UNO</a>-based services that
+    allow you to import or export XML data through the SAX
+    interface. A documentation of this technique is available <a href="filter/">here</a>.</p>
+    <p>Also, it is planned to allow plain XML files (without packages)
+    to be read and written. However, this is not implemented yet.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="7"></a><li value="7"><b>
+    Why are so many styles written out?
+  </b><answer>
+    <p>In general, styles that are used in the document or that have been
+    modified by the user are written to disk. The former is necessary
+    to render the document correctly. The latter is preserved because
+    if a user edited those styles, he/she is likely to use them later
+    on. Therefore, those styles should not be discarded, even though
+    they do not contribute to the document in its current form and
+    shape.</p>
+    <p>If styles that meet neither of these criteria are written, then
+    this is may be considered a bug. The Draw, Impress, and Calc
+    applications currently show this behavior. </p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="8"></a><li value="8"><b>
+    How are embedded images and binary data handled?
+  </b><p><answer>
+    Images and embedded objects are stored in their native formats
+    into the ZIP-based package format.
+  </answer></p><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="9"></a><li value="9"><b>
+    Why didn't you use XHTML, XSL-FO, SVG, etc. ?
+  </b><answer>
+    <p>Those formats are not used because they do not have a
+    suitable level of presentation for office documents. When we found an
+    established format (like the ones mentioned above) contains
+    concepts that are used in OpenOffice.org as well, then we
+    generally adopted their representation for those concepts in our
+    XML format. We hope this will ease transformation between the
+    formats.</p>
+
+<!--
+    <p>As an example for the unsuitable level of presentation consider
+    text fields: A text field contains a string of text that gets
+    automatically for this consider text fields: Text fields are
+    special regions of text strings that are automatically updated by
+    the application. The text fields must be preserved, of course, so
+    the application can continue to update them. While the above
+    formats easily accomodate the text field output (after all, it's
+    just a string of text), they can only be represented by some sort
+    of extension to the basic format. Since these sort of issues
+    occur quite a lot, it seemed more prudent to create an own format.</p>
+-->
+
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="10"></a><li value="10"><b>
+    Can I write an XML translation from or into  ...?
+  </b><answer>
+    <p>You are absolutely welcome to write transformation from our
+    XML-based file format into and from anything you see fit.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="11"></a><li value="11"><b>
+    I found a bug. What do I do?
+  </b><answer>
+    <p>Report it using <a href="http://www.openoffice.org/issues/enter_bug.cgi">IssueZilla</a>. Try
+    to give a detailed description of what went wrong. Don't forget to
+    include the document in which the error occurred. (After submission
+    of the bug, choose "create attachment".)</p>
+    <p><strong>DON'T BE SHY ABOUT REPORTING BUGS!</strong> All of us
+    are interested in stable and bug-free applications, and bug
+    reports from our users are a very important means towards that
+    end. Bug reports help all of us. If you don't report your
+    findings, we can't fix them, and so they will cause problems for
+    users as well.</p>
+  </answer><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="12"></a><li value="12"><b>
+    Hey, I like your XML format. How can I help?
+  </b><p><answer>
+    There are many things you can do to help.
+    <ol>
+     <li>You can spread the word, e.g. by telling your friends and
+     co-workers about OpenOffice.org.</li>
+     <li>You can use the OpenOffice.org applications and report any
+     bugs you find.</li>
+     <li>You can program transformation from our format into others
+     (and vice versa).</li>
+     <li>You can implement one of the suggestions on the todo list on our homepage. </li>
+    </ol>
+  </answer></p><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ <ol><a name="13"></a><li value="13"><b>
+    But what about ...? And why isn't
+    my favorite question in here?
+  </b><p><answer>
+    If your question is not answered here, ask it on our mailing
+    list. You can view the archives <a href="http://xml.openoffice.org/xml-dev/">here</a>. Instructions
+    for joining the list are on our <a href="http://xml.openoffice.org">project homepage</a>.
+  </answer></p><br></li></ol><a href="#top">Back to top</a><hr noshade="noshade" size="1" align="left"><br>
+
+ 
+
+<p><small>FAQ maintained by <a href="mailto:dvo@openoffice.org">dvo</a>.</small></p>
+</body>
+</html>
+

Propchange: incubator/ooo/ooo-site/trunk/content/xml/faq.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/faq.xml
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/faq.xml?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/faq.xml (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/faq.xml Sun Sep 25 19:43:42 2011
@@ -0,0 +1,286 @@
+
+<faqs
+    maintainer="Daniel.Vogelheim@germany.sun.com"
+    maintainer-name="dvo" >
+
+ <faq>
+  <question>
+    Which OpenOffice.org application uses XML-based file formats?
+  </question>
+  <answer>
+    All OpenOffice.org applications use XML-based file formats. All
+    applications (except Math) use the same format as defined in our <a
+    href="xml_specification_draft.pdf">specification</a>. 
+    The Math component uses our package structure and format (see
+    below), but uses <a href="http://www.w3.org/Math/">MathML</a>
+    inside the package.
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    What are the default file extensions for XML-based documents?
+  </question>
+  <answer>
+    <table summary="OpenOffice.org XML file types">
+     <tr> <th>Writer</th> <td>sxw</td> </tr>
+     <tr> <th>Calc</th> <td>sxc</td> </tr>
+     <tr> <th>Draw</th> <td>sxd</td> </tr>
+     <tr> <th>Impress</th> <td>sxi</td> </tr>
+     <tr> <th>Math</th> <td>sxm</td> </tr>
+     <tr> <th>Writer<br/>global document</th> <td>sxg</td> </tr>
+    </table>
+    <p>XML is also used in other OpenOffice.org files
+    (e.g. configuration) which are not covered in the <tt>xmloff</tt> 
+    project.</p>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    What is all that binary goo I see in your files?
+  </question>
+  <answer>
+    <p>Our documents use packages that contain the XML data alongside
+    binary data such as images. The packages use the well known ZIP format. 
+    Just open an sxw/sxc/... file with a ZIP-tool of your choice, and 
+    you get access to the unadulterated XML.</p>
+    <p>The document meta data (in the meta.xml stream) is not
+    compressed. This allows for easy searching and extraction of the
+    meta data.</p>
+    <p> For more information on our packages, see the next question. </p>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    What package format do you use, and what do I find inside?    
+  </question>
+  <answer>
+
+    <p>We use the well-known ZIP file format as a package format. In
+    addition, we store an XML-based manifest file that describes the
+    package content and may supply additional information about the
+    included files (e.g. encryption method). Since we use ZIP, most
+    archive programs can already handle our files.</p>
+
+    <p>Inside the package, you generally find several streams that
+    make up the full office document. These are: </p>
+
+    <table>
+     <tr> 
+      <th>meta.xml</th> 
+      <td>information about the document (author, time of last save, ...)</td>
+     </tr>
+     <tr>
+      <th>styles.xml</th>
+      <td>styles that are used in the document</td>
+     </tr>
+     <tr>
+      <th>content.xml</th>
+      <td>main document content (text, tables, graphical elements)</td>
+     </tr>
+     <tr>
+      <th>settings.xml</th>
+      <td>document and view settings (such as magnification level and 
+          selected printer); these are usually application specific </td>
+     </tr>
+     <tr>
+      <th>META-INF/manifest.xml</th>
+      <td>provides additional information about the other files (such
+      as MIME type or encryption method)</td>
+     </tr>
+     <tr>
+      <th>Pictures/</th>
+      <td>directory containing images (in their native, binary formats)</td>
+     </tr>
+     <tr>
+      <th>Dialogs/</th>
+      <td>directory containing dialogs used by document macros</td>
+     </tr>
+     <tr>
+      <th>Basic/</th>
+      <td>directory containing StarBasic macros</td>
+     </tr>
+     <tr>
+      <th>Obj.../</th>
+      <td>directories containing embedded objects, such as charts;
+      each directory contains one such object, stored in its native format.
+      For OpenOffice.org objects that is its XML representation, for other
+      objects it's usually a binary format.</td>
+     </tr>
+    </table>
+
+    <p>For more information on why we chose ZIP, please read <a
+    href="package.html">package.html</a>. For more information on the
+    ZIP format itself, please look <a
+    href="http://www.wotsit.org/">here</a>.</p>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    How can I put additional information into an XML file?
+  </question>
+  <answer>
+    <p><em>Alien</em> attributes, i.e. attributes not defined in the
+    OpenOffice.org DTD, will be preserved if they are attached to
+    <code>&lt;style:properties&gt;</code> elements in style
+    definitions. All other alien content will be discarded by the
+    OpenOffice.org import filters.</p>
+    <p>Since you can attach styles to arbitrary text ranges, you can
+    use this mechanism to attach your information to arbitrary text
+    ranges, too.</p>
+    <p><strong>Note:</strong> The above mechanism seems to only work
+    in Writer. The issue is under investigation.</p>
+    <p>It is planned that you can also put additional files with your
+    own content into the packages. However, this doesn't work yet.</p>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    But I really, really want plain XML. No compression, no binary
+    data, no nothing. Just plain XML. Can I have that, please?
+  </question>
+  <answer>
+    <p>For purposes of import and export, we provide <a
+    href="http://udk.openoffice.org/">UNO</a>-based services that
+    allow you to import or export XML data through the SAX
+    interface. A documentation of this technique is available <a
+    href="filter/">here</a>.</p>
+    <p>Also, it is planned to allow plain XML files (without packages)
+    to be read and written. However, this is not implemented yet.</p>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    Why are so many styles written out?
+  </question>
+  <answer>
+    <p>In general, styles that are used in the document or that have been
+    modified by the user are written to disk. The former is necessary
+    to render the document correctly. The latter is preserved because
+    if a user edited those styles, he/she is likely to use them later
+    on. Therefore, those styles should not be discarded, even though
+    they do not contribute to the document in its current form and
+    shape.</p>
+    <p>If styles that meet neither of these criteria are written, then
+    this is may be considered a bug. The Draw, Impress, and Calc
+    applications currently show this behavior. </p>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    How are embedded images and binary data handled?
+  </question>
+  <answer>
+    Images and embedded objects are stored in their native formats
+    into the ZIP-based package format.
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    Why didn't you use XHTML, XSL-FO, SVG, etc. ?
+  </question>
+  <answer>
+    <p>Those formats are not used because they do not have a
+    suitable level of presentation for office documents. When we found an
+    established format (like the ones mentioned above) contains
+    concepts that are used in OpenOffice.org as well, then we
+    generally adopted their representation for those concepts in our
+    XML format. We hope this will ease transformation between the
+    formats.</p>
+
+<!--
+    <p>As an example for the unsuitable level of presentation consider
+    text fields: A text field contains a string of text that gets
+    automatically for this consider text fields: Text fields are
+    special regions of text strings that are automatically updated by
+    the application. The text fields must be preserved, of course, so
+    the application can continue to update them. While the above
+    formats easily accomodate the text field output (after all, it's
+    just a string of text), they can only be represented by some sort
+    of extension to the basic format. Since these sort of issues
+    occur quite a lot, it seemed more prudent to create an own format.</p>
+-->
+
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    Can I write an XML translation from or into  ...?
+  </question>
+  <answer>
+    <p>You are absolutely welcome to write transformation from our
+    XML-based file format into and from anything you see fit.</p>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    I found a bug. What do I do?
+  </question>
+  <answer>
+    <p>Report it using <a
+    href="http://www.openoffice.org/issues/enter_bug.cgi">IssueZilla</a>. Try
+    to give a detailed description of what went wrong. Don't forget to
+    include the document in which the error occurred. (After submission
+    of the bug, choose "create attachment".)</p>
+    <p><strong>DON'T BE SHY ABOUT REPORTING BUGS!</strong> All of us
+    are interested in stable and bug-free applications, and bug
+    reports from our users are a very important means towards that
+    end. Bug reports help all of us. If you don't report your
+    findings, we can't fix them, and so they will cause problems for
+    users as well.</p>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    Hey, I like your XML format. How can I help?
+  </question>
+  <answer>
+    There are many things you can do to help.
+    <ol>
+     <li>You can spread the word, e.g. by telling your friends and
+     co-workers about OpenOffice.org.</li>
+     <li>You can use the OpenOffice.org applications and report any
+     bugs you find.</li>
+     <li>You can program transformation from our format into others
+     (and vice versa).</li>
+     <li>You can implement one of the suggestions on the todo list on our homepage. </li>
+    </ol>
+  </answer>
+ </faq>
+
+ <faq>
+  <question>
+    But what about ...? And why isn't
+    my favorite question in here?
+  </question>
+  <answer>
+    If your question is not answered here, ask it on our mailing
+    list. You can view the archives <a
+    href="http://xml.openoffice.org/xml-dev/">here</a>. Instructions
+    for joining the list are on our <a
+    href="http://xml.openoffice.org">project homepage</a>.
+  </answer>
+ </faq>
+
+ <!-- faq template 
+ <faq>
+  <question>
+   ...
+  </question>
+  <answer>
+    ...
+  </answer>
+ </faq>
+ -->
+
+</faqs>

Propchange: incubator/ooo/ooo-site/trunk/content/xml/faq.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/faq.xsl
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/faq.xsl?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/faq.xsl (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/faq.xsl Sun Sep 25 19:43:42 2011
@@ -0,0 +1,110 @@
+<?xml version="1.0"?> 
+
+<!--
+    Transform FAQs into HTML.
+
+    Input XML is expected to look like this:
+
+    <faqs maintainer="...email..." maintainer-name="...name...">
+     <faq>
+      <question> ...? </question>
+      <answer> ... test with HTML ... </answer>
+     </faq>
+     <faq> ... </faq>
+     <faq> ... </faq>
+     <faq> ... </faq>
+    </faqs>
+-->
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
+
+    <xsl:output method="html" indent="no"/>
+
+    <!-- document root: list questions, then q+a -->
+    <xsl:template match="faqs">
+
+        <!-- header question list -->
+        <a name="top"/>
+        <p><img src="http://www.openoffice.org/sharedimages/start_blue_bar.gif" alt=""/>&#160;&#160;<font size="-1"><b>MOST FREQUENTLY ASKED QUESTIONS: QUESTIONS</b></font>&#160;&#160;<img src="http://www.openoffice.org/sharedimages/end_blue_bar.gif" alt=""/></p>
+
+        <!-- list of questions -->
+        <ol>
+            <xsl:apply-templates mode="list"/>
+        </ol>
+
+        <!-- header answers -->
+        <p><img src="http://www.openoffice.org/sharedimages/start_blue_bar.gif" alt=""/>&#160;&#160;<font size="-1"><b>MOST FREQUENTLY ASKED QUESTIONS: ANSWERS</b></font>&#160;&#160;<img  src="http://www.openoffice.org/sharedimages/end_blue_bar.gif" alt=""/></p>
+
+        <!-- list of q+answers -->
+        <xsl:apply-templates/>
+
+        <xsl:if test="@maintainer">
+            <p><small>FAQ maintained by <a href="mailto:{@maintainer}">
+                <xsl:choose>
+                    <xsl:when test="@maintainer-name">
+                        <xsl:value-of select="@maintainer-name"/>
+                    </xsl:when>
+                    <xsl:otherwise>
+                        <xsl:value-of select="@maintainer"/>
+                    </xsl:otherwise>
+                </xsl:choose>
+            </a>.</small></p>
+        </xsl:if>
+
+    </xsl:template>
+
+
+
+    <!-- FAQ element (list mode) -->
+    <!-- <li><a href="#1">...</a></li> -->
+    <xsl:template mode="list" match="faq">
+        <li><a href="#{1+count(preceding::faq)}"><xsl:apply-templates select="question"/></a></li>
+    </xsl:template>
+
+    <!-- FAQ element (question + answer) -->
+    <!-- <ol>
+            <a name="1"></a>
+            <li value ="1">
+                <b>...?</b>
+                <p> ... </p>
+                <br/><br/>
+            </li>
+        </ol>
+        <a href="main_faq_new.html">Back to main question page</a><br/>
+        <a href="#top">Back to top</a>
+        <HR ALIGN=left SIZE="1" NOSHADE> 
+        <br/>
+    -->
+    <xsl:template match="faq">
+        <ol>
+            <a name="{1+count(preceding::faq)}"/>
+            <li value="{1+count(preceding::faq)}">
+                <b> <xsl:apply-templates select="question"/> </b>
+                <xsl:choose>
+                    <xsl:when test="answer/p">
+                        <xsl:apply-templates select="answer" mode="copy"/>
+                    </xsl:when>
+                    <xsl:otherwise>
+                        <p>
+                            <xsl:apply-templates select="answer" mode="copy"/>
+                        </p>
+                    </xsl:otherwise>
+                </xsl:choose>
+                <br/>
+            </li>
+        </ol>
+
+        <a href="#top">Back to top</a>
+        <hr align="left" size="1" noshade="noshade"/> 
+        <br/>
+    </xsl:template>
+
+
+    <!-- copy mode copies all content -->
+    <xsl:template mode="copy" match="@*|node()">
+        <xsl:copy>
+            <xsl:apply-templates mode="copy" select="@*|node()"/>
+        </xsl:copy>
+    </xsl:template>
+
+</xsl:stylesheet>

Propchange: incubator/ooo/ooo-site/trunk/content/xml/faq.xsl
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/filters.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/filters.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/filters.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/filters.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,9 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+<p>This page is outdated. A list of <a href="http://wiki.services.openoffice.org/wiki/Xml/Filters">XML based OpenOffice.org filters</a> is available in the <a href="http://wiki.services.openoffice.org/wiki/Xml/Filters">Wiki</a>.
+</body>
+</html>
+

Propchange: incubator/ooo/ooo-site/trunk/content/xml/filters.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/general.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/general.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/general.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/general.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,149 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<h1>OpenOffice.org XML File Format</h1>
+<h2>File Format Specification and General Information</h2>
+
+<p><em><b>Note:</b>The information provided on this page is related to the OpenOffice.org XML file format used by OpenOffice.org 1.0 only. Please visit the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS OpenDocument Technical Committee web pages</a> for information regarding the OASIS OpenDocument file format used by OpenOffice.org 2.0.</em></p>
+<h3>Mission</h3>
+    <a name="mission"></a>     
+<p align="justify"> Our mission is to create an open and ubiquitous XML-based 
+ file format for office documents and to provide an open reference implementation 
+ for this format. </p>
+<h4> Core Requirements <small>(these items are absolutely required)</small>
+    </h4>
+        
+<ol>
+     <li> The file format must be capable of being used as an office program's
+  native file format.  The format must be "non-lossy" and must support (at
+ least) the full capability of a StarOffice/OpenOffice document.  The format
+ is likely to be used for document interchange but that use alone is not
+enough.    </li>
+     <li> Structured content should make use of XML's structuring capabilities 
+ and be represented in terms of XML elements and attributes. </li>
+     <li> The file format must be fully documented and have no "secret" features. 
+   </li>
+     <li> OpenOffice must be the reference implementation for this file format. 
+   </li>
+        
+</ol>
+        
+<h4> Core Goals <small>(these items are highly desired)</small> </h4>
+        
+<ol>
+     <li> The file format should be developed in such a way that it will
+be  accepted by the community and can be placed under community control for
+future  development and format evolution. </li>
+     <li> The file formats should be suitable for all office types: text
+processing,   spreadsheet, presentation, drawing, charting, and math. </li>
+     <li> The file formats should reuse portions of each other as much as 
+possible  (so for example a spreadsheet table definition can work also as 
+a text processing  table definition). </li>
+        
+</ol>
+
+<h3>OASIS File Format Standardization</h3>
+
+<p>XML file formats allow users to regain ownership to his/her own
+data, by allowing access and manipulation of office documents by
+arbitrary tools which support the file format. To make such capability
+ubiquitous, we believe it is necessary to standardize file
+formats. Thus, we have contributed the OpenOffice.org XML File
+Format to <a href="http://www.oasis-open.org/">OASIS</a>. The further development of the format now takes place in the <a
+href="http://www.oasis-open.org/committees/office/">OASIS OpenDocument
+Technical Committee</a>.</p>
+        
+
+<h3>General Information on the XML File Format</h3>
+
+<p>The definition of the XML File Format has been developed through
+OpenOffice.org. The resulting reference material, such as the specification and
+DTD may be downloaded here:</p>
+
+<table class="infotable">
+ <thead>
+  <tr>
+   <td colspan="3">OpenOffice.org XML File Format Specification</td>
+  </tr>
+  <tr>
+   <th>Document</th>
+   <th>Summary</th>
+   <th>Format</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td><a href="xml_specification.pdf">XML File Format Specification</a></td>
+   <td>This documents defines the XML file format used OpenOffice.org. It
+   serves as reference for the format.</td>
+   <td>PDF, ca.&nbsp;1.5MB</td>
+  </tr>
+  <tr>
+   <td><a href="/source/browse/xml/xmloff/dtd/">XML File Format DTD</a></td>
+   <td>The document type definition provides a handy reference against which
+   all OpenOffice.org XML files can be validated against.</td>
+   <td>text, ca.&nbsp;200KB</td>
+  </tr>
+ </tbody>
+</table>
+
+<p>Some supplementary information and resources on the OpenOffice.org XML File
+Format are available as well:</p>
+
+<table class="infotable">
+ <thead>
+  <tr>
+   <td colspan="3">General Information on the Format</td>
+  </tr>
+  <tr>
+   <th>Document</th>
+   <th>Summary</th>
+   <th>Format</th>
+  </tr>
+ </thead>
+ <tbody>
+  <tr>
+   <td><a href="faq.html">xmloff FAQ</a></td>
+   <td>The FAQ list some frequently asked question, together with answers from
+   the xmloff development team.</td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="xml_advocacy.html">XML Advantages</a></td>
+   <td>This page explains our motivation for using an XML based file
+   format. It lists advantages of our new file format, and discusses how these
+   will benefit different groups of users.</td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="package.html">Package Format Rationale</a></td>
+   <td>This document explains the rationale behind the ZIP-based package
+   format. The decision was made after an elaborate discussion on the XML dev
+   mailing list, whose <a href="http://xml.openoffice.org/xml-dev/">
+   archive</a> can be consulted for additional detail.</td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="filters.html">XML-based filters</a></td>
+   <td><p>Filters and transformations making use of the OpenDocument or OpenOffice.org XML File Formats.</p></td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="uses.html">Uses and Applications</a></td>
+   <td><p>Information on how to make use of the OASIS OpenDocument and OpenOffice.org XML File Format 
+ outside of the OpenOffice.org application.</p></td>
+   <td>HTML</td>
+  </tr>
+  <tr>
+   <td><a href="research.html">Resources</a></td>
+   <td><p>Books, articles, reports and research documents covering the OpenDocument and OpenOffice.org XML file formats.</p></td>
+   <td>HTML</td>
+  </tr>
+ </tbody>
+</table>
+</body>
+</html>
+

Propchange: incubator/ooo/ooo-site/trunk/content/xml/general.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/index.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/index.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/index.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/index.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,94 @@
+<html><head>
+<title>XML Project</title>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<!-- no current top news!
+<h2><strong>Top News</str
+ong>: <a href="xml_specification_draft.pdf">XML File Format Specification Updated</a></h2>
+-->
+<h1>The OpenOffice.org <strong>XML</strong> Project</h1>               
+<p>Lead: <a href="mailto:Michael.Brauer [AT]sun.com">Michael Brauer</a><br>
+Co-Lead: <a href="mailto:Svante.Schubert [AT]sun.com">Svante Schubert</a><br>
+<small>(Please use the provided <a href="/servlets/ProjectMailingListList">mailing lists</a> for discussion related to this project.</small>
+</p>
+
+<p>The OpenOffice.org <strong>XML project</strong> is the home of of XML related features of <a href="http://download.openoffice.org/">OpenOffice.org</a>, 
+like its <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OASIS OpenDocument</a>/<a href="http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43485">ISO/IEC 26300</a> file format implementation. It further provides some XML base implementations,
+like XML parser and printer components.</p>
+
+<p>The following sub-projects are within the scope of the XML project:</p>
+<ul>
+<li><p>The <a href="#ODF">OASIS OpenDocument/ISO/IEC 26300 file format</a> implementation, and the implementation of its predecessor, <a href="#OOo-XML">OpenOffice.org XML</a>.</p>
+<li><p>The <a href="#filter">framework for XML based filters</a>.</p>
+<li><p><a href="#xforms">XForms</a>.</p>
+<li><p><a href="#security">XML Security</a>.</p>
+<li><p><a href="#parser">XML Parser and Writer</a>.</p>
+</ul>
+<p>Please follow above links to get more information about these sub projects.</p>
+The XML project is one of the <a href="http://projects.openoffice.org/accepted.html">accepted projects</a> of <a href="http://www.openoffice.org">OpenOffice.org</a>.</p>
+<p>Please visit the <a href="http://wiki.services.openoffice.org/wiki/Xml">XML project's wiki pages</a> for
+more information about the project.</p>
+
+<h2>Contributing to the XML Project</h2>
+<p>If you are interested in contributing to this project, please don't hesitate to contact us at <a href="http://xml.openoffice.org/servlets/ProjectMailingListList">dev@xml.openoffice.org</a>. 
+If you are looking for <a href="http://wiki.services.openoffice.org/wiki/Xml#Contribution_Areas">ideas</a> what you may contribute, please visit the <a href="http://wiki.services.openoffice.org/wiki/Xml">project's wiki</a>.
+
+
+<h2 id="ODF">OASIS OpenDocument/ISO/IEC 26300 File Format (ODF)</h2>
+<p>The OpenOffice.org application uses the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OpenDocument file format</a> (also known as ODF) as 
+native file format. This means, OpenOffice.org stores all documents in 
+OpenDocument file format unless the user requests to store them in a 
+different file format.</p>
+<p><a href="http://opendocument.xml.org""><img align=right border=0 width=315 src="opendocument-cropped_0.jpg" /></a>The OpenDocument file format is developed by a <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">technical committee</a> at <a href="http://www.oasis-open.org">OASIS</a>. 
+It further is an approved and published ISO standard (<a href="http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43485">ISO/IEC 26300:2006</a>). The <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OpenDocument specification</a> is available at the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS OpenDocument TC's web page</a>. See
+<a href="http://opendocument.xml.org">opendocument.xml.org</a> for more information on 
+OpenDocument.</p>
+<p>Several members of the OpenOffice.org XML project and other OpenOffice.org 
+projects are <a href="http://www.oasis-open.org/committees/membership.php?wg_abbrev=office">members</a> of the OASIS OpenDocument technical committee, and 
+collaborate there with members from other projects and vendors on the further 
+development of the OpenDocument file format.</p>
+<p>The XML project maintains the implementation of the OpenDocument file format 
+in OpenOffice.org in very close collaboration and with large support of other 
+OpenOffice.org projects, in particular the 
+<a href="http://framework.openoffice.org/">application framework</a>, 
+<a href="http://graphics.openoffice.org/">graphical application</a>, 
+<a href="http://sc.openoffice.org">spreadsheet</a> and 
+<a href="http://sw.openoffice.org/">word processing</a> 
+projects.</p>
+
+<h2 id="OOo-XML">OpenOffice.org XML File Format</h2>
+<p>The <a href="general.html">OpenOffice.org XML file format</a> is the native 
+file format of OpenOffice.org 1.0. It has been replaced by the 
+<a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OASIS OpenDocument file format</a>
+ in OpenOffice.org 2.0.</p>
+
+<h2 id="filter">XML-Based Filters</h2>
+<p>The XML project contains the framework for the <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">XML based filters</a>. More
+information about the development of XML based filters is available in the <a href="filter">XML Based Filter Tutorial</a>.
+A <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">list of XML based filters</a> available for OpenOffice.org is available <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">in the wiki</a>.
+
+<h2 id="xforms">XForms</h2>
+<p>The XML project maintains the base technology of 
+OpenOffice.org's XForms feature, and cares about specifications in that area 
+in collaboration with the <a href="http://sw.openoffice.org/">word processing</a>
+and <a href="http://dba.openoffice.org/">database</a> projects. The Writer specific parts of the 
+XForms feature is maintained by the <a href="http://sw.openoffice.org/">word processing</a>
+project.</p>
+
+<h2 id="security">XML Security</h2>
+<p>In collaboration with the 
+<a href="http://framework.openoffice.org/">application framework</a> project, the 
+XML projects specifies and implements XML Security features of OpenOffice.org, 
+like digital signatures. 
+
+<h2 id="parser">XML Basis Implementations</h2>
+Being an important client of XML parser and writer implementations, the 
+XML project maintains these components in collaboration with the <a href="http://framework.openoffice.org/">application framwork</a> project project. 
+
+
+</body>
+</html>
+

Propchange: incubator/ooo/ooo-site/trunk/content/xml/index.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/index2.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/index2.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/index2.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/index2.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,93 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<!-- no current top news!
+<h2><strong>Top News</str
+ong>: <a href="xml_specification_draft.pdf">XML File Format Specification Updated</a></h2>
+-->
+<h1>The OpenOffice.org <strong>XML</strong> Project</h1>               
+<p>Lead: <a href="mailto:Michael.Brauer@sun.com">Michael Brauer</a><br>
+Co-Lead: <a href="mailto:Svante.Schubert@sun.com">Svante Schubert</a><br>
+<small>(Please use the provided <a href="/servlets/ProjectMailingListList">mailing lists</a> for discussion related to this project.</small>
+</p>
+
+<p>The OpenOffice.org <strong>XML project</strong> is the home of of XML related features of <a href="http://download.openoffice.org/">OpenOffice.org</a>, 
+like its <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OASIS OpenDocument</a>/<a href="http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43485">ISO/IEC 26300</a> file format implementation. It further provides some XML base implementations,
+like XML parser and printer components.</p>
+
+<p>The following sub-projects are within the scope of the XML project:</p>
+<ul>
+<li><p>The <a href="#ODF">OASIS OpenDocument/ISO/IEC 26300 file format</a> implementation, and the implementation of its predecessor, <a href="#OOo-XML">OpenOffice.org XML</a>.</p>
+<li><p>The <a href="#filter">framework for XML based filters</a>.</p>
+<li><p><a href="#xforms">XForms</a>.</p>
+<li><p><a href="#security">XML Security</a>.</p>
+<li><p><a href="#parser">XML Parser and Writer</a>.</p>
+</ul>
+<p>Please follow above links to get more information about these sub projects.</p>
+The XML project is one of the <a href="http://projects.openoffice.org/accepted.html">accepted projects</a> of <a href="http://www.openoffice.org">OpenOffice.org</a>.</p>
+<p>Please visit the <a href="http://wiki.services.openoffice.org/wiki/Xml">XML project's wiki pages</a> for
+more information about the project.</p>
+
+<h2>Contributing to the XML Project</h2>
+<p>If you are interested in contributing to this project, please don't hesitate to contact us at <a href="http://xml.openoffice.org/servlets/ProjectMailingListList">dev@xml.openoffice.org</a>. 
+If you are looking for <a href="http://wiki.services.openoffice.org/wiki/Xml#Contribution_Areas">ideas</a> what you may contribute, please visit the <a href="http://wiki.services.openoffice.org/wiki/Xml">project's wiki</a>.
+
+
+<h2 id="ODF">OASIS OpenDocument/ISO/IEC 26300 File Format</h2>
+<p>The OpenOffice.org application uses the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OpenDocument file format</a> as 
+native file format. This means, OpenOffice.org stores all documents in 
+OpenDocument file format unless the user requests to store them in a 
+different file format.</p>
+<p>The OpenDocument file format is developed by a <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">technical committee</a> at <a href="http://www.oasis-open.org">OASIS</a>. 
+It further is an approved and published ISO standard (<a href="http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=43485">ISO/IEC 26300:2006</a>). The <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OpenDocument specification</a> is available at the <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office">OASIS OpenDocument TC's web page</a>. See
+<a href="opendocument.xml.org">opendocument.xml.org</a> for more information on 
+OpenDocument.</p>
+<p>Several members of the OpenOffice.org XML project and other OpenOffice.org 
+projects are <a href="http://www.oasis-open.org/committees/membership.php?wg_abbrev=office">members</a> of the OASIS OpenDocument technical committee, and 
+collaborate there with members from other projects and vendors on the further 
+development of the OpenDocument file format.</p>
+<p>The XML project maintains the implementation of the OpenDocument file format 
+in OpenOffice.org in very close collaboration and with large support of other 
+OpenOffice.org projects, in particular the 
+<a href="http://framework.openoffice.org/">application framework</a>, 
+<a href="http://graphics.openoffice.org/">graphical application</a>, 
+<a href="http://sc.openoffice.org">spreadsheet</a> and 
+<a href="http://sw.openoffice.org/">word processing</a> 
+projects.</p>
+
+<h2 id="OOo-XML">OpenOffice.org XML File Format</h2>
+<p>The <a href="general.html">OpenOffice.org XML file format</a> is the native 
+file format of OpenOffice.org 1.0. It has been replaced by the 
+<a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office#technical">OASIS OpenDocument file format</a>
+ in OpenOffice.org 2.0.</p>
+
+<h2 id="filter">XML-Based Filters</h2>
+<p>The XML project contains the framework for the <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">XML based filters</a>. More
+information about the development of XML based filters is available in the <a href="filter">XML Based Filter Tutorial</a>.
+A <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">list of XML based filters</a> available for OpenOffice.org is available <a href="http://wiki.services.openoffice.org/wiki/Xml#Filters_and_Conversions_based_on_OpenDocument.2FOpenOffice.org_XML">in the wiki</a>.
+
+<h2 id="xforms">XForms</h2>
+<p>The XML project maintains the base technology of 
+OpenOffice.org's XForms feature, and cares about specifications in that area 
+in collaboration with the <a href="http://sw.openoffice.org/">word processing</a>
+and <a href="http://dba.openoffice.org/">database</a> projects. The Writer specific parts of the 
+XForms feature is maintained by the <a href="http://sw.openoffice.org/">word processing</a>
+project.</p>
+
+<h2 id="security">XML Security</h2>
+<p>In collaboration with the 
+<a href="http://framework.openoffice.org/">application framework</a> project, the 
+XML projects specifies and implements XML Security features of OpenOffice.org, 
+like digital signatures. 
+
+<h2 id="parser">XML Basis Implementations</h2>
+Being an important client of XML parser and writer implementations, the 
+XML project maintains these components in collaboration with the <a href="http://framework.openoffice.org/">application framwork</a> project project. 
+
+
+</body>
+</html>
+

Propchange: incubator/ooo/ooo-site/trunk/content/xml/index2.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/ooo/ooo-site/trunk/content/xml/index2.html
------------------------------------------------------------------------------
    svn:executable = *

Added: incubator/ooo/ooo-site/trunk/content/xml/modules.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/modules.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/modules.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/modules.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,10 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<p>This page is outdated. A list of <a href="http://wiki.services.openoffice.org/wiki/Xml/Modules">Source Code Modules in the OpenOffice.org XML Project</a> is available in the <a href="http://wiki.services.openoffice.org/wiki/Xml/Modules">Wiki</a>.
+</body>
+</html>
+

Propchange: incubator/ooo/ooo-site/trunk/content/xml/modules.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/opendocument-cropped_0.jpg
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/opendocument-cropped_0.jpg?rev=1175554&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/ooo/ooo-site/trunk/content/xml/opendocument-cropped_0.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Added: incubator/ooo/ooo-site/trunk/content/xml/package.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/package.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/package.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/package.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,804 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+<HEAD>
+	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+	<TITLE></TITLE>
+	<META NAME="GENERATOR" CONTENT="StarOffice 6.0  (Win32)">
+	<META NAME="CREATED" CONTENT="20010801;20531125">
+	<META NAME="CHANGEDBY" CONTENT="Daniel Vogelheim">
+	<META NAME="CHANGED" CONTENT="20010801;20534064">
+</HEAD>
+<BODY>
+<H1>XML Packages</H1>
+<H2>Purpose of this document</H2>
+<P>At the end of September, I (<I>dvo</I>) have asked the
+openoffice.org community for help on the problem of embedding binary
+content in XML documents. This page is intended to summarize the
+discussion and provide a solid foundation that will guide our
+implementation efforts. 
+</P>
+<P>We will first restate the problem. Then follows a summary of the
+requirements that have been stated in the <A HREF="http://www.openoffice.org/www-discuss/">discuss</A>
+and <A HREF="http://xml.openoffice.org/xml-dev/">xml-dev</A> mailing
+lists. The candidate solutions mentioned on the mailing lists are
+then examined in light of these requirements. Finally, a conclusion
+is presented. 
+</P>
+<H3>A few definitions</H3>
+<P>To clarify the following discussion, a definition of a few terms
+for use within this document may be in order: 
+</P>
+<DL>
+	<DT STYLE="margin-bottom: 0.5cm">document 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	A document comprises everything a user considers to part of his
+	text, spreadsheet or presentation. In general this will include
+	several images or OLE objects in addition to the main content. 
+	</DD><DD STYLE="margin-bottom: 0.5cm">
+	If images are linked into the document, they are not considered part
+	of it. Whether an image is linked or embedded into the document is
+	determined by the user. Due to limitations in the current OLE
+	handling, OLE objects must always be embedded. 
+	</DD><DT STYLE="margin-bottom: 0.5cm">
+	file 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	A file is a sequence of bytes as stored in the operating system's
+	file system. This fairly obvious definition serves to distinguish
+	between the logical view (the document) and the physical view (the
+	file). 
+	</DD><DT STYLE="margin-bottom: 0.5cm">
+	<EM>b</EM>inary <EM>l</EM>arge <EM>ob</EM>ject, BLOB 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	A BLOB contains binary data that has no structured content that
+	could reasonably be encoded as XML data. Usually, BLOBs will be data
+	in established binary formats such as GIF, JPEG, or OLE data
+	streams. 
+	</DD><DT STYLE="margin-bottom: 0.5cm">
+	subdocument 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	A subdocument refers to an individual component of the document.
+	Each binary large object (BLOB) is one subdocument, as is the main
+	document content encoded as XML. 
+	</DD><DT STYLE="margin-bottom: 0.5cm">
+	main document content 
+	</DT><DD STYLE="margin-bottom: 0.5cm">
+	The main document content refers to the subdocument that best
+	represents the document as a whole. For example, if an OpenOffice
+	Writer document consists of an XML subdocument containing the text
+	body, and several image subdocument, then the XML subdocument would
+	form the main document content. 
+	</DD></DL>
+<H2>
+The Problem</H2>
+<P>OpenOffice and the next generation of StarOffice by default use an
+XML based file format (but the user may choose to save in a different
+format). Therefore this project differs from many others, as this is
+an XML based file format intended to be truly a format for the
+masses. The requirements for a native file format are different
+(usually more demanding) than those for an interchange format. 
+</P>
+<P>XML is meant for structured content and has no native support for
+binary objects (BLOBs) such as images, OLE objects or other media
+types. Since embedding of binary objects is needed for office
+documents, a way to handle XML and binary data in the same document
+must be provided. 
+</P>
+<P>One solution may be to simply store the XML data in a file and
+link to image data in separate files, much like in HTML documents.
+While linking files at the user's request should be possible, this is
+in general not considered adequate for office documents. A document
+should be stored in a single file to make external handling of the
+document (e.g. copying the document) possible. Therefore, binary
+content must be stored in the same file as the XML content, requiring
+either a <EM>package</EM> format or a means to encode binary content
+in XML. For the sake of simplicity, we will refer to all solutions
+that store XML and BLOB data in a single file as packages. 
+</P>
+<H2>The Requirements</H2>
+<P>The following requirements have been identified for the package
+format: 
+</P>
+<H3>A. Efficient Operation</H3>
+<P>Users have traditionally required efficient operation, especially
+for basic functionality such as loading or saving of documents. It is
+our experience that independent loading (or saving) of subdocuments
+is the key to efficient handling of large documents. Additionally,
+users require that disk space is used efficiently. This leads us to
+require the document format to support: 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">small file sizes 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">on-demand loading (i.e.,
+	independent loading of subdocuments) 
+	</P>
+	<LI><P>independent saving of subdocuments 
+	</P>
+</OL>
+<P>These requirements are strongly supported by ten years of
+experience at StarOffice. Failing to meet these requirements has
+repeatedly resulted in dissatisfaction and significant protests from
+the user base. 
+</P>
+<P><B>Note</B> on independent saving of subdocuments: Previous
+versions of StarOffice have gotten significant benefit from copying
+subdocuments on the file system level rather than reading and then
+writing subdocuments through the <A HREF="http://ucb.openoffice.org/">UCB</A>.
+This should be supported by the package format. Saving modified
+subdocuments into an existing (compound) document may provide further
+benefits. 
+</P>
+<H3>B. Compatibility with Existing Tools</H3>
+<P>A primary motivation for creating an XML based file format is the
+ability to process, create and manipulate StarOffice documents with
+external tools. To deserve the label &quot;open&quot; document
+format, these tools should be standard and widely available. As far
+as possible, this should apply to both, the document and the
+individual subdocuments (if applicable). In particular, the main
+document content (using XML) should be accessible to standard XML
+tools. 
+</P>
+<P>This leads us to state three subrequirements: 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">Subdocuments should be usable with
+	standard tools. In particular, XML subdocuments should be usable
+	with standard XML tools, e.g. XSLT transformations. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The document should be accessible
+	with standard tools, making it possible to insert, modify and
+	extract subdocuments, e.g. similar to zip or other popular
+	archivers. 
+	</P>
+	<LI><P>The document should be accessible with ASCII-based tools,
+	e.g. the Windows file find function. 
+	</P>
+</OL>
+<P><B>Note:</B> During discussion on openoffice.org mailing lists
+several people preferred requirement number 1 to be extended to the
+complete document. This would essentially require the document format
+to be XML as well, with subdocuments (including BLOBS) being embedded
+within the XML structure. 
+</P>
+<P><B>Note:</B> Since XML is based on Unicode, ASCII based tools
+cannot generally be assumed to work on XML files. Thus, no solution
+will be able to fully support the third requirement. If UTF-8
+encoding is used, ASCII-based tools will work at least for those
+languages that can be properly represented in ASCII, like English or
+Latin. 
+</P>
+<P><B>Note:</B> Compression interferes with some of the requirements
+above. The discussion on the mailing list has clearly proven that
+those requirements are very important to some users. To support these
+users, 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">compression should be made
+	optional, and 
+	</P>
+	<LI><P>an additional implementation that writes pure XML (and saves
+	binary data into separate files) should be created. 
+	</P>
+</OL>
+<P>Formats supporting compression on a per subdocument basis would
+have an additional advantage in this respect. Also, this would allow
+a subdocument with e.g. meta information (title, keywords, etc.) to
+be stored uncompressed, making it more easily accessible. 
+</P>
+<H3>C. Security</H3>
+<P>An additional advantage that may be gained through the use of a
+package is easy support for document security. We can distinguish
+between two security considerations: 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">privacy: be able to encrypt
+	(partial) documents 
+	</P>
+	<LI><P>integrity: be able to verify origin of (partial) documents 
+	</P>
+</OL>
+<P><B>Note:</B> These requirements are of fairly low priority. 
+</P>
+<H3>D. Additional Issues</H3>
+<OL>
+	<LI><P>A package structure supporting documents and subdocuments
+	makes it easy to add additional information to a document, even if
+	the reference implementation does not understand it. For example, in
+	situations where a certain transformation is used very often, the
+	transformation result may be stored in the package as well. 
+	</P>
+	<LI><P>The current implementation is based on the SAX API. XML
+	filters (transformations) also using the SAX API can be pipelined,
+	e.g. they can import (or export) data into (or from) OpenOffice by
+	going directly through the API, rather than going through a file. 
+	</P>
+</OL>
+<H2>The Contenders</H2>
+<P>On the openoffice.org mailing lists, the following possible
+solutions were suggested: 
+</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">ZIP or JAR files 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">XML with binary data being
+	ASCII-encoded within special tags (e.g. base64) 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">MIME files 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">.tgz files 
+	</P>
+	<LI><P>BONOBO libefs 
+	</P>
+</OL>
+<P><B>Note:</B> The participants quickly focused on two choices: JAR
+and XML 
+</P>
+<P><B>Note:</B> ZIP and JAR files are identical for most intents and
+purposes. JAR differs from the older ZIP in the file ending, as well
+as in additional meta information stored in a directory called
+META-INF. JAR files can be accessed using unmodified ZIP tools. 
+</P>
+<H2>Examination of the contenders</H2>
+<P>This chapter gives an overview of how well the various contenders
+met the specified requirements. It was my (<I>dvo</I>) impression
+that most people would agree on the suitability of the various
+contenders for the various requirements. The disagreement was mainly
+between the importance of the requirements. 
+</P>
+<P>In particular one group valued accessibility with XML tools (B1)
+very high and consequently would speak for XML with base64 encoding,
+while most others would prefer ZIP/JAR. 
+</P>
+<H3>ZIP / JAR</H3>
+<P>Tools to create and manipulate ZIP files are widely available on
+all platforms. The manifest file used with JAR files is usually
+considered optional and may even be created using a text editor.
+Access to subdocuments requires unzipping the required subdocuments
+first. ASCII based tools will in general not work on the package,
+although (at the user's request) individual subdocuments could be
+stored uncompressed, thus making them available to ASCII based tools.</P>
+<P>Since ZIP files have an index, efficient on-demand loading of
+subdocuments can be achieved. Subdocuments can be copied from one
+package to another without uncompressing and compressing them first.
+With some hackery for on-demand saving, only those files following
+the newly-written subdocuments need to be written. Due to (optional)
+compression, files can be small, although not quite as small as .tgz
+files. 
+</P>
+<P><B>Note:</B> As requested on the mailing list, the JAR manifest
+file should be replaced by an XML-based manifest file. The older JAR
+manifest may be supported for compatibility reasons. This is to be
+determined. 
+</P>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>ZIP / JAR</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<H3>XML + base64</H3>
+<P>This suggestion is to use plain XML documents and embed binary
+content as base64 encoded ASCII in special elements. 
+</P>
+<P>Tools to generate or manipulate subdocuments in this format are
+not commonly available, but could be written with reasonable effort.
+Usability of the main document content with XML tools is, of course,
+excellent. ASCII based tools should work with no problems (except for
+the already mentioned UTF encodings). 
+</P>
+<P>Without an index, on-demand loading is not possible, neither is
+on-demand saving. Files are not compressed and binary subdocuments
+are even expand by 33% due to the base64 encoding. 
+</P>
+<P><B>Note:</B> In the discussion lists, several remedies to allow
+on-demand reading were suggested. Either the inclusion of indices in
+the XML file, or placing the binary data at the end of the file. The
+former was considered to be non-XML (as it relies on the physical
+layout of the XML data) and useless, since any standard XML tool
+would not update the index and thus OpenOffice couldn't rely on it.
+The latter can not be done with standard (e.g. SAX-based) parsers, as
+they are used in the current implementation. The SAX API is necessary
+for the filter pipelining mentioned in the requirements section, so
+forgoing SAX may have significant drawbacks. 
+</P>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>XML + base64</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<H3>MIME</H3>
+<P>MIME is the established packaging format for emails. As is
+required for SMTP compatibility, it is ASCII-based (7bit ASCII).
+Non-Mailer tools to manipulate MIME files are rare. 
+</P>
+<P>Being an ASCII based format, accessibility to ASCII based tools is
+excellent. However, the encoding of non-ASCII characters is solved
+differently than in XML. Tools to manipulate MIME files (outside of
+mail programs) are not readily available, but could be written with
+reasonable effort. Access with XML tools requires unpacking first,
+but as said before the tools to do so are not currently available. 
+</P>
+<P>MIME has no index of subdocuments, making on-demand loading
+difficult. For saving of individual subdocuments, a reasoning similar
+to ZIP files applies. However, copying subdocuments requires
+accessing them, which is slow on MIME due to the lack of an index.
+Since no compression is used, files get fairly large. In addition,
+binary documents are usually encoded in base64, enlarging them by
+33%. 
+</P>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII 
+				</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>MIME</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<H3>.tgz</H3>
+<P>The .tgz format (tar files compressed with gzip) is the most
+popular archiving format on the UNIX platform. Tools to manipulate
+.tgz files exist on most other platforms as well. As participants on
+the mailing lists mentioned, it is used as package format for
+KOffice. 
+</P>
+<P>.tgz operates according to the compress-after-packaging principle.
+in general, this results in very good compression ratios. However,
+the same principle causes on-demand loading of subdocument to be
+severely inefficient: Not only is it impossible to quickly determine
+the start position of subdocuments, it is also impossible to start
+reading subdocuments once the start position is known because the
+state of the uncompression tables cannot easily be reconstructed. For
+the same reason, changing a subdocument or even copying subdocuments
+is inefficient. 
+</P>
+<P>Availability of tools for manipulating .tgz files is good, and
+even very good on UNIX platforms. Accessibility to subdocuments
+requires unpacking the subdocuments first, which is slow because the
+document must be uncompressed from the start. 
+</P>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>.tgz</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<H3>Comparison Table</H3>
+<CENTER>
+	<TABLE BORDER=1 CELLPADDING=2 CELLSPACING=2>
+		<TR>
+			<TD></TD>
+			<TH COLSPAN=3>
+				<P>Efficiency</P>
+			</TH>
+			<TH COLSPAN=3>
+				<P>Standard Tools</P>
+			</TH>
+		</TR>
+		<TR>
+			<TD></TD>
+			<TH>
+				<P>size</P>
+			</TH>
+			<TH>
+				<P>load</P>
+			</TH>
+			<TH>
+				<P>save</P>
+			</TH>
+			<TH>
+				<P>XML</P>
+			</TH>
+			<TH>
+				<P>document</P>
+			</TH>
+			<TH>
+				<P>ASCII [6]</P>
+			</TH>
+		</TR>
+		<TR>
+			<TH>
+				<P>ZIP / JAR</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [1]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [2]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [2]</P>
+			</TD>
+		</TR>
+		<TR>
+			<TH>
+				<P>XML + base64</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>- [3]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [4]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+		</TR>
+		<TR>
+			<TH>
+				<P>MIME</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>-</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>- [1]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>- [2]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [4]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+</P>
+			</TD>
+		</TR>
+		<TR>
+			<TH>
+				<P>.tgz</P>
+			</TH>
+			<TD>
+				<P ALIGN=CENTER>++</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>--</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [2]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>+ [5]</P>
+			</TD>
+			<TD>
+				<P ALIGN=CENTER>0 [2]</P>
+			</TD>
+		</TR>
+	</TABLE>
+</CENTER>
+<P ALIGN=CENTER>++&nbsp;=&nbsp;very good, +&nbsp;=&nbsp;good,
+0&nbsp;=&nbsp;medium, -&nbsp;=&nbsp;bad, --&nbsp;=&nbsp;very bad</P>
+<P>Remarks:</P>
+<OL>
+	<LI><P STYLE="margin-bottom: 0cm">Copying subdocuments is possible.
+	With some hackery, (repeated) partial updates can be supported. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Requires unpackaging (or
+	package-aware tools), so score depends on availability of tools and
+	their efficiency 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">On-demand loading may be
+	implemented at the expense of being unable to use standard XML
+	parser APIs (e.g. SAX). 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Tools can be written with
+	reasonable effort but don't currently exist; at least not on many
+	platforms. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">Very good on Unix, good on other
+	platforms. 
+	</P>
+	<LI><P>Due to XML being Unicode-based, ASCII-based tools probably
+	don't work in many circumstances, independent of the document
+	format. 
+	</P>
+</OL>
+<H3>libefs 
+</H3>
+<P>Additionally, the BONOBO libefs was suggested. Since this was not
+much discussed in the mailing lists, I (<I>dvo</I>) tried to find out
+about libefs from the web. This was my impression: 
+</P>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">libefs was created to solve a
+	problem very similar to ours. It is designed to be an ambitious
+	file-system-in-a-file solution. If it works out the way its
+	developers imagine, it will be technically superior to the other
+	proposals discussed here. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The page didn't mention any ports,
+	thus making it a UNIX solution only. This prohibits its use in a
+	cross-platform application like OpenOffice. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">No external tools to manipulate
+	libefs files exist. 
+	</P>
+	<LI><P STYLE="margin-bottom: 0cm">The page I consulted referred to
+	it as &quot;very much a work-in-progress&quot;, meaning that
+	currently it is not suitable for a consumer product. 
+	</P>
+	<LI><P>The libefs documentation was a bit unclear on the
+	relationship between libefs API and libefs implementation (meaning:
+	file format(s)). If it is mainly an API, it would compete with the
+	current <A HREF="http://ucb.openoffice.org/">UCB</A> architecture. 
+	</P>
+</UL>
+<H3>Security</H3>
+<P>Documents could of course be encrypted for all candidate formats.
+All formats could encrypt subdocuments as well, except for
+XML+base64, which would make it impossible to encrypt the main
+document content without encrypting the binaries as well. In .tgz,
+subdocument encryption could adversely affect compression, since the
+entire file is compressed at once. 
+</P>
+<P>The same applies to file integrity verification. JAR is very
+appealing in this regard, as it has already the full infrastructure
+for subdocument and document integrity verification in place. 
+</P>
+<H2>The Conclusion</H2>
+<P>The JAR file format seems to provide the best balance among the
+stated requirements. Unlike all other formats, it does not have any
+real weakness in regard to any of the requirements, and quite a lot
+of advantages. 
+</P>
+<P>If one values accessibility with standard XML tools very high, XML
++ base64 seems a logical choice. While this is one of the
+requirements for OpenOffice, the xmloff development team does not
+follow the opinion that this single requirement significantly exceeds
+all other requirements in importance. To accommodate this user base,
+an additional pure XML file format with external subdocuments should
+be created. 
+</P>
+<H3>Remaining Issues</H3>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Decide on meta information and
+	manifest file format. 
+	</P>
+	<LI><P>Implement a UCB that allows pure XML documents. 
+	</P>
+</UL>
+<H3>Further Reading</H3>
+<UL>
+	<LI><P STYLE="margin-bottom: 0cm">Most of these topics have been
+	discussed in detail on the openoffice.org <A HREF="http://www.openoffice.org/www-discuss/">discuss</A>
+	and <A HREF="http://xml.openoffice.org/xml-dev/">xml-dev</A> mailing
+	lists. The archives should provide more information. 
+	</P>
+	<LI><P>Details of ZIP and many other file formats are described on
+	<A HREF="http://www.wotsit.org/">www.wotsit.org</A>. 
+	</P>
+</UL>
+<HR>
+<P><FONT SIZE=2>The <A HREF="http://xml.openoffice.org/">xmloff</A>
+development team <BR>Summarized by <A HREF="mailto:dvo@openoffice.org">dvo</A>
+</FONT>
+</P>
+</BODY>
+</HTML>

Propchange: incubator/ooo/ooo-site/trunk/content/xml/package.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/project_tools.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/project_tools.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/project_tools.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/project_tools.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,46 @@
+<!-- Note:  You don't have to fill in the name of your project
+with ONE exception:
+you must specify the project name for the Version control link. -->
+
+<div class="label"><strong>Project tools</strong></div>
+<div class="body">
+  <div> <a href="/servlets/ProjectHome">Project home</a> </div>
+  <div> <a href="/servlets/ProjectMemberList">Membership</a> </div>
+</div>
+<div class="body">
+  <div> <a href="/servlets/ProjectNewsList">Announcements</a> </div>
+ <!-- #if ($isLoggedIn && !$loginUser.isAnonymous())
+  <div><a href="/servlets/ProjectForumView">Discussion forums</a></div>
+  #end -->
+  <div> <a href="/servlets/ProjectMailingListList">Mailing lists</a> </div>
+</div>
+<div class="body">
+  <div> <a href="/servlets/ProjectDocumentList">Documents &amp; files</a> </div>
+  <div><a href="/source/browse/xml">Version control</a> </div>
+</div>
+<div class="body">
+  <div> <a href="/servlets/ProjectIssues">Issue tracker</a> </div>
+ <!-- #if ($isLoggedIn && !$loginUser.isAnonymous())
+  <div><a href="http://qa.openoffice.org/issues/buglist.cgi?cmdtype=runuserdefault">My issues</a></div>
+  #end </div> -->
+<!--Other links should just be added using <div>...</div>, with regular expressions, eg., <div>about-downloads.html</div>, to link to http://[projectname].openoffice.org/about-downloads.html, which is in the project/www/ directory.  To link to, say, http://[projectname].openoffice.org/information/index.html, use <div>/information/index.html</div>. 
+
+Thus:
+
+<div>file.html</div>
+<div>/directory/file.html</div>
+
+-->
+
+
+</div>
+<div class="label"><strong><a href="http://wiki.services.openoffice.org/wiki/Xml">Wiki</a></strong></div>
+<div class="body">
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Efforts">Current Efforts</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/ContributionAreas">Contributions</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/ArticlesAndBooks">Articles and Books</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Research">Reports and Research</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Tools">Tools</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Filters">Filters</a> </div>
+  <div><a href="http://wiki.services.openoffice.org/wiki/Xml/Modules">Modules</a> </div>
+</div>

Propchange: incubator/ooo/ooo-site/trunk/content/xml/project_tools.html
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: incubator/ooo/ooo-site/trunk/content/xml/project_tools.html
------------------------------------------------------------------------------
    svn:executable = *

Added: incubator/ooo/ooo-site/trunk/content/xml/research.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/research.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/research.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/research.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,10 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+
+<p>This page is outdated. A list of <a href="http://wiki.services.openoffice.org/wiki/Xml/Research">Reports and Research Documents covering the OpenDocument format</a> is available in the <a href="http://wiki.services.openoffice.org/wiki/Xml/Research">Wiki</a>.
+</body>
+</html>
+

Propchange: incubator/ooo/ooo-site/trunk/content/xml/research.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/robots.txt
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/robots.txt?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/robots.txt (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/robots.txt Sun Sep 25 19:43:42 2011
@@ -0,0 +1,7 @@
+User-Agent: *
+Disallow: /source/
+Disallow: /issues/
+Disallow: /search/
+Disallow: /servlets/
+Disallow: /project/
+Disallow: /nonav/

Propchange: incubator/ooo/ooo-site/trunk/content/xml/robots.txt
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ooo/ooo-site/trunk/content/xml/uses.html
URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/xml/uses.html?rev=1175554&view=auto
==============================================================================
--- incubator/ooo/ooo-site/trunk/content/xml/uses.html (added)
+++ incubator/ooo/ooo-site/trunk/content/xml/uses.html Sun Sep 25 19:43:42 2011
@@ -0,0 +1,9 @@
+<html><head>
+<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8">
+</head>
+<body>
+<link rel="stylesheet" type="text/css" href="xmloff.css" media="screen" />
+<p>This page is outdated. A list of <a href="http://wiki.services.openoffice.org/wiki/Xml/Tools">OpenDocument related tools</a> is available in the <a href="http://wiki.services.openoffice.org/wiki/Xml/Tools">Wiki</a>.
+</body>
+</html>
+

Propchange: incubator/ooo/ooo-site/trunk/content/xml/uses.html
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message