Commit 72e41fe4 authored by Marco Antoniotti's avatar Marco Antoniotti 💬
Browse files

Updated formatting and corrected a few glitches in the HTML.

parent 60711035
<!-- index -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
<html><head>
<!DOCTYPE html PUBLIC
"-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd">
<html>
<head>
<title>
CDR - Common Lisp Document Repository
CDR - Common Lisp Document Repository
</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" charset="UTF-8">
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8"
charset="UTF-8">
<link rel="stylesheet" href="cdr.css">
</head>
<frameset rows="65px,*,65px" noresize="noresize">
</head>
<frameset rows="65px,*,65px" noresize="noresize">
<!-- HEADER ROW -->
<frame src="index_files/index-header.htm" frameborder="0">
<!-- NAVIGATION/CONTENT/SIDEBAR ROW -->
<frameset cols="15%,85%">
<!-- NAVIGATION FRAME -->
<frame src="index_files/index-navigation.htm" frameborder="0">
<!-- CONTENT #<DOC-FILE 2297EB93> -->
<frame src="index_files/introduction.htm" name="introduction_frame" frameborder="0" class="cdr_dict_entry">
<!-- FRAME introduction -->
<frame src="index_files/index-navigation.htm"
frameborder="0">
<!-- CONTENT -->
<frame src="index_files/introduction.htm"
name="introduction_frame"
frameborder="0"
class="cdr_dict_entry">
<!-- FRAME introduction -->
</frameset>
<!-- FOOTER ROW -->
<frame src="index_files/index-footer.htm" frameborder="0">
</frameset>
<noframes>
</frameset>
<noframes>
<h2>
Frame Alert
Frame Alert
</h2>
<p>
This document is designed to be viewed using the frames feature.
If you see this message, you are using a non-frame-capable web client.
<br />
Link to
<a href="overview-summary.html">
Non-frame version.
</a>
This document is designed to be viewed using the frames feature.
If you see this message, you are using a non-frame-capable web client.
<br />
<!-- Link to
<a href="overview-summary.html">
Non-frame version.
</a> -->
</p>
</noframes>
</noframes>
</html>
<!-- end of file : index.htm -->
\ No newline at end of file
<!-- end of file : index.htm -->
<!-- introduction.html -->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html><head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" charset="UTF-8">
<title>CDR - Common Lisp Document Repository</title>
<link rel="stylesheet" href="../cdr.css">
<!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<title>
CDR - Common Lisp Document Repository
</title>
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8"
charset="UTF-8" />
<link rel="stylesheet" href="../cdr.css" />
</head>
<body>
<h1><a name="What">What?</a></h1>
<p>The Common Lisp Document Repository is a repository of documents that are of interest to the Common Lisp community. The most important property of a CDR
document is that it will never change: if you refer to it, you can be sure that your reference will always refer to exactly the same document.
<p>
The Common Lisp Document Repository is a repository of
documents that are of interest to the Common Lisp community. The
most important property of a CDR document is that it will never
change: if you refer to it, you can be sure that your reference
will always refer to exactly the same document.
</p>
<h1><a name="Why?">Why?</a></h1>
<p>There have been a number of attempts to establish a standardization process for Common Lisp after it has been officially published as an ANSI standard.
The ANSI standardization was very costly and very time consuming (according to <a href="http://groups.google.com/group/comp.lang.lisp/msg/15248a1b11c5a603 " target="_blank">
http://groups.google.com/group/comp.lang.lisp/msg/15248a1b11c5a603 </a> it took nearly 10 years and at least $400K). The goal of the Common Lisp Document Repository is to be more
light-weight and more efficient. We focus on one aspect of standardization: the ability to refer to a specification document in an unambiguous way. The Common Lisp Document Repository
intentionally does not define a process for coming up with specifications or any other means to guarantee some level of quality of the submitted documents. Instead, we aim for a community-driven,
decentralized approach to come up, discuss and finalize specifications. In this sense, we only provide the services of librarians. We hope that the Common Lisp Document Repository has the potential
to prove useful in establishing new de-facto standards, and to serve as a stepping stone for more formal standardizations in the long run.
<p>
There have been a number of attempts to establish a
standardization process for Common Lisp after it has been
officially published as an ANSI standard. The ANSI
standardization was very costly and very time consuming (according
to <a href="http://groups.google.com/group/comp.lang.lisp/msg/15248a1b11c5a603"
target="_blank">
http://groups.google.com/group/comp.lang.lisp/msg/15248a1b11c5a603
</a>
it took nearly 10 years and at least $400K). The goal of the
Common Lisp Document Repository is to be more light-weight and
more efficient. We focus on one aspect of standardization: the
ability to refer to a specification document in an unambiguous
way. The Common Lisp Document Repository intentionally does not
define a process for coming up with specifications or any other
means to guarantee some level of quality of the submitted
documents. Instead, we aim for a community-driven, decentralized
approach to come up, discuss and finalize specifications. In this
sense, we only provide the services of librarians. We hope that
the Common Lisp Document Repository has the potential to prove
useful in establishing new de-facto standards, and to serve as a
stepping stone for more formal standardizations in the long run.
</p>
<h1><a name="Where">Where?</a></h1>
<p> The Common Lisp Document Repository is hosted at <a href="https://zenodo.org/communities/cdr/about/" target="_black"> Zenodo </a>
<p>
The Common Lisp Document Repository is hosted
at <a href="https://zenodo.org/communities/cdr/"
target="_black">Zenodo</a>.
</p>
<h1><a name="How">How?</a></h1>
<p>The Common Lisp Document Repository is a repository of printable text documents that contain material that are of interest to the Common Lisp community. For example, a CDR document can contain
specifications of libraries, language extensions, example implementations, test suites, articles, etc. Each CDR document will be identified by a number. Form and possible contents of CDR documents
are not prescribed, but the goal is to provide the Common Lisp community with a way to unambiguously refer to a document by way of mentioning its CDR number. The presence of a document in the CDR
repository does not imply a recommendation of any kind, but we leave the acceptance or rejection of particular documents to the community's natural selection process. We expect that some CDR documents
will claim to be replacements of, or clarifications for, previous ones, but again such statements do not mean that this repository's goal is to enforce such developments. We are just librarians who
want to make it possible to refer and cite documents of interest to Common Lispers.
We use a light-weight process that consists of the following steps:
<p>
The Common Lisp Document Repository is a repository of
printable text documents that contain material that are of
interest to the Common Lisp community. For example, a CDR document
can contain specifications of libraries, language extensions,
example implementations, test suites, articles, etc. Each CDR
document will be identified by a number. Form and possible
contents of CDR documents are not prescribed, but the goal is to
provide the Common Lisp community with a way to unambiguously
refer to a document by way of mentioning its CDR number. The
presence of a document in the CDR repository does not imply a
recommendation of any kind, but we leave the acceptance or
rejection of particular documents to the community's natural
selection process. We expect that some CDR documents will claim to
be replacements of, or clarifications for, previous ones, but
again such statements do not mean that this repository's goal is
to enforce such developments. We are just librarians who want
to make it possible to refer and cite documents of interest to
Common Lispers.
</p>
<p>
We use a light-weight process that consists of the following steps:
</p>
<ol>
<p>
<ol>
<li>One or more authors submit a document.
</li>
<li>We check that the document is a printable text document, that it is indeed about Common Lisp, and that it does not contain objectionable material (like porn, religious or political statements, etc.).
<li>We check that the document is a printable text document,
that it is indeed about Common Lisp, and that it does not
contain objectionable material (like porn, religious or
political statements, etc.).
</li>
<li>The document will be immediately assigned a fresh CDR number that can be used to refer to the document. We will make the document available for an initial period, after which it will be frozen and
moved into final status, unless the authors decide to withdraw the document during the initial period.
<li>The document will be immediately assigned a fresh CDR number
that can be used to refer to the document. We will make the
document available for an initial period, after which it will
be frozen and moved into final status, unless the authors
decide to withdraw the document during the initial period.
</li>
</ol>
<p>For more details about the process, see the CDR manual.
</p>
</ol>
</p>
<p>
For more details about the process, see the CDR manual.
</p>
<h1> <a name="Mailinglist">Mailing Lists</a></h1>
<h1><a name="Mailinglist">Mailing Lists</a></h1>
<ol>
<li><a href="https://mailman.common-lisp.net/listinfo/cdr-announce" target="_blank">cdr-announce</a> for announcements of new CDRs, etc
<p>
<ol>
<li><a href="https://mailman.common-lisp.net/listinfo/cdr-announce"
target="_blank">cdr-announce</a> for announcements of new
CDRs, etc.
</li>
<li><a href="https://mailman.common-lisp.net/listinfo/cdr-devel" target="_blank">cdr-devel</a> for discussions / questions about CDR.
<li><a href="https://mailman.common-lisp.net/listinfo/cdr-devel"
target="_blank">cdr-devel</a> for discussions / questions
about CDR.
</li>
<li><a href="https://mailman.common-lisp.net/listinfo/cdr-discuss" target="_blank">cdr-discuss</a> for discussions about specific CDRs.
<li><a href="https://mailman.common-lisp.net/listinfo/cdr-discuss"
target="_blank">cdr-discuss</a> for discussions about
specific CDRs.
</li>
</ol>
<!--
;;; Copyright (c) 2021 Marco Antoniotti, All rigths reserved.
;;;
;;; Permission to use, modify, and redistribute this code is hereby
;;; granted.
;;; The code is provided AS IS with NO warranty whatsoever. The author
;;; will not be held liable etc etc etc etc etc.
-->
</ol>
</p>
<!--
;;; Copyright (c) 2022 Marco Antoniotti, All rigths reserved.
;;;
;;; Permission to use, modify, and redistribute this code is hereby
;;; granted.
;;; The code is provided AS IS with NO warranty whatsoever. The author
;;; will not be held liable etc etc etc etc etc.
-->
</body></html>
<!-- end of file : introduction.html -->
\ No newline at end of file
</body>
</html>
<!-- end of file : introduction.html -->
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment