JSON license service

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

JSON license service

Jonathan Gray
(updating subject line to reflect topic)

This looks fantastic Kent!

Are you on the Open Definition discuss list? It would be great to
reintegrate this back into the Open Definition licensing service.

http://lists.okfn.org/mailman/listinfo/od-discuss

I'm cc'ing the list.

J.

On Tue, Jul 31, 2012 at 8:04 PM, Kent Mewhort <[hidden email]> wrote:

> Hi Everyone,
>
> I just joined this list earlier today after being directed towards this
> thread.  I'm actually working on a project to accomplish some of what's
> being described with respect to license metadata.
>
> Specifically, I'm trying to describe the core features of data licenses in a
> machine readable format (JSON).  This is a first step towards several other
> projects in the works to help users view the core license terms of any data
> license in a CC "Legal Deed"-style format, as well as to compare the
> compatibility and risks of different data/content/software licenses.
>
> You can best view the beta JSON format that I've come up with at the
> following link, with a few licenses already filled-out:
> http://clip-test.cippic.ca/tools/license_editor/index.html.  It's backwards
> compatible with the Open Definition Project (with the idea to reintegrate in
> the future).  I'd really appreciate any comments, especially w.r.t. any
> important license aspects anyone thinks are missing.
>
> I'll also directly post an example for ODC-By-1.0:
>
> {
>    "id": "ODC-By-1.0",
>    "title": "ODC Attribution License v.1.0",
>    "url": "http://opendatacommons.org/licenses/by/1.0/",
>    "maintainer": "Open Data Commons",
>    "domain_content": false,
>    "domain_data": true,
>    "domain_software": false,
>    "is_okd_compliant": true,
>    "is_osi_compliant": false,
>    "is_dfcw_compliant": false,
>    "status": "active",
>    "rights":
>    {
>        "right_to_use_and_reproduce": true,
>        "right_to_modify": true,
>        "right_to_distribute": true,
>        "covers_copyright": true,
>        "covers_neighbouring_rights": true,
>        "covers_sgdrs": true,
>        "covers_moral_rights": true,
>        "covers_trademarks": false,
>        "covers_patents": false,
>        "covers_circumventions": false,
>        "prohibits_commercial_use": false,
>        "prohibits_tpms": false,
>        "prohibits_tpms_unless_parallel": false
>    },
>    "obligations":
>    {
>        "obligation_notice": true,
>        "obligation_modifiable_form": false,
>        "obligation_attribution_flexible": true,
>        "obligation_attribution_specific": false,
>        "obligation_attribution_specific_details": "",
>        "obligation_copyleft": false
>    },
>    "copyleft":
>    {
>    },
>    "sublicensing":
>    {
>        "sublicense_any": false,
>        "sublicense_future_versions": false,
>        "sublicense_other": ""
>    },
>    "termination":
>    {
>        "termination_automatic": true,
>        "termination_discretionary": false,
>        "termination_reinstatement": true
>    },
>    "license_changes":
>    {
>        "license_changes_effective_immediately": false
>    },
>    "disclaimers":
>    {
>        "disclaimer_warranty": true,
>        "disclaimer_liability": true,
>        "disclaimer_indemnity": false,
>        "warranty_noninfringement": false
>    },
>    "conflict_of_laws":
>    {
>        "law_of": "forum",
>        "forum_of": "unspecified"
>    }
> }
>
>
> Kent
>
> --
> Kent Mewhort
> Staff Lawyer
> CIPPIC, the Samuelson-Glushko Canadian Internet Policy & Public Interest
> Clinic
> University of Ottawa, Faculty of Law
> 57 Louis Pasteur St.
> Ottawa, Ontario  K1N 6N5
>
> Ph:  (613)562-5800 (ext.2556)
> Fax: (613)562-5417
>
>
> On 31/07/12 01:43 PM, Jonathan Gray wrote:
>> Regarding the open license identifier idea, you might like this:
>>
>>
>> http://blog.okfn.org/2012/02/16/announcing-the-open-definition-licenses-service/
>>
>> Regarding a bunch of 'buckets' of data, I wonder whether CKAN or
>> TheDataHub.org might be of any value for this? It already has the Open
>> Definition licenses service built into it, and has lots of geodata
>> aggregated from different sources around the world.
>>
>> http://thedatahub.org/
>> http://ckan.org/
>>
>> All the best,
>>
>> Jonathan
>>
>> On Tue, Jul 31, 2012 at 2:04 PM, Arnulf Christl
>> <[hidden email]> wrote:
>
> On 07/31/2012 12:23 AM, Scot Wilcoxon wrote:
>>>> On Mon, 2012-07-30 at 11:40 +0100, Seven (aka Arnulf) wrote:
>>>>>
>>>>> 1. My suggestion is to also use this committee as a hub to build
>>>>> knowledge around licenses, maintain a repository of initiatives
>>>>> and link everything together. Not so much like hard metadata in a
>>>>> catalog but a lot looser, more like a big bucket with goodies to
>>>>> find.
>>>>
>>>> I think the concept that you're looking for is a "semantic web".
>>>> http://en.wikipedia.org/wiki/Semantic_Web
>
> Scot, sure thing but I wanted to avoid the term because people
> associate all kinds of things with Semantic Web that I want to avoid
> at this stage. :-)
>
>>>> A bunch of buckets of data, and you define the characteristics of
>>>> the buckets so software can use (and display) the info.
>
> The "bucket" context is taken from David Weinberger's "Everything is
> Misceallaneous" [1] and my intention was to purposefully not make it
> technically sound yet but leave as a Wiki until we know where this is
> going. At the same time the semantic extensions for Mediawiki are
> evolving and might eventually do the job you suggest without much help
> from our side.
>
> Thanks,
> Arnulf
>
> [1] http://evident.com/
>
>>>> * You have a license object which defines the characteristics of a
>>>> license. Probably defined in something like XML. * You define a
>>>> license (identifier="CC-BY-SA", name="Creative Commons ... etc",
>>>> restrictions="share-derivatives,attribute", etc...) -- except you
>>>> probably use XML. * You have a data object which defines the
>>>> characteristics of some data, and this includes the license
>>>> (identifier). * You define data using the data object
>>>> characteristics.
>>>>
>>>> If a data definition is available through a URL, inside that
>>>> definition will be the relevant other objects, including the URL of
>>>> the data object definition, the license identifier ("CC-BY-SA"),
>>>> and the URL of the definition of the license.  Similarly, the
>>>> license includes the URL of the license object which defines all
>>>> the license fields.
>>>>
>>>>
>>>> _______________________________________________ Geodata mailing
>>>> list [hidden email]
>>>> http://lists.osgeo.org/mailman/listinfo/geodata
>>>>
>
>
>>> _______________________________________________
>>> Geodata mailing list
>>> [hidden email]
>>> http://lists.osgeo.org/mailman/listinfo/geodata
>>
>>
>>
>



--
Jonathan Gray

Community Coordinator
The Open Knowledge Foundation
http://www.okfn.org

http://twitter.com/jwyg
_______________________________________________
Geodata mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/geodata
Reply | Threaded
Open this post in threaded view
|

Re: JSON license service

Puneet Kishor
We (http://earth-base.org) have been experimenting with sending various licenses in JSON format. We are trying to standardize them, specifically reconciling them with ccREL used for embedding CC licenses in RDFa. Would love to see a lot of activity and interest in this front.


On Jul 31, 2012, at 3:47 PM, Jonathan Gray <[hidden email]> wrote:

> (updating subject line to reflect topic)
>
> This looks fantastic Kent!
>
> Are you on the Open Definition discuss list? It would be great to
> reintegrate this back into the Open Definition licensing service.
>
> http://lists.okfn.org/mailman/listinfo/od-discuss
>
> I'm cc'ing the list.
>
> J.
>
> ..


--
Puneet Kishor

_______________________________________________
Geodata mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/geodata