schemedoc / bibliography Goto Github PK

View Code? Open in Web Editor NEW

145.0 17.0 20.0 226 KB

Bibliography of Scheme research (readscheme.org and beyond)

Home Page: https://research.scheme.org

Scheme 98.66% Emacs Lisp 1.34%

scheme-programming-language scheme lisp bibliography

bibliography's People

Stargazers

Watchers

bibliography's Issues

Links return 404

I only checked few but they return 404. This page with Macros.

https://github.com/schemedoc/bibliography/blob/master/page3.md

Add Higher-Order and Symbolic Computation / LISP and Symbolic Computation articles

https://link.springer.com/journal/10990/volumes-and-issues

Page 9 is missing?

It seems
https://github.com/schemedoc/bibliography/blob/master/page9.md
is missing.

There is a page9.scm with contents but the corresponding markdown file is missing.

One markdown file per document

Use the following template and create one markdown per document:

# [Title](https://link/to/document)

By Author1, Author2 and Author3

## Keywords

- abc
- def

## Abstract

abracadabra...

Use github pages to show the contents of this repo?

It maybe is a better way to present these documents.

Empirical solution to name representation

The command:

grep -h '^(author ' page*.scm | sort | uniq | sed -e 's/^(author //' -e 's/)$//' -e 's/"//g' | grep -v others

gives all the names we have so far:

Adams, Norman
Anderson, Claude W
Anderson, Kenneth R
Ashley, J Michael
Baker, Henry G
Bartlett, Joel F
Bartley, David H
Barzilay, Eli
Bawden, Alan
Başar, R Emre
Benson Jr, Brent W
Bothner, Per
Boucher, Dominique
Boussinot, Frédéric
Bres, Yannis
Bruggeman, Carl
Carlstrom, Brian David
Cejtin, Henry
Chen, Pee-Hong
Ciabrini, Damien
Clements, John
Clinger, Will
Clinger, William D
Clinger, William
Cowley, Anthony
Danvy, Olivier
De Roure, David
DePristo, Mark
DeRoure, David
Derici, Caner
Desbien, Jocelyn
Dionne, Carl
Duba, Bruce F
Dwyer, Rex A
Dybvig, R Kent
Earl, Christopher
Epardaud, Stéphane
Farmer, William M
Feeley, Marc
Felleisen, Matthias
Findler, Robert Bruce
Flanagan, Cormac
Flatt, Matthew
Forin, Alessandro
Foster, Ian
Friedman, Daniel P
Friedman, Daniel P.
Fuchs, Matthew
Gasbichler, Martin
Germain, Guillaume
Ghuloum, Abdulaziz
Grossman, Dan
Guttman, Joshua D
Halstead Jr, Robert H
Hansen, Lars Thomas
Hanson, Chris
Hartheimer, Anne
Haynes, Christopher T
Haynes, Christopher T.
Hickey, Timothy J
Hieb, Robert
Hilsdale, Erik
Hudak, Paul
Jagannathan, Suresh
Jensen, John C
Katz, Morry
Keep, Andrew W
Kelsey, Richard A
Kelsey, Richard
Kimball, Aaron
Kranz, David A
Kranz, David
Krishnamurthi, Shriram
Lang, Kevin J
Lapalme, Guy
Loaiza, Juan R
Loitsch, Florian
Marshall, Joe
Masuhara, Hidehiko
McDermott, Drew
Meunier, Philippe
Might, Matthew
Miller, James S
Miller, James
Miller, Scott G
Mirani, Rajiv
Mohr, Eric
Monk, Leonard G
Monnier, Stefan
Moreau, Luc
Muller, Hans
Nagata, Akihito
Norvig, Peter
Oliva, Dino P
Ost, Eric
Pearlmutter, Barak A
Pettyjohn, Greg
Philbin, James
Philbin, Jim
Piquer, José
Piérard, Adrien
Pleban, Uwe F
Pleban, Uwe F.
Prabhu, Tarun
PreScheme, Multithreaded
Queinnec, Christian
Ramsdell, John D
Rees, Jonathan A
Rees, Jonathan
Ribbens, Daniel
Rose, John R
Rozas, Guillermo J
Rozas, Guillermo
Sabry, Amr Afaf
Sabry, Amr
Sarkar, Dipanwita
Schooler, Richard
Schultz, Ulrik P
Schultz, Ulrik Pagh
Serpette, Bernard P
Serpette, Bernard Paul
Serpette, Bernard
Serrano, Manuel
Shivers, Olin
Sperber, Michael
Stamos, James W
Steele Jr, Guy L
Steele Jr, Guy Lewis
Steele, Guy L
Sumii, Eijiro
Sussman, Gerald Jay
Swarup, Vipin
Tammet, Tanel
Taura, Kenjiro
Taylor, CJ
Teodosiu, Dan
Thanos, Dimitri
Thiemann, Peter
Tinker, Pete
Turcotte, Marcel
Van Horn, David
Vegdahl, Steven R
Vitek, Jan
Waddell, Oscar
Wand, Mitchell
Weeks, Stephen
Weis, Pierre
Weise, Daniel
Wilson, Jason
Wittenberger, J
Yonezawa, Akinori
Şenol, Çağdaş

Add SIGPLAN Lisp Pointers articles

https://dl.acm.org/newsletter/sigplan-lisppointers

More papers that are not yet included in the bibliography

ORBIT: An Optimizing Compiler For Scheme by David Andrew Kranz
https://cpsc.yale.edu/sites/default/files/files/tr632.pdf

First pass: convert Markdown to LOSE

I'd like to start by first converting each foo.md file currently in the repo to an equivalent LOSE file foo.scm listing exactly the same papers.

After that, we can think about reorganizing them.

If we work on these goals in parallel, I feel it would become difficult to keep track of the complete set of papers we have, and it would be easy to accidentally drop some papers from the collection. It's also more fun to do the reorg than to convert the current papers, so having to convert first will motivate us to get it done ;)

Thoughts?

Clarify licenses

My understanding is that a database, especially a list of facts, is not necessarily a work from copyright law point of view. (IANAL; TINLA)

However, specifying the licenses of work is vital to free and open source collaboration. My proposal is: CC0-1.0 for database and MIT or MIT/Apache-2.0 dual licenses for software.

Add Workshop on Continuations proceedings

First of all, thanks a lot for making this backup, readscheme.org (RIP) was a wonderful resource. I'm thankful that you managed to preserve it.

I've been thinking, we could also include the proceedings of the Workshop on Continuations:

Workshop on Continuations (WoC 2015): http://eptcs.web.cse.unsw.edu.au/content.cgi?WoC15 https://arxiv.org/html/1606.05839
ACM SIGPLAN Continuation Workshop (CW 2011): http://www.cs.tsukuba.ac.jp/~kam/CW2011/index.html
Continuation Fest 2008: http://logic.cs.tsukuba.ac.jp/~kam/Continuation2008/
ACM SIGPLAN Continuation Workshop (CW 2004): http://www.cs.bham.ac.uk/~hxt/cw04/index.html
ACM SIGPLAN Workshop on Continuations (CW 2001): https://web.archive.org/web/20100729140303/http://www.cs.indiana.edu/~sabry/cw01/
ACM SIGPLAN Workshop on Continuations (CW 1997): https://web.archive.org/web/20110607065911/http://www.brics.dk/~cw97/

I'm going to make a PR this weekend with these changes.

Bibliographies other than Readscheme

Ozan Yigit's Scheme Bibliography -- https://legacy.cs.indiana.edu/scheme-repository/doc.misc.bib.html

Add Lisp and Functional Programming Conference proceedings

https://dl.acm.org/conference/lfp/proceedings

Organize into yearly files?

It might be most fruitful to organize the papers into yearly files:

1989.scm
1990.scm
1991.scm
...

Since the set of papers published in a particular year is fixed, it's easier to keep track of progress. When the papers are organized by topic (as they are now), each file can grow without bound and there are some ambiguous cases where a paper concerns more than one topic.

The organization by topic is very useful for browsing; we can keep it by adding tags to each paper. Then the topics can be specified as set operations on tags.

@amirouche What do you think about this approach?

schemedoc / bibliography Goto Github PK

bibliography's People

Stargazers

Watchers

Forkers

bibliography's Issues

Recommend Projects

Recommend Topics

Recommend Org