[e-cvs] cvs commit: e/domains/small/smallstd-org/smallschema index.html
markm@eros.cs.jhu.edu
markm@eros.cs.jhu.edu
Sun, 1 Jul 2001 17:43:33 -0400
markm 01/07/01 17:43:32
Modified: domains/small/smallstd-org index.html
domains/small/smallstd-org/smallschema index.html
Log:
changed case
Revision Changes Path
1.7 +25 -25 e/domains/small/smallstd-org/index.html
Index: index.html
===================================================================
RCS file: /cvs/e/domains/small/smallstd-org/index.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.html 2001/02/20 18:30:45 1.6
+++ index.html 2001/07/01 21:43:32 1.7
@@ -29,7 +29,7 @@
<TD ALIGN="RIGHT">
<!-- #BeginEditable "BigTitle" --><FONT SIZE="7"><b><font size="5">Welcome
to<br>
- <font size="7">smallStd.org</font></font></b></FONT><!-- #EndEditable -->
+ <font size="7">SmallStd.org</font></font></b></FONT><!-- #EndEditable -->
</TD>
</TR>
</TABLE>
@@ -46,27 +46,27 @@
this latter kind of compatibility. Is there a way out of this dilemma?
</p>
<p align="left">Inspired by <a href="http://www.docuverse.com/smldev/index.html">Minimal-XML</a>,
- the <i>small*</i> standards will leverage the power of<i> </i>Downward
+ the <i>Small*</i> standards will leverage the power of<i> </i>Downward
Compatibility. Each standard will be developed at its own website, with
- smallStd.org as the coordination site among the others. Each <i>small*</i>
+ SmallStd.org as the coordination site among the others. Each <i>Small*</i>
standard will remove enough from an existing standard to get simple, will
leave enough to be useful <i>for some purposes</i> (typically fewer than
the original), but will remain fully downwards compatible from the full
- standard. As a result, anything correctly expressed in the <i>small*</i>
+ standard. As a result, anything correctly expressed in the <i>Small*</i>
version of the standard is, <i>and can claim to be</i>, compatible with
- the full standard. The <i>small*</i> standards are the intersection of
+ the full standard. The <i>Small*</i> standards are the intersection of
these above two kinds of compatibility -- with conventional standards,
and with the needs of reliability and security. </p>
<p align="left">Standards need names, and the easiest way to claim name
space is to occupy the corresponding domain names. Towards this end, I've
- grabbed a bunch of small*.{com,org} domain names which I have put up <a href="http://www.caplet.com/domains.html">for
+ grabbed a bunch of Small*.{com,org} domain names which I have put up <a href="http://www.caplet.com/domains.html">for
sale</a> at high prices, but with deep discounts for those that would
use the name for it's intended purpose -- to define and promote the corresponding
- <i>small*</i> standard. In the meantime, I will proceed slowly to use
+ <i>Small*</i> standard. In the meantime, I will proceed slowly to use
each site to explain what I have in mind for each standard.</p>
- <p align="left">Ideally, each of the <i>small*</i>.org domain names should
+ <p align="left">Ideally, each of the <i>Small*</i>.org domain names should
get transfered to a standards organization that gets the point. If we're
- wildly successful, smallStd.org may eventually be the anti-w3c.</p>
+ wildly successful, SmallStd.org may eventually be the anti-w3c.</p>
<table border="1" cellpadding="6">
<tr>
<th>Base Name</th>
@@ -78,7 +78,7 @@
<td>com</td>
<td>org</td>
<td>A simple schema language for <a href="http://www.docuverse.com/smldev/index.html">Minimal-XML</a>.
- Intended to be identical to smallSchema.</td>
+ Intended to be identical to SmallSchema.</td>
</tr>
<tr>
<td>Minimal-XML</td>
@@ -88,63 +88,63 @@
according to the consensus of SML-DEV.</td>
</tr>
<tr>
- <td>smallDOM</td>
+ <td>SmallDOM</td>
<td>com</td>
<td>org</td>
- <td>A simple DOM tree for smallML</td>
+ <td>A simple DOM tree for SmallML</td>
</tr>
<tr>
- <td>smallHTTP</td>
+ <td>SmallHTTP</td>
<td>com</td>
<td>org</td>
<td>A simple subset of HTTP, adequate for simple browsers to talk to
simple servers</td>
</tr>
<tr>
- <td>smallIDL</td>
+ <td>SmallIDL</td>
<td>com</td>
<td>org</td>
<td>A simple subset of <a href="http://www.corba.org">Corba IDL</a>
and <a href="http://www.capidl.org">CapIDL</a></td>
</tr>
<tr>
- <td>smallJ</td>
+ <td>SmallJ</td>
<td>com</td>
<td>org</td>
<td>A simple and capability secure subset of Java</td>
</tr>
<tr>
- <td>smallML</td>
+ <td>SmallML</td>
<td>com</td>
<td>org</td>
<td>A slight subset of <a href="http://www.docuverse.com/smldev/index.html">Minimal-XML</a>,
- with the addition of validity rules in terms of smallSchema</td>
+ with the addition of validity rules in terms of SmallSchema</td>
</tr>
<tr>
- <td>smallPath</td>
+ <td>SmallPath</td>
<td>com</td>
<td>org</td>
- <td>A simple subset of XPath for use with smallML</td>
+ <td>A simple subset of XPath for use with SmallML</td>
</tr>
<tr>
- <td><a href="smallschema/index.html">smallSchema</a></td>
+ <td><a href="smallschema/index.html">SmallSchema</a></td>
<td>com</td>
<td>org</td>
- <td>Not a subset of XML Schema. Rather, a Schema for smallML able to
+ <td>Not a subset of XML Schema. Rather, a Schema for SmallML able to
generate a subset of standard DTDs. Intended to be identical to Minimal-Schema.</td>
</tr>
<tr>
- <td>smallStd</td>
+ <td>SmallStd</td>
<td>com</td>
<td><a href="http://www.smallstd.org/">org</a></td>
- <td>The coordination point for these small* standards.</td>
+ <td>The coordination point for these Small* standards.</td>
</tr>
<tr>
- <td>smallVM</td>
+ <td>SmallVM</td>
<td>com</td>
<td>org</td>
<td>A simple and capability secure subset of the Java Virtual Machine
- (JVM), able to support smallJ.</td>
+ (JVM), able to support SmallJ.</td>
</tr>
</table>
<!-- #EndEditable --></TD>
1.3 +16 -16 e/domains/small/smallstd-org/smallschema/index.html
Index: index.html
===================================================================
RCS file: /cvs/e/domains/small/smallstd-org/smallschema/index.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.html 2001/02/19 22:59:49 1.2
+++ index.html 2001/07/01 21:43:32 1.3
@@ -27,46 +27,46 @@
<TR>
<TD ALIGN="LEFT"><a href="../index.html"><img src="../images/lgmarb3.gif" width="26" height="26" align="absmiddle" border="0"></a></TD>
<TD ALIGN="RIGHT"> <!-- #BeginEditable "BigTitle" -->
- <p><FONT SIZE="7"><B>smallSchema<br>
+ <p><FONT SIZE="7"><B>SmallSchema<br>
<font size="5">Draft Proposals</font></B></FONT></p>
<!-- #EndEditable --> </TD>
</TR>
</TABLE>
<hr>
<!-- #BeginEditable "LongBody" -->
- <P ALIGN="left">The requirements for smallSchema:
+ <P ALIGN="left">The requirements for SmallSchema:
<ul>
<li>
- <p>A smallSchema must represent information that would be contained
+ <p>A SmallSchema must represent information that would be contained
in a standard XML DTD for representing validity constraints over
Minimal-XML data. Not every possible such DTD must be representable
- in smallSchema, but the set of DTDs covered should be adequate for
+ in SmallSchema, but the set of DTDs covered should be adequate for
SML-DEV consensus. </p>
</li>
<li>
- <p>Any valid smallSchema must automatically translate to a standard
+ <p>Any valid SmallSchema must automatically translate to a standard
XML DTD. </p>
</li>
<li>
- <p>Given only reasonable effort writing the smallSchema, the resulting
+ <p>Given only reasonable effort writing the SmallSchema, the resulting
DTD must be readable and documented.</p>
</li>
<li>
- <p>A Minimal-XML document is valid according to a smallSchema <i>exactly</i>
- when it's valid according to the DTD generated from that smallSchema.
- Therefore, an adequate validity check is to translate the smallSchema
+ <p>A Minimal-XML document is valid according to a SmallSchema <i>exactly</i>
+ when it's valid according to the DTD generated from that SmallSchema.
+ Therefore, an adequate validity check is to translate the SmallSchema
to a DTD and validate the document against the DTD.</p>
</li>
<li>
- <p>The smallSchema may contain information not present in the generated
- DTD. In particular, smallSchema repairs a major hole in DTDs: the
+ <p>The SmallSchema may contain information not present in the generated
+ DTD. In particular, SmallSchema repairs a major hole in DTDs: the
need to associate names with positional arguments of Elements. This
- should aid conversion of data from one smallSchema to another, as
+ should aid conversion of data from one SmallSchema to another, as
is familiar from the object-serialization class-evolution problem.</p>
</li>
<li>
- <p>A smallSchema itself must be written in Minimal-XML and be valid
- according to the smallSchema describing smallSchemas.</p>
+ <p>A SmallSchema itself must be written in Minimal-XML and be valid
+ according to the SmallSchema describing SmallSchemas.</p>
</li>
</ul>
@@ -80,7 +80,7 @@
</tr>
<tr>
<td><a href="../src/org/smallschema/smallschema-schema-0.1-regex.xml">smallschema-schema-0.1-regex.xml</a></td>
- <td>Validity constraints for smallSchema definitions, including itself.</td>
+ <td>Validity constraints for SmallSchema definitions, including itself.</td>
</tr>
<tr>
<td><a href="http://www.erights.org/elang/kernel/kernel-e-0.8.9e.dtd">kernel-e-0.8.9e.dtd</a></td>
@@ -90,7 +90,7 @@
<tr>
<td><a href="../src/org/smallschema/kernel-e-schema.xml">kernel-e-schema.xml</a></td>
<td>A partial hand-rewrite of the above DTD in Minimal-XML conforming
- to smallSchema.</td>
+ to SmallSchema.</td>
</tr>
</table>
<P ALIGN="left">The <i>regex</i> proposal isn't as minimal as I'd like,