Commit ef25dda8 authored by Marco Antoniotti's avatar Marco Antoniotti 💬
Browse files

Fixed dangling web links.

parent 9a585a5f
Pipeline #5848 passed with stage
in 4 seconds
No preview for this file type
This diff is collapsed.
......@@ -8,7 +8,7 @@ The Common Lisp Document Repository is a repository of documents that are of int
* Why
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 http://groups.google.com/group/comp.lang.lisp/msg/15248a1b11c5a603 it took nearly 10 years and at least $400K).
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 https://groups.google.com/g/comp.lang.lisp/c/yIvSw-GVGlw/m/A6bFERuKJBUJ 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.
......@@ -95,7 +95,7 @@ During the initial period (usually 6 weeks) after a document has been submitted
- How do I remove a document?
During the initial period (usually 6 weeks) after a document has been submitted, the document can be removed by the authors at any time by sending a request to editors@cdr.eurolisp.org. Afterwards, a document can only be removed under exceptional circumstances. When a document is removed the repository will show the title of the document and indicate its withdrawn status for the records. We will also provide archives of the version(s) of the document and the accompanying material for the purpose of documenting the progress, unless you explicitly ask us not to do so.
During the initial period (usually 6 weeks) after a document has been submitted, the document can be removed by the authors at any time by sending a request to editors@cdr.eurolisp.org. Afterwards, a document can only be removed under exceptional circumstances. When a document is removed the repository will show the title of the document and indicate its withdrawn status for the records. We will also provide archives of the version(s) of the document and the accompanying material for the purpose of documenting the progress unless you explicitly ask us not to do so.
Marc Battyani, Pascal Costanza, Arthur Lemmens, Edmund Weitz
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html> <head>
<title>CDR 4: Common Lisp Document Repository (revised)</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" charset="UTF-8">
<html>
<head>
<title>CDR 4: Common Lisp Document Repository (revised)</title>
<meta http-equiv="Content-Type"
content="text/html; charset=UTF-8"
charset="UTF-8">
<link rel="stylesheet" href="../../cdr.css">
</head>
</head>
<body>
<h1>CDR 4: Common Lisp Document Repository (revised)</h1>
<body>
<h1>CDR 4: Common Lisp Document Repository (revised)</h1>
<h2>Authors</h2>
<h2>Authors</h2>
<p>Marc Battyani, Pascal Costanza, Arthur Lemmens, Edi Weitz</p>
<p>Marc Battyani, Pascal Costanza, Arthur Lemmens, Edi Weitz</p>
<h2>Submitter</h2>
<h2>Submitter</h2>
<p>Pascal Costanza, for contact use <a href=mailto:editors@cdr.eurolisp.org>editors@cdr.eurolisp.org</a></p>
<p>Pascal Costanza, for contact
use <a href="mailto:cdr-discuss@common-lisp.net">cdr-discuss@common-lisp.net</a></p>
<h2>Abstract</h2>
<h2>Abstract</h2>
<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>
<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>
<h2>Rationale</h2>
<h2>Rationale</h2>
<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>http://groups.google.com/group/comp.lang.lisp/msg/15248a1b11c5a603</a> it took nearly 10 years and at least $400K).</p>
<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="https://groups.google.com/g/comp.lang.lisp/c/yIvSw-GVGlw/m/A6bFERuKJBUJ"
target=_blank>a
comment by Kent Pitman's on <tt>comp.lang.lisp</tt></a>,
it took nearly 10 years and at least $400K).</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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>
<p>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>
<h2>The Document</h2>
<h2>The Document</h2>
<ul>
<li><a href=CDR.rtf>.rtf</a></li>
<li><a href=CDR.txt>.txt</a></li>
<li><a href=CDR.pdf>.pdf</a></li>
</ul>
<ul>
<li><a href=CDR.rtf>.rtf</a></li>
<li><a href=CDR.txt>.txt</a></li>
<li><a href=CDR.pdf>.pdf</a></li>
</ul>
<h2>Changes</h2>
<h2>Changes</h2>
<ul>
<li><a href=changes.rtf>.rtf</a></li>
<li><a href=changes.txt>.txt</a></li>
<li><a href=changes.pdf>.pdf</a></li>
</ul>
<ul>
<li><a href=changes.rtf>.rtf</a></li>
<li><a href=changes.txt>.txt</a></li>
<li><a href=changes.pdf>.pdf</a></li>
</ul>
<h2>Status</h2>
<h2>Status</h2>
<p>Final</p>
<p>Final</p>
<h2>Remarks</h2>
<h2>Remarks</h2>
<p>This CDR supersedes <a href="../0/index.html">CDR 0</a>.</p>
<p>This CDR supersedes <a href="../0/index.html">CDR 0</a>.</p>
</body> </html>
</body>
</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