From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/projects
Date: Tuesday March 20, 19101 @ 12:23
Author: fen
CVSWEB Options: -------------------
Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi
View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/projects
-----------------------------------
Update of /usr/local/cvs/public/openprivacy/htdocs/projects
In directory giga:/home/fen/projects/openprivacy/htdocs/projects
Modified Files:
jewel.shtml
Log Message:
standard indentation
*****************************************************************
File: openprivacy/htdocs/projects/jewel.shtml
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/projects/jewel.shtml?annotate=1.21
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/projects/jewel.shtml?rev=1.21&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/projects/jewel.shtml.diff?r1=1.21&r2=1.20
-----------------------------------
Index: openprivacy/htdocs/projects/jewel.shtml
diff -u openprivacy/htdocs/projects/jewel.shtml:1.20 openprivacy/htdocs/projects/jewel.shtml:1.21
--- openprivacy/htdocs/projects/jewel.shtml:1.20 Tue Feb 6 16:03:37 2001
+++ openprivacy/htdocs/projects/jewel.shtml Tue Mar 20 12:23:41 2001
@@ -1,124 +1,121 @@
<!--#include virtual="/includes/top.html"-->
<!--#include virtual="/includes/navigation.html"-->
-<!-- $Id: jewel.shtml,v 1.20 2001/02/07 00:03:37 fen Exp $ -->
+<!-- $Id: jewel.shtml,v 1.21 2001/03/20 20:23:41 fen Exp $ -->
-<p>
+ <h3>Jewel -> DataStore</h3>
-<h3>Jewel -> DataStore</h3>
+ Jewel is the DataStore on which <a
+ href="/projects/reptile.shtml">Reptile</a> and <a
+ href="http://sierra.openprivacy.org/">Sierra</a> are based. Jewel is an
+ Open Source implementation and a standard set of APIs which many
+ OpenPrivacy based systems can run on. Jewel provides data storage, query
+ abstraction, and is architecture agnostic towards the underlying
+ persistence layer (could be SQL, XQL, OQL, or in-memory data structures).
-<p>
-Jewel is the DataStore on which <a
-href="/projects/jetspeek.shtml">JetsPeek</a> and
-<a href="http://sierra.openprivacy.org/">Sierra</a>
-are based. Jewel is an Open Source implementation and a standard set of
-APIs which many OpenPrivacy based systems can run on. Jewel provides data
-storage, query abstraction, and is architecture agnostic towards the
-underlying persistence layer (could be SQL, XQL, OQL, or in-memory data
-structures).
+ <h4>Query support</h4>
-<p>
+ Jewel supports a portable query mechanism (should map to SQL, OQL, XQL,
+ etc). It is based on the concept of a Query and Criteria object.
-<h4>Query support</h4>
+ <p align="center">
-<p>Jewel supports a portable query mechanism (should map to SQL, OQL, XQL,
-etc). It is based on the concept of a Query and Criteria object.
+ <img src="/notes/uml/query-mechanism.png">
-<p align="center">
+ </p>
+ <h4>XML Support</h4>
-<img src="/notes/uml/query-mechanism.png">
+ The following are requirements for Jewel. Some XML technologies are clearly
+ early and should be implemented in their current state.
-<h4>XML Support</h4>
-
-<p>
-The following are requirements for Jewel. Some XML technologies are clearly
-early and should be implemented in their current state.
-
-<ul>
-
+ <ul>
<li>
- XML Schema support:
- <a href="http://www.w3.org/TR/xmlschema-0">Primer</a>
-
- <a href="http://www.w3.org/TR/xmlschema-1">Structures</a>
- and
- <a href="http://www.w3.org/TR/xmlschema-2">Datatypes</a>
+ XML Schema support:
+ <a href="http://www.w3.org/TR/xmlschema-0" target="_new">Primer</a>
+ <a href="http://www.w3.org/TR/xmlschema-1" target="_new">Structures</a>
+ and
+ <a href="http://www.w3.org/TR/xmlschema-2" target="_new">Datatypes</a>
+ </li>
<li>
- Namespaces. All documents should correctly use namespaces
- <li>
- Requires <a href="http://www.w3.org/TR/xmldsig-core/">XML Signature</a> in
- order to communicate pseudonymously with other parts of the OpenPrivacy system.
-
-</ul>
+ Namespaces. All documents should correctly use namespaces
+ </li>
+ <li> Requires <a href="http://www.w3.org/TR/xmldsig-core/"
+ target="_new">XML Signature</a> in order to communicate pseudonymously
+ with other parts of the OpenPrivacy system.
+ </li>
+ </ul>
-<h4>Property Resolver</h4>
+ <h4>Property Resolver</h4>
+ <p>
-<p>
-In order to support multiple data representations and still work within
-OpenPrivacy (and not tie it to a specific backend technology) we need a way to
-map XML documents so that their data is exposed to all systems including legacy
-ones. The solution to this is the property resolver. Jewel maps "properties"
-(description) to XPath queries (XPath is very solid and there are plenty of
-engine implementations). These properties can then be used by any system (legacy
-and bleeding edge) without technical, scalable or speed compromises.
+ In order to support multiple data representations and still work within
+ OpenPrivacy (and not tie it to a specific backend technology) we need a way to
+ map XML documents so that their data is exposed to all systems including legacy
+ ones. The solution to this is the property resolver. Jewel maps "properties"
+ (description) to XPath queries (XPath is very solid and there are plenty of
+ engine implementations). These properties can then be used by any system (legacy
+ and bleeding edge) without technical, scalable or speed compromises.
-<p>
-Example:
+ </p><p>
-<pre>
+ Example:
- <property-resolver>
+ </p>
+ <pre>
- <property name="description" select="/rss/channel/description"/>
+ <property-resolver>
- </property-resolver>
+ <property name="description" select="/rss/channel/description"/>
-</pre>
+ </property-resolver>
-<p>
-The source document would have a <property-resolver uri=""/> element which
-would point to the above document. Jewel uses this to build property sets
-(tokenize) the XML document. The properties are used by the query engine to
-find instances of XML documents with match a request.
+ </pre>
-<h3>Record management</h3>
+ <p>
-<p align="center">
-<img src="/notes/uml/record-package.png">
+ The source document would have a <property-resolver uri=""/> element which
+ would point to the above document. Jewel uses this to build property sets
+ (tokenize) the XML document. The properties are used by the query engine to
+ find instances of XML documents with match a request.
+ </p>
+ <h3>Record management</h3>
-<h3>Technical</h3>
+ <p align="center">
+ <img src="/notes/uml/record-package.png">
+ </p>
-<p>
-<ul>
- <li>Written in Java (requires JDK 1.1 only)
+ <h3>Technical</h3>
+ <ul>
+ <li>Written in Java (requires JDK 1.1 only)
+ </li>
<li>Based on
- <a href="http://xml.apache.org/xerces-j/" target="_new">Apache
- Xerces</a>
-
+ <a href="http://xml.apache.org/xerces-j/" target="_new">Apache
+ Xerces</a>
+ </li>
<li>Data replication between Jewel nodes.
-
+ </li>
<li>Swapable persistence mechanism. Should support most databases and also
- newer technologies such as XQL.
-
-</ul>
-
-<p>
-<h3>References</h3>
+ newer technologies such as XQL.
+ </li>
+ </ul>
-<ul>
- <li><a href="http://java.apache.org/turbine/torque.html">Torque</a> will
- probably be some of the database abstraction within Jewel
+ <h3>References</h3>
+ <ul>
+ <li><a href="http://java.apache.org/turbine/torque.html"
+ target="_new">Torque</a> will probably be some of the database
+ abstraction within Jewel
+ </li>
+ </ul>
-</ul>
+ <p>
-<p>
-All of the above should have a flexible infrastructure. Components should
-be able to be removed and replaced with alternative objects that as long as
-implement an interface provided by
-<a href="http://java.apache.org/framework/" target="_new">Avalon</a>.
-</p>
+ All of the above should have a flexible infrastructure. Components should
+ be able to be removed and replaced with alternative objects that as long as
+ implement an interface provided by
+ <a href="http://java.apache.org/framework/" target="_new">Avalon</a>.
+ </p>
-<!--#include virtual="/includes/bottom.html"-->
+ <!--#include virtual="/includes/bottom.html"-->
This archive was generated by hypermail 2b30 : Tue Mar 20 2001 - 12:23:42 PST