thinking

Hello Wyonacms-users,

(I have lose original letter, and write again (much more) :) )

Idea is to have differents "edition" of WyonaCMS.

For example "light" "standard" "professional".


[ PREAMBULE ]================================================

With internet works different people - they solve different tasks.
There is "low" task, there is "high" task.
"Low" mean "simple" but this not mean "not need".

XML+XSLT - is the future of web, it's unambiguously.

And users want to use advantages of XML technologies for their tasks.
And users have different resources (computer, internet access, knowledge).


"Light" task:
- genetate static html site from XML content with
  automatic generation navigation (menu),
- not "high" design site, not "high" content manage.
Resources:
- local computer (low performance),
- dealup internet,
- access to free hosting,
- know: XML+XSLT, or not.
- don't know Java, Tomcat setting, Cocoon2 settings, SQL, SVG ...


"Standard" task:
- offline site generation,
- use advantage SVG to have "high" desigh,
- use advantage of SQL Database to manage content site (use XML-DB,
  XIndice, f.e.)
- i.e. "high" design site - designer, "high" site content manage -
  programmer
Resources:
- local computer (medium performance),
- dealup or direct internet,
- access to free or paying hosting.
- know: XML+XSLT, Java not high, SQL, SVG, Cocoon setting, XSP
- don't know all other :)


"Professional" task:
- on-line site,
- roles, users ...
- all power now's wyonaCMS.
Resources:
- computer (high preformance) in intranet with Java+Tomcat, or on
  hosting with Java+Tomcat,
- direct internet (or not, for intranet using)
- access to Hosting with Java+Tomcat
- know: Java "high", all technologies.


[ SOLVING ]================================================

And according to this tasks - to make WyonaCMS "editions".
Different "editions" are destinationed to differents user-layers.

This "tasks" cover different percentage of internet-users (who want to
take advantage of XML). I think about 80% (light) 15% (standard) 5%
(professional). Of cause it is rough estimate.

I.e. WyonaCMS now cover 5% of potential users.
It possible to compare wyonaCMS-now to high flying aircraft, but many
people walking on earth :)

"Editions" have in mind that user from "light edition" in future time
may go to "standard", from "standard" to "professional".

(I have paint 2 images about "light" version -
 http://www.nemilya.narod.ru/wyona/ or
 http://www.nemilya.by.ru/wyona/)

[ PS ]==============

possible to write XML for "editions":

<edition type="light">
  <task-list>
    <task name="offline site generation"/>
  </task-list>
  <user-knowledge-list>
    <user-knowledge id="html" percentage="50%"/>
    <user-knowledge id="xslt" percentage="50%"/>
  </user-knowledge-list>
</edition>

...

Also possible to write knowledge-list, covering all technologies, which
are using in WyonaCMS, (and make from this teaching resource, where user
may see what technologies is in the Internet world):

<knowledge-list>
  <knowledge id="xslt" type="specification">
    <description>XSL Transformation needed for...</description>
    <link-list>
      <link href="http://www.w3.org/TR/xslt" descr="W3C XSL Transformations (XSLT) Version 1.0"/>
    </link-list>
    <relation-list>
      <relation link="Xalan"/>
    <relation-list>
  </knowledge>

  <knowledge id="svg" type="specification">
    <description>Scalagle Vector Graphic needed for ...</description>
    <link-list>
      <link href="http://www.w3.org/TR/SVG/" descr="Scalable Vector Graphics (SVG) 1.0 Specification"/>
    </link-list>
    <relation-list>
      <relation link="Batik"/>
    <relation-list>
  </knowledge>

  <knowledge id="Java" type="language">
    <description>Java ...</description>
    <link-list>
      <link href="http://www.sun.com/java/" descr="..."/>
    </link-list>
  </knowledge>

  <knowledge id="servlet" type="word %)">
    <description>Servlet is ...</description>
    <link-list>...</link-list>
    <relation-list>
      <relation link="Servlet specification"/>
      <relation link="Cocoon"/>
    <relation-list>
  </knowledge>

  <knowledge id="servlet container" type="word %)">
    <description>Servlet container needed for ...</description>
    <link-list>...</link-list>
    <relation-list>
      <relation link="Java"/>
      <relation link="Tomcat"/>
    <relation-list>
  </knowledge>

  <knowledge id="Tomcat" type="program">
    <description>Tomcat is ...</description>
    <link-list>...</link-list>
    <relation-list>
      <relation link="servlet container"/>
    <relation-list>
  </knowledge>

  <knowledge id="FOP" type="word %)">
    <description>FOP ...</description>
    <link-list>...</link-list>
    <relation-list>
      <relation link="FOP specification"/>
      <relation link="Apache FOP"/>
    <relation-list>
  </knowledge>


  ...

</knowledge-list>

I.e. <link-list> - what is about in web.
And <relation-list> - relation inside <knowledge-list>.

For example "XML acronyms for Java developers":
http://www.javaworld.com/javaworld/jw-09-2002/jw-0927-xmlglossary.html

(may by needed to have "parent"-"child" relations,
like "Servlet container" -> "Servlet" -> "Java program" ...).

Or generally (in ideal) write this in RDF
(
  "Tomcat" -[implement]->"Servlet container"-[run]->"Servlet"
  "Cocoon"-[implement]->"Servlet"
          -[working on]->"Servelt container"
  "Servlet"-[are]->"Java byte code"
  "Java byte code"-[executed by]->"JVM"
  "JVM"-[there are]->"Sun"
       -[there are]->"IBM"

  this is only my estimates, in reality I don't know RDF :))
)

All this I imagine right now - comment (if are) welcome.

This (knowledge-list) is another project, but I think it will be very
useful to understand what WyonaCMS is, and how WyonaCMS work.


Regards,
Ilya