- From: David I. Lehn <dil@lehn.org>
- Date: Fri, 31 Jan 2014 19:13:18 -0500
- To: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Cc: Dave Longley <dlongley@digitalbazaar.com>, Matteo Collina <matteo.collina@gmail.com>, "public-rdfjs@w3.org" <public-rdfjs@w3.org>, alex@milowski.com
On Fri, Jan 31, 2014 at 4:58 AM, ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org> wrote: > On 01/29/2014 10:15 PM, Dave Longley wrote: >> >> I think adding a "jsonld-core" library is messy and, in the end, will be >> confusing. So I'd rather see the extras moved out into their own lib. >> Once they are moved out, we can bump the npm version to indicate to >> dependencies that there have been backwards-incompatible changes. > > awesome! > > with current version 0.1.27 of jsonld.js people shouldn't expect that much > stability yet and in long run it can help avoiding confusions in a future... > > Alex what do you think about releasing green-turtle to NPM? we could help > with it if you welcome such offer :) > https://npmjs.org/search?q=rdfa > > BTW I also met @bergie in Berlin in last weeks and we spoken shortly about > updating http://npm.im/vie IMOy green-turtle available through npm would > also come handy in that case! > Since this is mainly a jsonld.js issue, I put a long comment on github: https://github.com/digitalbazaar/jsonld.js/issues/41#issuecomment-33855670 Short version: I'd rather not split up the library and explore solving the issues directly. -dave
Received on Saturday, 1 February 2014 00:13:45 UTC