stefano 00/06/06 16:21:04
Modified: xdocs Tag: xml-cocoon2 docs-book.xml index.xml
Log:
cleaned up a little
Revision Changes Path
No revision
No revision
1.4.2.3 +1 -1 xml-cocoon/xdocs/docs-book.xml
Index: docs-book.xml
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/docs-book.xml,v
retrieving revision 1.4.2.2
retrieving revision 1.4.2.3
diff -u -r1.4.2.2 -r1.4.2.3
--- docs-book.xml 2000/05/26 15:16:27 1.4.2.2
+++ docs-book.xml 2000/06/06 23:21:00 1.4.2.3
@@ -13,5 +13,5 @@
<todo id="todo" label="Todo" source="todo.xml"/>
<separator/>
<external label="Mail Archive" href="http://xml-archive.webweaving.org"/>
- <external label="Bug Database" href="http://xml.apache.org/bugs/"/>
+ <!-- <external label="Bug Database" href="http://xml.apache.org/bugs/"/>
-->
</book>
1.3.2.2 +9 -157 xml-cocoon/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-cocoon/xdocs/index.xml,v
retrieving revision 1.3.2.1
retrieving revision 1.3.2.2
diff -u -r1.3.2.1 -r1.3.2.2
--- index.xml 2000/03/20 21:51:09 1.3.2.1
+++ index.xml 2000/06/06 23:21:00 1.3.2.2
@@ -4,7 +4,7 @@
<document>
<header>
- <title>Cocoon</title>
+ <title>Cocoon2</title>
<subtitle>XML Publishing Framework</subtitle>
<authors>
<person name="Stefano Mazzocchi" email="[EMAIL PROTECTED]"/>
@@ -15,170 +15,22 @@
<s1 title="What is it?">
<p>
- <img src="images/cocoon2.gif" alt="Cocoon"/> Cocoon is a 100% pure
- Java publishing framework that relies on new W3C
- technologies (such as DOM, XML, and XSL) to provide web content.
+ Cocoon2 is a complete rewrite of the Cocoon XML publishing framework that
+ is supposed to remove all those design constraint that emerged from the
+ Cocoo1 experience.
</p>
<p>
- The Cocoon project aims to change the way web information is created,
- rendered and served. This new paradigm is based on fact that document
content, style and
- logic are often created by different individuals or working groups.
Cocoon aims to a
- complete separation of the three layers, allowing the three layers to be
independently
- designed, created and managed, reducing management overhead, increasing
work reuse and
- reducing time to market.
+ This documentation is alpha, like anything else, so don't expect
+ that much. If you are not a developer and you are not willing to test
+ new stuff that may not work as expected, we suggest you to refer to the
latest
+ Cocoon1 release which is very stable.
</p>
<p>
- Read the <connect href="technologies.xml">Introduction on Cocoon
- technologies</connect> white paper to find out more on the subject.
+ Otherwise, if you are brave enough, we welcome you into this new world of
XML wonders :-)
</p>
</s1>
- <s1 title="What does it do?">
- <p>
- Web content generation is mostly based on HTML, but HTML doesn't separate
- the information from its presentation, mixing formatting tags,
descriptive tags and
- programmable logic (both on server side and client side). Cocoon changes
this view
- allowing content, logic and style on different XML files and uses XSL
transformation
- capabilities to merge them.
- </p>
- </s1>
-
- <s1 title="What does it change for me?">
- <p>
- Even if the most common use of Cocoon is the automatic creation of HTML
- through the processing of statically or dynamically generated XML files,
Cocoon is also
- able to perform more sophisticated formatting, such as XSL:FO rendering
on PDF,
- client-depending transformations such as WML formatting for WAP-enabled
- devices or direct XML serving to XML and XSL aware clients.
- </p>
-
- <p>
- The Cocoon model allows web sites to be highly structured and
- well designed, reducing duplication efforts and site management costs by
- allowing different presentations of the same data depending on the
requesting
- client (HTML clients, PDF clients, WML clients) and separating on
different <em>contexts</em>
- different requirements, skills and capacities. Cocoon allows a better
human
- resource management by giving to each individual its job and reducing to a
- minimum the cross-talks between different working contexts.
- </p>
-
- <p>
- To do this, the Cocoon model divides the development of web content in
three
- separate levels:
- </p>
-
- <dl>
- <dt>XML creation</dt>
- <dd>the XML file is created by the <em>content owners</em>. They do not
- require specific knowledge on how the XML content is further processed
rather than the
- particular chosen DTD/namespace. This layer is always performed by
humans directly
- through normal text editors or XML-aware tools/editors.</dd>
- <dt>XML processing</dt>
- <dd>the requested XML file is processed and the logic contained in its
- logicsheet is applied. Unlike other dynamic content generators, the
logic
- is separated from the content file.</dd>
- <dt>XSL rendering</dt>
- <dd>the created document is then rendered by applying an XSL
- stylesheet to it and formatting it to the specified resource type
- (HTML, PDF, XML, WML, XHTML)</dd>
- </dl>
- </s1>
-
- <s1 title="Are there any known problems?">
- <p>
- The biggest known problem in this framework is the lack of XML/XSL
- knowledge, being relatively new formats. We do believe, though, that this
publishing
- framework will be a winner in web sites of medium to high complexity and
will lead the
- transition from an HTML-oriented to a XML-oriented web publishing model,
still allowing the
- use of existing client technologies as well as supporting new types of
clients
- (such as WAP-aware ultra thin clients like cell phones or PDAs).
- </p>
- <p>
- Even if considered heavy and hype overloaded, the XML/XSL pair will do
- magic once its public knowledge receives the spread it deserves. This
project wants to be
- a small step in this direction, helping people to learn this technology
and to focus on
- what they need with examples, tutorial and source code and a real-life
system
- carefully designed with portability, modularity and real-life usage in
- mind.
- </p>
- <p>
- The main concern remains processing complexity: the kind of operations
required
- to process the document layers are complex and not designed for real-time
- operation on the server side. For this reason, Cocoon is designed to be a
page compiler for dynamic pages,
- trying to hardcode, whenever possible, those layers in precompiled binary
- code coupled with an adaptive and memory-wise cache system for both
static and
- dynamic pages. Most of the development effort is focused on performance
- improvement of both processing subsystems as well as the creation and
testing
- of special cache systems.
- </p>
- <p>
- Another problem is the intrinsic impossibility of page-compiling all the
three
- processing layers, due to the post-processing requirements of XSL
styling. This
- problem will be solved (hopefully!) with the availability of XSL-enabled
- web browsers since the XSL rendering would be then
- performed on client side reducing the server work.
- </p>
- </s1>
-
- <s1 title="Where do I get it?">
- <p>
- Here is the <link href="http://xml.apache.org/dist/";>download area</link>.
- </p>
- <note>
- Since Cocoon requires many different packages to work (Xerces, Xalan,
FOP, etc...)
- but sometimes there are small incompatibilities between them that make the
- installation harder, we decided to help you by placing all the required
- binary libraries inside the Cocoon distribution. So, after you
- downloaded the latest Cocoon distribution, <strong>you don't need
anything else</strong>.
- </note>
- </s1>
-
- <s1 title="How do I Contribute?">
- <p>
- The Cocoon Project is an open volunteer project based on the spirit of the
- <link href="http://www.apache.org";>Apache Software Foundation</link>
(ASF).
- This means that there are lots of ways to contribute to the project,
either
- with direct participation (coding, documenting, answering questions,
- proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by
resource
- donation (money, time, publicity, hardware, software, conference
- presentations, speeches, etc...).
- </p>
- <p>
- For direct participation, we suggest you to subscribe to the
- <link href="http://xml.apache.org/mail.html";>Cocoon mail lists</link>
- (follow the link for information on how to subscribe and to access the
mail
- list archives), to checkout the <link
href="http://xml.apache.org/websrc/cvsweb.cgi/xml-cocoon/";>
- latest and greatest code</link> (which you found in the xml-cocoon module
in
- the xml.apache.org CVS code repository, or from the
- <link href="http://xml.apache.org/from-cvs/xml-cocoon/";>CVS
snapshots</link>),
- control the <connect href="../todo.xml">todo</connect>
- list and jump in. Document writers are usually the most wanted people so
if
- you like to help but you're not familiar with technical details, don't
worry:
- we have work for you.
- </p>
- <p>
- For money funding in particular, the Cocoon Project and the ASF in general
- is closely collaborating with the <link
href="http://www.sourcexchange.com";>Collab.net
- SourceXchange</link> program that will provide a legal, solid and well
- established resource for money collecting to fund direct software
production
- under the open source flag. Please, feel free to contact directly Cocoon's
- main architect and project creator <link href="mailto:[EMAIL
PROTECTED]">Stefano
- Mazzocchi</link> or the ASF President and Collab.net co-founder <link
href="mailto:[EMAIL PROTECTED]">Brian
- Behlendorf</link> for more information on how to contribute directly to
the
- advancement of this project.
- </p>
- <p>
- Anyway, a great way of contributing back to the project is to
- allow others to know about it so that the word spreads and others may
wish to
- contribute, so, please, help us by placing the cocoon logo somewhere in
your
- site to indicate that you are using and supporting the Cocoon Project.
- </p>
-
- <p>
- Thank you very much.
- </p>
- </s1>
</body>
</document>
