- From: Austin William Wright <aaa@bzfx.net>
- Date: Fri, 18 Sep 2015 13:23:18 -0700
- To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Cc: "public-rdfjs@w3.org" <public-rdfjs@w3.org>
Received on Friday, 18 September 2015 20:23:46 UTC
We have a wiki page for much of this research, it may be a few months out of date by now: https://www.w3.org/community/rdfjs/wiki/Comparison_of_RDFJS_libraries https://www.w3.org/community/rdfjs/wiki/RDF_ECMAScript_APIs GitHub would be a good place to write test suites and such, too. Austin. <https://www.w3.org/community/rdfjs/wiki/RDF_ECMAScript_APIs> On Fri, Sep 18, 2015 at 5:53 AM, ☮ elf Pavlik ☮ < perpetual-tripper@wwelves.org> wrote: > Howdy, > > I would like to propose an effort to map dependencies between various > RDF libraries, tools and apps implemented in javascript. > > Most of them already should have package.json or bower.json with list of > dependencies. > > IMO this exercise can help us better understand different audiences > (developers of libraries, tools and apps) as well as have better > overview of current state of this environment. > > For now I started forking various projects to > https://github.com/rdfjs > > This way we can write script which will fetch that list from github api, > get all the package.json and bower.json and process them. Whenever we > find new project we can simply fork it and re run such script. > > https://developer.github.com/v3/activity/events/types/#forkevent > > RDF output we could include in http://rdfjs.org and also make it update > automatically. > > Cheers! > >
Received on Friday, 18 September 2015 20:23:46 UTC