News for hackers. Stuff that matters.
Re:Readings in Databases by walterbell on Friday August 29, 2014 @12:17AM (#8241098)
These lists (of lists ..) are reinventing early Yahoo/DMOZ/webrings. If lists were available in a parseable format with accurate metadata (title, author, date, publisher), one could monitor github RSS and generate a local master list for analysis.

Related: https://github.com/inukshuk/jekyll-scholar

Re:Readings in Databases by mtdewcmu on Friday August 29, 2014 @02:33AM (#8241378)
Assuming you're right that this is a trend, I don't think it should be too hard to heuristically pick out likely examples. Assuming most of them are good quality, there should not be so many that it's impossible to pick through the results and do the final formatting manually. Waiting for a standard format to come along could take a while (seen the semantic web yet?).
Re:Readings in Databases by walterbell on Friday August 29, 2014 @09:23AM (#8242354)
The jekyll-scholar format already exists and is more "semantic" than Markdown. After people read these database papers, perhaps one will understand the value of indexing structured data and convert/fork the list repo to structure the source format. This is easy at the birth of a collaboratively edited project and impossible later.

> Assuming you're right that this is a trend

Here is one list of lists, https://github.com/sindresorhus/awesome

Re:Readings in Databases by mtdewcmu on Friday August 29, 2014 @10:55AM (#8242769)
My experience has been that expecting people to do more work, even a little bit more, doesn't often pan out.
Re:Readings in Databases by walterbell on Friday August 29, 2014 @11:17AM (#8242884)
At least MS/Google will thank humans for enriching their proprietary knowledge graphs / semantic webs. It may take a few more years for people to realize why they need "personal algos" as much as "personal computing devices". Humans can then feed delectable metadata to their private algos, in addition to feeding large public spiders.