Talk:Scheme: An Interpreter for Extended Lambda Calculus
Information about this edition | |
---|---|
Edition: | Scheme: An interpreter for extended lambda calculus, 1975 |
Source: | Index:Scheme - An interpreter for extended lambda calculus.djvu |
Contributor(s): | Piet Delport |
Level of progress: | Proofread and corrected |
Permission
[edit]
This work is free and may be used by anyone for any purpose. If you wish to use this content, you do not need to request permission as long as you follow any licensing requirements mentioned on this page.
Wikimedia has received an e-mail confirming that the copyright holder has approved publication under the terms mentioned on this page. This correspondence has been reviewed by an OTRS member and stored in our permission archive. The correspondence is available to trusted volunteers.
Public domainPublic domainfalsefalse
See also Talk:Lambda Papers#Permission. --Piet Delport (talk) 21:15, 19 December 2009 (UTC)
DIV
[edit]You may wish to consider to wrap the page in <div class=lefttext> or <div class=prose> which better allows the page data to show when you toggle
display options * links to scans
in the left hand margin. -- billinghurst (talk) 01:08, 7 September 2009 (UTC)
- Thanks. The
lefttext
andprose
classes seem to make the text column too narrow to contain the source code quotes, though? I added a direct 5em left margin instead, which seems to work. --Piet Delport (talk) 02:24, 7 September 2009 (UTC)
- That was my quick opinion too when I did a quick preview, hence, why I threw it back to you. -- billinghurst (talk) 04:45, 7 September 2009 (UTC)
Copyright
[edit]I see no reason why PD-USGov would apply. "Support for the laboratory's artificial intelligence research is provided in part by the Advanced Research Projects Agency of the Department of Defense under Office of Naval Research contract N00014-75-C-0643." does not make the authors into employees of the Federal Government, nor does it even give the government control over any part of the output.--Prosfilaes (talk) 03:17, 7 September 2009 (UTC)
- (Responded at Wikisource:Possible copyright violations#Scheme: An interpreter for extended lambda_calculus) --Piet Delport (talk) 00:10, 8 September 2009 (UTC)
Okay, i had the following correspondence with the authors and Patrick Winston, the AI Lab director at the time the papers were written, and they're all happy with free use of the memos as long as attribution is given.
- (Moved to Talk:Lambda Papers#Permission. --Piet Delport (talk) 21:13, 19 December 2009 (UTC))
I'll change the license template to {{cc-by-3.0}}. --Piet Delport (talk) 17:34, 29 September 2009 (UTC)
Reference formatting
[edit]I formatted the in-text citation references using a combination of Cite.php and Labeled Section Transclusion.
Each citation in the Bibliography is labeled for transclusion like:
<section begin="Moon"/>'''[Moon]'''<br/> Moon, David A. ''MACLISP Reference Manual, Revision 0''. Project MAC, MIT (Cambridge, April 1974).<section end="Moon"/>
and then referenced in the main text (e.g. Abstract) like:
[Moon]<ref name="Moon">{{#section:Page:Scheme - An interpreter for extended lambda calculus.djvu/43|Moon}}</ref>
Advantage: References are visible both on individual pages and wherever they are transcluded, without source duplication.
Disadvantage: It would be nicer if the reference number:
MacLISP [Moon][1]
could be replaced with the name:
MacLISP[Moon]
but Cite.php does not support this yet, to my knowledge. --Piet Delport (talk) 18:16, 3 October 2009 (UTC)
Possible improvements
[edit]The text should be in a reasonable good state now, but some things could be better:
- Trace formatting: The computation traces in Section 3 are currently just big
<syntaxhighlight>
blocks; they might be formatted better as a table of some sort. - Syntax highlighting: The GeSHi highlighting for Scheme/Lisp sucks a bit. Improve it, or figure out a good way to do explicit formatting? (The latter would also allow non-highlighting annotations and markup, such as {{SIC}}.)
- Table of Contents: Is there a way to make MediaWiki's usual TOC generation work for transcluded
<pages>
(especially for Whole text)? - Section links: Is there a reasonable way to make section references render as relative links (
../Section 3
) within individual sections, and as fragment links (#Section 3
) within Whole text?
A bigger project to tackle would be annotations for the text, with historical notes and explanations, and modern source code equivalents. (Compare the 1998 HOSC revisit and reprint.) --Piet Delport (talk) 21:35, 14 October 2009 (UTC)