[open-sustainability] AMEE data licensing

Mon Nov 26 15:54:23 UTC 2012

Fantastic. Look forward to hearing more about this. Let us know if there is
anything you need from our end!

J.

On Mon, Nov 26, 2012 at 4:53 PM, Chris Adams <chris.adams at amee.com> wrote:

> Hi guys,
>
> I'm a current employee of AMEE.
>
> I'm checking internally about a few of the licenses this week, and once I
> can provide more clarity.
>
> I'd be happy to have a convo about how best to go about doing this best,
> as I expect when the company was aggregating this data from all these
> sources, working out how to republish it under an open licence wasn't the
> main priority, and speaking to others about how they've gone about
> relicensing data (not code) like this would be extremely handy.
>
> But in terms of intentions - we're now keen to have this data licensed as
> permissively as the law will allow us to do so.
>
> C
>
>
>
>
> On 26 November 2012 15:36, James Smith <james at floppy.org.uk> wrote:
>
>> Rough list of the major datasets included:
>> http://discover.amee.com/categories/Primary_Data_and_Methodologies_Represented_in_AMEE
>>
>> I suspect that most of them aren't openly licensed, though other
>> ex-colleagues could probably be more authoritative on this than me.
>> Hopefully we'll hear from them here soon, I've told them about our
>> conversation.
>>
>> cheers,
>> James
>>
>> On Monday, 26 November 2012 at 15:31, Jonathan Gray wrote:
>>
>> (Forking thread as there are two separate discussions to be had: (i) call
>> for help maintaining AMEE data and (ii) licensing of AMEE data!)
>>
>> Re: (ii) if we can establish which bits of AMEE are openly licensed, then
>> that will do a lot to help sign off more official support for (i) from OKFN.
>>
>> I guess the most obvious question is: is there a list of sources that
>> AMEE has its data from? If we can work this out, then we should be able to
>> figure out which bits AMEE is able to say are open and which bits it can't!
>>
>> J.
>>
>>
>> On Mon, Nov 26, 2012 at 4:21 PM, James Smith <james at floppy.org.uk> wrote:
>>
>>  That's the interesting part. AMEE was always a republisher of other
>> people's datasets, and I'm not sure where that puts the legal situation.
>> Combine that with the fact that the internal representations of the
>> datasets have been released under the MIT license, and I'm *really* not
>> sure.
>>
>> I'd love someone who knows the ins and outs of open data licensing to try
>> to work it out, because now that the data is accessible outside the
>> company, making it properly Open would be awesome.
>>
>> cheers,
>> James
>>
>> On Monday, 26 November 2012 at 15:12, Jonathan Gray wrote:
>>
>> Amazing! Is the data (or some portion of it) openly licensed?
>>
>> J.
>>
>>
>> On Mon, Nov 26, 2012 at 12:51 PM, James Smith <james at floppy.org.uk>wrote:
>>
>>  Hey guys,
>>
>> You all know AMEE, the platform for running carbon calculation
>> methodologies. It was a great thing, and had a good run, but I suspect that
>> it's winding down and the data is not being maintained as much as it
>> should. It was never an Open project, and suffered from not getting
>> submissions of new data from the outside, but I still think it's a very
>> useful resource to have around.
>>
>> AMEE have now open sourced their datasets at
>> https://github.com/AMEE/datasets, and ex-employees have defined a better
>> open standard for executable data (https://github.com/spatchcock/calcJSON),
>> and a conversion tool to go from one to the other (
>> https://github.com/Floppy/connery).
>>
>> The nice thing is that the calcJSON format means you don't need an API
>> platform to use the data, so it makes it possible for a voluntary effort to
>> take over the AMEE data and maintain it in an open way just using github,
>> and extend it to include other datasets that it never had before.
>>
>> I'd love to find a way to make this happen, as the resource that's there
>> is too good to stay locked up and slowly dying. Anyone interested, and more
>> importantly, able to put in any time?
>>
>> cheers,
>> James
>>
>>
>> _______________________________________________
>> open-sustainability mailing list
>> open-sustainability at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/open-sustainability
>>
>>
>>
>>
>> --
>> Jonathan Gray <http://jonathangray.org/> | @jwyg<http://twitter.com/jwyg>
>> The Open Knowledge Foundation <http://okfn.org/> | @okfn<http://twitter.com/okfn>
>> Support our work: okfn.org/support
>>
>>  _______________________________________________
>> open-sustainability mailing list
>> open-sustainability at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/open-sustainability
>>
>>
>>
>> _______________________________________________
>> open-sustainability mailing list
>> open-sustainability at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/open-sustainability
>>
>>
>>
>>
>> --
>> Jonathan Gray <http://jonathangray.org/> | @jwyg<http://twitter.com/jwyg>
>> The Open Knowledge Foundation <http://okfn.org/> | @okfn<http://twitter.com/okfn>
>> Support our work: okfn.org/support
>>
>>  _______________________________________________
>> open-sustainability mailing list
>> open-sustainability at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/open-sustainability
>>
>>
>>
>> _______________________________________________
>> open-sustainability mailing list
>> open-sustainability at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/open-sustainability
>>
>>
>
> _______________________________________________
> open-sustainability mailing list
> open-sustainability at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/open-sustainability
>
>

-- 
Jonathan Gray <http://jonathangray.org/> | @jwyg <http://twitter.com/jwyg>
The Open Knowledge Foundation <http://okfn.org/> |
@okfn<http://twitter.com/okfn>
Support our work: okfn.org/support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/open-sustainability/attachments/20121126/51c43fcf/attachment.html>