Quantcast

Rights/Authorship of Dependent Styles

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Rights/Authorship of Dependent Styles

Richard Karnesky
> Date: Fri, 13 May 2011 13:49:07 -0400
> From: Rintze Zelle <[hidden email]>
> Subject: Re: [xbiblio-devel] use of CSL styles in Peaya with changed
>        attribution
>
> In related news, I recently updated the CSL schema to disallow the cs:rights
> element in cs:info for dependent styles, as I think we shouldn't bother with
> licensing those (none of the existing dependent styles include a cs:rights
> element).


Rintze contacted me off-list because (contrary to the above) dependent
styles I wrote did use this and other recently removed elements.  I'll
just throw in my two cents:  I think that it was useful for dependent
styles to have authors/contributors that have apparently been removed
from the schema recently.  Rintze also noticed that two of the
AIP-dependent styles I wrote used the same title & was able to contact
me for clarification.  A point of contact is useful for many things.
If I see a dependent style doesn't seem quite right for a paper I'm
writing, do I fork the style into a dependent one?  Do I modify the
style it is dependent on, changing the output for all other dependent
styles?  Or perhaps I should just add an ISSN or other identifying
information to let me know that the dependent style applies to some
other journal whose name happens to be similar to the name of some
different journal I'm actually writing to.  Being able to ask for
clarification seems like a good thing.  I'd like to see the author
elements restored.

Regarding rights: I know that Bruce has taken the position that ALL
CSL styles are not copyrightable.  Neither of us are lawyers, but I've
talked to lawyers about this issue.  Lawyers never give you a straight
answer, but the informal consensus I got was that the US copyright
laws were so all-encompassing that they probably are subject to US
copyright & that we should act as if they are, as we don't really lose
anything if we do.

The dependent styles are much less expressive than the independent
styles & much less is lost if they are somehow used contrary to
CC-BY-SA.  But I don't know whether this, alone, is reason to remove
the rights tag.  I suppose I just don't see what real benefit doing
that will bring.

--Rick

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
On Tue, May 17, 2011 at 10:18 AM, Richard Karnesky <[hidden email]> wrote:
> Date: Fri, 13 May 2011 13:49:07 -0400
> From: Rintze Zelle <[hidden email]>
> Subject: Re: [xbiblio-devel] use of CSL styles in Peaya with changed
>        attribution
>
> In related news, I recently updated the CSL schema to disallow the cs:rights
> element in cs:info for dependent styles, as I think we shouldn't bother with
> licensing those (none of the existing dependent styles include a cs:rights
> element).


Rintze contacted me off-list because (contrary to the above) dependent
styles I wrote did use this and other recently removed elements.  I'll
just throw in my two cents:  I think that it was useful for dependent
styles to have authors/contributors that have apparently been removed
from the schema recently.

I'll restore cs:author, cs:contributor and cs:rights to dependent styles (unless somebody disagrees with Rick). Removing them was a maybe not so thought-out decision when I split the schema for dependent and independent styles.

Rintze

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Bruce D'Arcus-3
In reply to this post by Richard Karnesky
On Tue, May 17, 2011 at 10:18 AM, Richard Karnesky <[hidden email]> wrote:

>> Date: Fri, 13 May 2011 13:49:07 -0400
>> From: Rintze Zelle <[hidden email]>
>> Subject: Re: [xbiblio-devel] use of CSL styles in Peaya with changed
>>        attribution
>>
>> In related news, I recently updated the CSL schema to disallow the cs:rights
>> element in cs:info for dependent styles, as I think we shouldn't bother with
>> licensing those (none of the existing dependent styles include a cs:rights
>> element).
>
>
> Rintze contacted me off-list because (contrary to the above) dependent
> styles I wrote did use this and other recently removed elements.  I'll
> just throw in my two cents:  I think that it was useful for dependent
> styles to have authors/contributors that have apparently been removed
> from the schema recently.  Rintze also noticed that two of the
> AIP-dependent styles I wrote used the same title & was able to contact
> me for clarification.  A point of contact is useful for many things.
> If I see a dependent style doesn't seem quite right for a paper I'm
> writing, do I fork the style into a dependent one?  Do I modify the
> style it is dependent on, changing the output for all other dependent
> styles?  Or perhaps I should just add an ISSN or other identifying
> information to let me know that the dependent style applies to some
> other journal whose name happens to be similar to the name of some
> different journal I'm actually writing to.  Being able to ask for
> clarification seems like a good thing.  I'd like to see the author
> elements restored.

That seems reasonable to me, but I have no strong opinion either way.

> Regarding rights: I know that Bruce has taken the position that ALL
> CSL styles are not copyrightable.  Neither of us are lawyers, but I've
> talked to lawyers about this issue.  Lawyers never give you a straight
> answer, but the informal consensus I got was that the US copyright
> laws were so all-encompassing that they probably are subject to US
> copyright & that we should act as if they are, as we don't really lose
> anything if we do.

Just to be clear, I have not taken any position on this, since IANAL.
I have only raised questions, most specifically about what a "BY"
clause on an individual style would mean practically (the larger
question is whether this is really a creative work, and thus whether
CC licenses are most appropriate at all).

> The dependent styles are much less expressive than the independent
> styles & much less is lost if they are somehow used contrary to
> CC-BY-SA.  But I don't know whether this, alone, is reason to remove
> the rights tag.  I suppose I just don't see what real benefit doing
> that will bring.

I have a feeling Rintze is more worrying about future hypothetical
issues. Are we OK with someone submitting a dependent style to the
repo that has rights like "all rights reserved; contact author for
permission to use"?

It would be nice if we could clear up the legal issues how, and then
adopt policies accordingly.

Bruce

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
On Tue, May 17, 2011 at 10:27 AM, Bruce D'Arcus <[hidden email]> wrote:
> The dependent styles are much less expressive than the independent
> styles & much less is lost if they are somehow used contrary to
> CC-BY-SA.  But I don't know whether this, alone, is reason to remove
> the rights tag.  I suppose I just don't see what real benefit doing
> that will bring.

I have a feeling Rintze is more worrying about future hypothetical
issues.

Well, dependent styles are basically just bookmarks with a little bit of metadata, so I thought it would make little sense to apply a license.
 
Are we OK with someone submitting a dependent style to the
repo that has rights like "all rights reserved; contact author for
permission to use"?

We wouldn't be okay with that. I think an important question is whether, if we decide that CC-BY-SA is a good license for dependent and independent styles, it would make sense to make it the mandatory license for styles hosted in the github repo. As I mentioned here (http://xbiblio-devel.2463403.n2.nabble.com/use-of-CSL-styles-in-Peaya-with-changed-attribution-td5267001.html#a6360339), that would make it much easier for CSL adopters to comply with the licensing terms (currently, they'd theoretically have to check each individual style to see which license it uses).

Rintze

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Sebastian Karcher


We wouldn't be okay with that. I think an important question is whether, if we decide that CC-BY-SA is a good license for dependent and independent styles, it would make sense to make it the mandatory license for styles hosted in the github repo. As I mentioned here (http://xbiblio-devel.2463403.n2.nabble.com/use-of-CSL-styles-in-Peaya-with-changed-attribution-td5267001.html#a6360339), that would make it much easier for CSL adopters to comply with the licensing terms (currently, they'd theoretically have to check each individual style to see which license it uses).

I don't have much of an opinion on most aspects of this - but this part I agree with 100% - I think we should push for the repo to be on a single, open license.
--
------
Sebastian Karcher
Ph.D. Candidate
Department of Political Science
Northwestern University

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
On Tue, May 17, 2011 at 10:57 AM, Sebastian Karcher <[hidden email]> wrote:


We wouldn't be okay with that. I think an important question is whether, if we decide that CC-BY-SA is a good license for dependent and independent styles, it would make sense to make it the mandatory license for styles hosted in the github repo. As I mentioned here (http://xbiblio-devel.2463403.n2.nabble.com/use-of-CSL-styles-in-Peaya-with-changed-attribution-td5267001.html#a6360339), that would make it much easier for CSL adopters to comply with the licensing terms (currently, they'd theoretically have to check each individual style to see which license it uses).

I don't have much of an opinion on most aspects of this - but this part I agree with 100% - I think we should push for the repo to be on a single, open license.

Do any of the other parties aside from Zotero that use CSL styles (i.e. Mendeley, Mekentosj/Papers) have any legal advice on whether CC-BY-SA would be a suitable license?

Rintze

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Robert Knight
Hello Rintze,

Apologies for not replying earlier, can I check that by CC-BY-SA, you
mean http://creativecommons.org/licenses/by-sa/3.0/us/ ?

In that case, I'm pretty sure that should be fine.  We display the
original author (as specified in the CSL file) in the style browser
interface in the Mendeley client, we don't currently display any
licensing information there but I'm happy to add that.

Regards,
Rob.

On 30 May 2011 16:58, Rintze Zelle <[hidden email]> wrote:

> On Tue, May 17, 2011 at 10:57 AM, Sebastian Karcher
> <[hidden email]> wrote:
>>
>>>
>>> We wouldn't be okay with that. I think an important question is whether,
>>> if we decide that CC-BY-SA is a good license for dependent and independent
>>> styles, it would make sense to make it the mandatory license for styles
>>> hosted in the github repo. As I mentioned here
>>> (http://xbiblio-devel.2463403.n2.nabble.com/use-of-CSL-styles-in-Peaya-with-changed-attribution-td5267001.html#a6360339),
>>> that would make it much easier for CSL adopters to comply with the licensing
>>> terms (currently, they'd theoretically have to check each individual style
>>> to see which license it uses).
>>
>> I don't have much of an opinion on most aspects of this - but this part I
>> agree with 100% - I think we should push for the repo to be on a single,
>> open license.
>
> Do any of the other parties aside from Zotero that use CSL styles (i.e.
> Mendeley, Mekentosj/Papers) have any legal advice on whether CC-BY-SA would
> be a suitable license?
>
> Rintze
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> xbiblio-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>
>

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
On Mon, May 30, 2011 at 6:37 PM, Robert Knight <[hidden email]> wrote:
by CC-BY-SA, you
mean http://creativecommons.org/licenses/by-sa/3.0/us/ ?

Or the unported license (http://creativecommons.org/licenses/by-sa/3.0/). The main question is whether CC-licenses are applicable at all to something like CSL styles, or whether we should pick a software license. If everybody is comfortable with CC-BY-SA, it'd like to make it the requirement for styles hosted in the github repo.

We touched on this before, but we never came to a clear conclusion. We could really use some advice from somebody legally schooled.

Rintze

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Bruce D'Arcus-3
In reply to this post by Robert Knight
On Mon, May 30, 2011 at 6:37 PM, Robert Knight
<[hidden email]> wrote:
> Hello Rintze,
>
> Apologies for not replying earlier, can I check that by CC-BY-SA, you
> mean http://creativecommons.org/licenses/by-sa/3.0/us/ ?
>
> In that case, I'm pretty sure that should be fine.  We display the
> original author (as specified in the CSL file) in the style browser
> interface in the Mendeley client, we don't currently display any
> licensing information there but I'm happy to add that.

See, this is the awkward thing about all this. I don't necessarily
want my name to be displayed in clients. When I do put my name as a
contributor on a style, it's only for convenience (so someone knows
who to contact); not to assert any claim to the style.

Rintze followed up with:

> The main question is whether CC-licenses are applicable at all to something like
> CSL styles, or whether we should pick a software license. If everybody is
> comfortable with CC-BY-SA, it'd like to make it the requirement for styles hosted
> in the github repo.
>
> We touched on this before, but we never came to a clear conclusion. We could really
> use some advice from somebody legally schooled.

Yes; and preferably someone with experience with these specific
licenses, and understanding of copyright law.

Bruce

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
On Mon, May 30, 2011 at 8:01 PM, Bruce D'Arcus <[hidden email]> wrote:
> We display the
> original author (as specified in the CSL file) in the style browser
> interface in the Mendeley client, we don't currently display any
> licensing information there but I'm happy to add that.

See, this is the awkward thing about all this. I don't necessarily
want my name to be displayed in clients. When I do put my name as a
contributor on a style, it's only for convenience (so someone knows
who to contact); not to assert any claim to the style.

Authorship assignments are rather messy in the domain of CSL styles, as styles almost always based on other styles, and sometimes receive significant updates after their first release, so the contribution by the primary author may be limited. I agree with Bruce that it's probably better to not include author/contributor names in clients.

Rintze


------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
In reply to this post by Bruce D'Arcus-3
On Mon, May 30, 2011 at 8:01 PM, Bruce D'Arcus <[hidden email]> wrote:
> The main question is whether CC-licenses are applicable at all to something like
> CSL styles, or whether we should pick a software license. If everybody is
> comfortable with CC-BY-SA, it'd like to make it the requirement for styles hosted
> in the github repo.
>
> We touched on this before, but we never came to a clear conclusion. We could really
> use some advice from somebody legally schooled.

Yes; and preferably someone with experience with these specific
licenses, and understanding of copyright law.

I just came across this: http://discovery.ac.uk/files/pdf/Licensing_Open_Data_A_Practical_Guide.pdf (via http://twitter.com/#!/ostephens/statuses/75466458326511616 )

The JISC people are obviously interested in scientific publishing, so they might not mind giving some advice.

Rintze

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
Dear all,

As of this moment, all the CSL styles in the style repository at https://github.com/citation-style-language/styles are registered under a single license, using the exact string "This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/".

I added the license to styles that did not carry one, updated older versions of the license, and replaced ported variants by the unported version. I got permission of the style authors who had released their styles under by-nc-sa licenses to switch to by-sa.

Going forward I would like to require that any new style added to the repository should use Creative Commons Attribution-Share Alike (I already included this in our requirements: https://github.com/citation-style-language/styles/wiki/Style-Requirements ).

If anybody has an issue with any of these changes, please let me know,

Rintze

On Tue, May 31, 2011 at 8:25 AM, Rintze Zelle <[hidden email]> wrote:
On Mon, May 30, 2011 at 8:01 PM, Bruce D'Arcus <[hidden email]> wrote:
> The main question is whether CC-licenses are applicable at all to something like
> CSL styles, or whether we should pick a software license. If everybody is
> comfortable with CC-BY-SA, it'd like to make it the requirement for styles hosted
> in the github repo.
>
> We touched on this before, but we never came to a clear conclusion. We could really
> use some advice from somebody legally schooled.

Yes; and preferably someone with experience with these specific
licenses, and understanding of copyright law.

I just came across this: http://discovery.ac.uk/files/pdf/Licensing_Open_Data_A_Practical_Guide.pdf (via http://twitter.com/#!/ostephens/statuses/75466458326511616 )

The JISC people are obviously interested in scientific publishing, so they might not mind giving some advice.

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Charles Parnot
I am all for it. It seems very reasonable, and while it may keep a few styles out (?), it makes it much easier to use those styles without extra friction.

charles

On Jan 3, 2012, at 3:20 PM, Rintze Zelle wrote:

> Dear all,
>
> As of this moment, all the CSL styles in the style repository at https://github.com/citation-style-language/styles are registered under a single license, using the exact string "This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/".
>
> I added the license to styles that did not carry one, updated older versions of the license, and replaced ported variants by the unported version. I got permission of the style authors who had released their styles under by-nc-sa licenses to switch to by-sa.
>
> Going forward I would like to require that any new style added to the repository should use Creative Commons Attribution-Share Alike (I already included this in our requirements: https://github.com/citation-style-language/styles/wiki/Style-Requirements ).
>
> If anybody has an issue with any of these changes, please let me know,
>
> Rintze
>
> On Tue, May 31, 2011 at 8:25 AM, Rintze Zelle <[hidden email]> wrote:
> On Mon, May 30, 2011 at 8:01 PM, Bruce D'Arcus <[hidden email]> wrote:
> > The main question is whether CC-licenses are applicable at all to something like
> > CSL styles, or whether we should pick a software license. If everybody is
> > comfortable with CC-BY-SA, it'd like to make it the requirement for styles hosted
> > in the github repo.
> >
> > We touched on this before, but we never came to a clear conclusion. We could really
> > use some advice from somebody legally schooled.
>
> Yes; and preferably someone with experience with these specific
> licenses, and understanding of copyright law.
>
> I just came across this: http://discovery.ac.uk/files/pdf/Licensing_Open_Data_A_Practical_Guide.pdf (via http://twitter.com/#!/ostephens/statuses/75466458326511616 )
>
> The JISC people are obviously interested in scientific publishing, so they might not mind giving some advice.
> ------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev_______________________________________________
> xbiblio-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

--
Charles Parnot
[hidden email]
twitter: @cparnot
http://mekentosj.com



------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Robert Knight
Sounds good to me.  Thanks for chasing up existing style authors for
re-licensing.

Regards,
Rob.

On 3 January 2012 23:55, Charles Parnot <[hidden email]> wrote:

> I am all for it. It seems very reasonable, and while it may keep a few styles out (?), it makes it much easier to use those styles without extra friction.
>
> charles
>
> On Jan 3, 2012, at 3:20 PM, Rintze Zelle wrote:
>
>> Dear all,
>>
>> As of this moment, all the CSL styles in the style repository at https://github.com/citation-style-language/styles are registered under a single license, using the exact string "This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/".
>>
>> I added the license to styles that did not carry one, updated older versions of the license, and replaced ported variants by the unported version. I got permission of the style authors who had released their styles under by-nc-sa licenses to switch to by-sa.
>>
>> Going forward I would like to require that any new style added to the repository should use Creative Commons Attribution-Share Alike (I already included this in our requirements: https://github.com/citation-style-language/styles/wiki/Style-Requirements ).
>>
>> If anybody has an issue with any of these changes, please let me know,
>>
>> Rintze
>>
>> On Tue, May 31, 2011 at 8:25 AM, Rintze Zelle <[hidden email]> wrote:
>> On Mon, May 30, 2011 at 8:01 PM, Bruce D'Arcus <[hidden email]> wrote:
>> > The main question is whether CC-licenses are applicable at all to something like
>> > CSL styles, or whether we should pick a software license. If everybody is
>> > comfortable with CC-BY-SA, it'd like to make it the requirement for styles hosted
>> > in the github repo.
>> >
>> > We touched on this before, but we never came to a clear conclusion. We could really
>> > use some advice from somebody legally schooled.
>>
>> Yes; and preferably someone with experience with these specific
>> licenses, and understanding of copyright law.
>>
>> I just came across this: http://discovery.ac.uk/files/pdf/Licensing_Open_Data_A_Practical_Guide.pdf (via http://twitter.com/#!/ostephens/statuses/75466458326511616 )
>>
>> The JISC people are obviously interested in scientific publishing, so they might not mind giving some advice.
>> ------------------------------------------------------------------------------
>> Write once. Port to many.
>> Get the SDK and tools to simplify cross-platform app development. Create
>> new or port existing apps to sell to consumers worldwide. Explore the
>> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
>> http://p.sf.net/sfu/intel-appdev_______________________________________________
>> xbiblio-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>
> --
> Charles Parnot
> [hidden email]
> twitter: @cparnot
> http://mekentosj.com
>
>
>
> ------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev
> _______________________________________________
> xbiblio-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
In reply to this post by rmzelle
I also updated the license conditions for the style repository, which seemed necessary, since the CC BY-SA license specifies that "[y]ou must attribute the work in the manner specified by the author or licensor".


In short, I think we should demand that any project using CSL styles from the repo should publicly acknowledge this, and that authorship/contributorship information shouldn't be stripped from distributed styles. Let me know if you think the text needs changes/polish.

Rintze

On Tue, Jan 3, 2012 at 6:20 PM, Rintze Zelle <[hidden email]> wrote:
Dear all,

As of this moment, all the CSL styles in the style repository at https://github.com/citation-style-language/styles are registered under a single license, using the exact string "This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/".

I added the license to styles that did not carry one, updated older versions of the license, and replaced ported variants by the unported version. I got permission of the style authors who had released their styles under by-nc-sa licenses to switch to by-sa.

Going forward I would like to require that any new style added to the repository should use Creative Commons Attribution-Share Alike (I already included this in our requirements: https://github.com/citation-style-language/styles/wiki/Style-Requirements ).

If anybody has an issue with any of these changes, please let me know,

Rintze

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Charles Parnot
Sounds good to me. Here is what our acknowledgment box says:

The following CSL stylesheets were contributed by different members of the CSL community, and are hosted at https://github.com/citation-style-language/styles. You can learn more about the CSL project at http://citationstyles.org/. Like the original files, the CSL stylesheets are included in Papers2 under the following licenses:
"This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/:"

Since there is only one license now, that's the only license listed now (in the upcoming version).

charles


On Jan 4, 2012, at 7:05 AM, Rintze Zelle wrote:

> I also updated the license conditions for the style repository, which seemed necessary, since the CC BY-SA license specifies that "[y]ou must attribute the work in the manner specified by the author or licensor".
>
> https://github.com/citation-style-language/styles/blob/master/README.md
>
> In short, I think we should demand that any project using CSL styles from the repo should publicly acknowledge this, and that authorship/contributorship information shouldn't be stripped from distributed styles. Let me know if you think the text needs changes/polish.
>
> Rintze
>
> On Tue, Jan 3, 2012 at 6:20 PM, Rintze Zelle <[hidden email]> wrote:
> Dear all,
>
> As of this moment, all the CSL styles in the style repository at https://github.com/citation-style-language/styles are registered under a single license, using the exact string "This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/".
>
> I added the license to styles that did not carry one, updated older versions of the license, and replaced ported variants by the unported version. I got permission of the style authors who had released their styles under by-nc-sa licenses to switch to by-sa.
>
> Going forward I would like to require that any new style added to the repository should use Creative Commons Attribution-Share Alike (I already included this in our requirements: https://github.com/citation-style-language/styles/wiki/Style-Requirements ).
>
> If anybody has an issue with any of these changes, please let me know,
>
> Rintze
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
> xbiblio-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

--
Charles Parnot
[hidden email]
twitter: @cparnot
http://mekentosj.com



------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
Perfect.

Rintze

On Wed, Jan 4, 2012 at 11:34 AM, Charles Parnot <[hidden email]> wrote:
Sounds good to me. Here is what our acknowledgment box says:

The following CSL stylesheets were contributed by different members of the CSL community, and are hosted at https://github.com/citation-style-language/styles. You can learn more about the CSL project at http://citationstyles.org/. Like the original files, the CSL stylesheets are included in Papers2 under the following licenses:
"This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/:"

Since there is only one license now, that's the only license listed now (in the upcoming version).

charles


On Jan 4, 2012, at 7:05 AM, Rintze Zelle wrote:

> I also updated the license conditions for the style repository, which seemed necessary, since the CC BY-SA license specifies that "[y]ou must attribute the work in the manner specified by the author or licensor".
>
> https://github.com/citation-style-language/styles/blob/master/README.md
>
> In short, I think we should demand that any project using CSL styles from the repo should publicly acknowledge this, and that authorship/contributorship information shouldn't be stripped from distributed styles. Let me know if you think the text needs changes/polish.
>
> Rintze
>
> On Tue, Jan 3, 2012 at 6:20 PM, Rintze Zelle <[hidden email]> wrote:
> Dear all,
>
> As of this moment, all the CSL styles in the style repository at https://github.com/citation-style-language/styles are registered under a single license, using the exact string "This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/".
>
> I added the license to styles that did not carry one, updated older versions of the license, and replaced ported variants by the unported version. I got permission of the style authors who had released their styles under by-nc-sa licenses to switch to by-sa.
>
> Going forward I would like to require that any new style added to the repository should use Creative Commons Attribution-Share Alike (I already included this in our requirements: https://github.com/citation-style-language/styles/wiki/Style-Requirements ).
>
> If anybody has an issue with any of these changes, please let me know,
>
> Rintze
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
--
Charles Parnot
[hidden email]
twitter: @cparnot
http://mekentosj.com



------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel


------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Robert Knight
In reply to this post by Charles Parnot
> In short, I think we should demand that any project using CSL styles from the repo should publicly acknowledge this,
> and that authorship/contributorship information shouldn't be stripped from distributed styles.
> Let me know if you think the text needs changes/polish.

I would suggest putting the licensing details under a separate heading
in the readme from the general information.
The attribution requirements sound fine to me.  We list the author
next to each style and credit the CSL language / citeproc-js in the
About dialog but not citationstyles.org itself.  I've filed a ticket
to resolve that.

Regards,
Rob.

On 4 January 2012 16:34, Charles Parnot <[hidden email]> wrote:

> Sounds good to me. Here is what our acknowledgment box says:
>
> The following CSL stylesheets were contributed by different members of the CSL community, and are hosted at https://github.com/citation-style-language/styles. You can learn more about the CSL project at http://citationstyles.org/. Like the original files, the CSL stylesheets are included in Papers2 under the following licenses:
> "This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/:"
>
> Since there is only one license now, that's the only license listed now (in the upcoming version).
>
> charles
>
>
> On Jan 4, 2012, at 7:05 AM, Rintze Zelle wrote:
>
>> I also updated the license conditions for the style repository, which seemed necessary, since the CC BY-SA license specifies that "[y]ou must attribute the work in the manner specified by the author or licensor".
>>
>> https://github.com/citation-style-language/styles/blob/master/README.md
>>
>> In short, I think we should demand that any project using CSL styles from the repo should publicly acknowledge this, and that authorship/contributorship information shouldn't be stripped from distributed styles. Let me know if you think the text needs changes/polish.
>>
>> Rintze
>>
>> On Tue, Jan 3, 2012 at 6:20 PM, Rintze Zelle <[hidden email]> wrote:
>> Dear all,
>>
>> As of this moment, all the CSL styles in the style repository at https://github.com/citation-style-language/styles are registered under a single license, using the exact string "This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License: http://creativecommons.org/licenses/by-sa/3.0/".
>>
>> I added the license to styles that did not carry one, updated older versions of the license, and replaced ported variants by the unported version. I got permission of the style authors who had released their styles under by-nc-sa licenses to switch to by-sa.
>>
>> Going forward I would like to require that any new style added to the repository should use Creative Commons Attribution-Share Alike (I already included this in our requirements: https://github.com/citation-style-language/styles/wiki/Style-Requirements ).
>>
>> If anybody has an issue with any of these changes, please let me know,
>>
>> Rintze
>> ------------------------------------------------------------------------------
>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
>> infrastructure or vast IT resources to deliver seamless, secure access to
>> virtual desktops. With this all-in-one solution, easily deploy virtual
>> desktops for less than the cost of PCs and save 60% on VDI infrastructure
>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________
>> xbiblio-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>
> --
> Charles Parnot
> [hidden email]
> twitter: @cparnot
> http://mekentosj.com
>
>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> xbiblio-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

rmzelle
Administrator
In reply to this post by rmzelle
Hi all,

Creative Commons just released their 4.0 licenses (see e.g.
https://twitter.com/dancohen/status/405331406622306304 ). IANAL, but
it is my understanding that we're free to upgrade all existing styles
and locales from CC BY-SA 3.0 to this license without having to
consult the original contributors. See
http://wiki.creativecommons.org/License_Versions#Compatibility_mechanism_in_BY-SA_licenses
, which says "Starting with the release of the 2.x license suites, CC
expanded compatibility by allowing contributions to adapted material
to be created under the same or later version of the original license,
including other ported versions of the same or later version of the
license".

I'm not really sure there are big advantages for us to upgrading to
4.0, but I think it would be a simple change to make if we wanted to.

Rintze

On Wed, Jan 4, 2012 at 10:05 AM, Rintze Zelle <[hidden email]> wrote:

> I also updated the license conditions for the style repository, which seemed
> necessary, since the CC BY-SA license specifies that "[y]ou must attribute
> the work in the manner specified by the author or licensor".
>
> https://github.com/citation-style-language/styles/blob/master/README.md
>
> In short, I think we should demand that any project using CSL styles from
> the repo should publicly acknowledge this, and that
> authorship/contributorship information shouldn't be stripped from
> distributed styles. Let me know if you think the text needs changes/polish.
>
> Rintze
>
> On Tue, Jan 3, 2012 at 6:20 PM, Rintze Zelle <[hidden email]> wrote:
>>
>> Dear all,
>>
>> As of this moment, all the CSL styles in the style repository at
>> https://github.com/citation-style-language/styles are registered under a
>> single license, using the exact string "This work is licensed under a
>> Creative Commons Attribution-Share Alike 3.0 License:
>> http://creativecommons.org/licenses/by-sa/3.0/".
>>
>> I added the license to styles that did not carry one, updated older
>> versions of the license, and replaced ported variants by the unported
>> version. I got permission of the style authors who had released their styles
>> under by-nc-sa licenses to switch to by-sa.
>>
>> Going forward I would like to require that any new style added to the
>> repository should use Creative Commons Attribution-Share Alike (I already
>> included this in our requirements:
>> https://github.com/citation-style-language/styles/wiki/Style-Requirements ).
>>
>> If anybody has an issue with any of these changes, please let me know,
>>
>> Rintze

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Rights/Authorship of Dependent Styles

Charles Parnot
Looks good to me.

On Nov 26, 2013, at 3:45 PM, Rintze Zelle <[hidden email]> wrote:

> Hi all,
>
> Creative Commons just released their 4.0 licenses (see e.g.
> https://twitter.com/dancohen/status/405331406622306304 ). IANAL, but
> it is my understanding that we're free to upgrade all existing styles
> and locales from CC BY-SA 3.0 to this license without having to
> consult the original contributors. See
> http://wiki.creativecommons.org/License_Versions#Compatibility_mechanism_in_BY-SA_licenses
> , which says "Starting with the release of the 2.x license suites, CC
> expanded compatibility by allowing contributions to adapted material
> to be created under the same or later version of the original license,
> including other ported versions of the same or later version of the
> license".
>
> I'm not really sure there are big advantages for us to upgrading to
> 4.0, but I think it would be a simple change to make if we wanted to.
>
> Rintze
>
> On Wed, Jan 4, 2012 at 10:05 AM, Rintze Zelle <[hidden email]> wrote:
>> I also updated the license conditions for the style repository, which seemed
>> necessary, since the CC BY-SA license specifies that "[y]ou must attribute
>> the work in the manner specified by the author or licensor".
>>
>> https://github.com/citation-style-language/styles/blob/master/README.md
>>
>> In short, I think we should demand that any project using CSL styles from
>> the repo should publicly acknowledge this, and that
>> authorship/contributorship information shouldn't be stripped from
>> distributed styles. Let me know if you think the text needs changes/polish.
>>
>> Rintze
>>
>> On Tue, Jan 3, 2012 at 6:20 PM, Rintze Zelle <[hidden email]> wrote:
>>>
>>> Dear all,
>>>
>>> As of this moment, all the CSL styles in the style repository at
>>> https://github.com/citation-style-language/styles are registered under a
>>> single license, using the exact string "This work is licensed under a
>>> Creative Commons Attribution-Share Alike 3.0 License:
>>> http://creativecommons.org/licenses/by-sa/3.0/".
>>>
>>> I added the license to styles that did not carry one, updated older
>>> versions of the license, and replaced ported variants by the unported
>>> version. I got permission of the style authors who had released their styles
>>> under by-nc-sa licenses to switch to by-sa.
>>>
>>> Going forward I would like to require that any new style added to the
>>> repository should use Creative Commons Attribution-Share Alike (I already
>>> included this in our requirements:
>>> https://github.com/citation-style-language/styles/wiki/Style-Requirements ).
>>>
>>> If anybody has an issue with any of these changes, please let me know,
>>>
>>> Rintze
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> xbiblio-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

--
Charles Parnot
[hidden email]
http://app.net/cparnot
twitter: @cparnot


------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
xbiblio-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
Loading...