Re: Licensing advice

Hi Barry

As Boris mentioned, this is an ongoing work.
Currently we have the mappings as ttl files in our server, and we are
thinking to store them in a triplestore (since R2RML mappings are in RDF).
So, we'd be more than happy to pull your mappings to our repository.

Thanks!
Freddy


On Fri, Jul 12, 2013 at 2:38 PM, Barry Norton <barry.norton@ontotext.com>wrote:

>
> Boris, that's really interesting, I wasn't aware.
>
> Under mappings, though, I just see directory listings and no version
> control - if these remain under git(hub) would you poll them?
>
> Cheers,
>
> Barry
>
>
>
> On 12/07/13 13:35, Boris Villazon-Terrazas wrote:
>
>> Hi Barry
>>
>> This is not fully related with your question. But, within mappingpedia
>> initiative [1]  we are collecting RDB2RDF mappings. So, your mappings would
>> be useful for us.
>> We are developing a vocab for describing the mappings, and we will
>> include the licence information.
>>
>> Boris
>>
>>
>> [1] http://mappingpedia.**linkeddata.es/<http://mappingpedia.linkeddata.es/>
>>
>> On 12/07/2013 14:20, Barry Norton wrote:
>>
>>>
>>> I'd like to publicly release R2RML mappings for the MusicBrainz dataset.
>>> DBpedia has shown interest in including the subset that can be used to
>>> create a linkset.
>>>
>>> Any idea what (kind of) licence could/should apply? (To be clear, to the
>>> mappings, as opposed to the dataset)
>>>
>>> I'd also like to attach, since R2RML is RDF, a licence and attribution
>>> on a per rr:TriplesMap basis. (The mappings are hosted on github and
>>> contributions will be accepted as I'm never going to get through all of the
>>> MB Advanced Relationships, a moving target, myself and I'm being a
>>> bottleneck.)
>>>
>>> The question's also been raised on whether a given licence can in turn
>>> impose conditions on the triples that are created using it (as derivative
>>> works)? Does that sound feasible?
>>>
>>> Any input appreciated.
>>>
>>> Barry
>>>
>>>
>>>
>>
>>
>
>