[od-discuss] City of Calgary Open Data License Approval Request

Simbirski, Walter Walter.Simbirski at calgary.ca
Tue Mar 19 18:15:20 GMT 2013


Kent,

Thanks for your response and good points on the non-reusable licence issue. I think this goes along with Andrew's comment about separating the terms of use from the data licence and this will need to be addressed.

Again, with respect to the internal/external review process the City has already internally reviewed its licence on more than one occasion. I'm not opposed to another internal review but I am trying to understand the shortcomings  with the existing licence before initiating this. I understand your desire for everyone to use the same licence and I'm in favour of that as well. Working together towards that goal is one of the reasons I've joined this discussion group. But you also need to consider how any future changes to an OKFN endorsed licence, no matter how minor, would impact the users of that licence especially if they are using a reusable version of the licence. I'm aware of the tremendous amount of effort that went in to the Creative Commons licences but there is no guarantee that these are immutable.

At this point the City of Calgary has a licence that it feels meets the requirements of an open data licence and the users of the data that we have canvassed are satisfied with it as well. Making a wholesale change would require a compelling argument.

Thanks,

Walter

From: od-discuss-bounces at lists.okfn.org [mailto:od-discuss-bounces at lists.okfn.org] On Behalf Of Kent Mewhort
Sent: 2013 March 19 11:10 AM
To: Simbirski, Walter
Cc: 'od-discuss at lists.okfn.org'
Subject: Re: [od-discuss] City of Calgary Open Data License Approval Request

Hi Walter,

I can understand where you're coming from about the the lengthy process for a city legal department to approve a new licence and I see your point that a review process could help the process.  The problem from my perspective though is that these legal department approval processes have, unfortunately, been going a bit awry in Canada.  From the start, even the first "G4" city licences -- all based on the same Vancouver licence text -- weren't compatible with one another.  Each city's legal department made their own tweaks and legal strokes-of-hand for further protection, resulting in similar but not-quite-compatible licences.  From there, as more cities  have commendably got on the open data train, the licencing proliferation problem has only become worse.

I'd strongly suggest that the internal review process should coincide with external review processes such as the OD procedure.  This way, problems can be fixed -- and suggestions, such as using a similar international licence can be made -- before the drafts become final versions.

Also, the reason I suggest it's a non-reusable licence is because of the very fact of the "hard-coded" entity and jurisdiction. If I wanted to apply the Calgary licence to my own work, I couldn't simply provide a hyperlink to it with a statement that "This Work is licenced under the City of Calgary Open Data Licence". If the city licence used more generic terms such as the "Licensor" or "Author" and, if necessary choice of law in the "jurisdiction of the licensor', other cities looking to apply a similar licence might instead just directly use the City of Calgary licence -- thereby reducing licence proliferation.  I'm not so sure I could even just change the hard-coded entity title, as the city owns the copyright in the actual legal document with no permission granted to re-use the text.

Kent

On 13-03-19 04:44 PM, Simbirski, Walter wrote:
Hi Kent,

I agree that the current OD procedure should change for all the reasons you give and I would certainly support such a move.

If the City of Calgary were creating a new licence  it would be counterproductive to create a "vanity licence" and then ask for a review but you are assuming that the CC licences are "long-established" in comparison to the City of Calgary licence. The City of Calgary licence was created in 2010 and modified in 2011 based on what was happening in the Open Data world at the time. When the licence was created (and modified) the CC licences were not in the same state they are in today and there was much public discussion around alternate Open Data licences as well.  The City of Calgary licence incorporated much of what was in existence but there were no clear leaders at that time.

You are also assuming that it is an easy matter for us to replace the existing license with one that is popular and long-established but that is not the case. This will require review and approval by the City's legal and intellectual property departments and this can be a time consuming process. In order to begin this process it will be helpful to know what elements of our existing licence are unacceptable.

I am also not sure why you call our existing licence "non-reusable". The reference you site states: "Licenses in this group are specific to their authors and cannot be reused by others. Many, but not all, of these licenses fall into the category of vanity licenses". I think that the licence could be used by any government body simply by substituting the legal entity and jurisdiction.

Thanks!

Walter



From: od-discuss-bounces at lists.okfn.org<mailto:od-discuss-bounces at lists.okfn.org> [mailto:od-discuss-bounces at lists.okfn.org] On Behalf Of Kent Mewhort
Sent: 2013 March 19 1:51 AM
To: 'od-discuss at lists.okfn.org<mailto:od-discuss at lists.okfn.org>'
Cc: Simbirski, Walter
Subject: Re: [od-discuss] City of Calgary Open Data License Approval Request

Walter, I disagree that the " the question is not why the City of Calgary finds it necessary to have a special license but whether the existing license is acceptable as is, can be made open with minor modification, or should be abandoned in favour of what is currently being recommended".  Perhaps this is technically true as per the current OD procedure and the definition itself, but I think this may need to change.

Sooner or later, we'll need to have some type of policy to deal with licence proliferation.  The growing list<http://clip.cippic.ca/license-list.php?cat=Canadian> (already in the dozens) of municipalities and other government bodies in Canada who are coming up with their own custom licences is a disconcerting and increasingly problematic trend.  The Calgary licence is just one of many Canadian municipal data licences that could easily be replaced with a suitable standard licence.  It's also likely the approval of one will just open a flood gate of every other city in Canada requesting similar approval.

The OSI's report on licence proliferation<http://opensource.org/proliferation-report> could be a good starting point for a policy here, and their justification hits the nail on the head:
"While it might at first sight not seem appropriate for the popularity of a license to be significant in categorizing it, popular and long-established licenses have an important thing going for them: the existence of an established interpretive tradition and a well-developed set of expectations about correct behavior with respect to them. This is significant in reducing confusion and (especially in common-law countries) is even likely to condition judicial interpretation of the licenses."

These non-reusable licences, such as the one the City of Calgary is using, are typically called "vanity licences" because they're akin to vanity licence plates: there's no real justification for them other than the branding of one's own name into the licence and a feeling of control over the labels and text.  I'd like to see much more justification for the special needs of the City of Calgary justifying a special licence.

In fact, overall, I'd suggest that a good procedural policy would be a reverse burden that requires anyone requesting a licence review to justify why CC, ODC, or, at the very least, national government licences, are not a suitable fit.  Even without having a strict requirement for a licence to differ, a procedural step of needing to adequately justify the differences will at least encourage licencors to look at, and better consider, these existing options.

Kent


On 13-03-18 08:21 PM, Simbirski, Walter wrote:
Hi Andrew,

Thanks for your response.

In order to understand why City of Calgary would find it necessary to have a special license  it should be noted that the current City of Calgary license is well over a year old, which may not seem very old but it predates some of the other licenses. So the question is not why the City of Calgary finds it necessary to have a special license but whether the existing license is acceptable as is, can be made open with minor modification, or should be abandoned in favour of what is currently being recommended. We are currently undergoing what should be a major overhaul of our Open Data Catalogue and reviewing all aspects of the catalogue including the license.

With that in mind I would answer your questions as follows:


1.       Limiting the liability of the City would be a simpler and better - agreed.

2.       The "any lawful use" clause is to make it clear that the City of Calgary does not endorse the use of the data in a manner that would be deemed unlawful. The issue of jurisdiction may be problematic but we felt this was less restrictive than a clause such as, "You must not distort, mutilate, modify or take other derogatory action in relation to the Work which would be prejudicial to the Original Author's honor or reputation", that is part of the current Creative Commons License Legal Code (section 4.c  http://creativecommons.org/licenses/by/3.0/legalcode ).  We did not want to be viewed as limiting the user's right to criticize the City of Calgary.

3.       This is actually two issues - the first being that the user would be bound by later changes to the license and I agree that this should be replaced with a statement granting perpetual use under the license applied at the time of download. The second issue is the one of attribution and, again, it relates the Creative Commons legal statement identified in item 2 - we felt that we would not restrict users from using the data in a manner that might be prejudicial to the City's honor or reputation, provided such use was lawful in nature,  but we also didn't want it to appear that the City was endorsing products that could be viewed as immoral or as a conflict of interest even though they may be lawful in nature.

4.       Agreed. No such restriction exists with any data sets available today but we felt that in the future such data sets could be  made available directly or indirectly through the Open Data Catalogue. One of the reasons for this exercise is to obtain permission to use the OKFN's OPEN DATA button which would provide a readily identifiable means of distinguishing truly open data sets from those which may have restrictions.

With respect to your statement:

[2] Note that CC-BY 3.0 actually allows the licensor to make the attribution optional, if that is what you want.  It also has provisions about what to do if there would be a lengthy list of attributions in a "collection".

Sorry - I'm not seeing that in the CC license. I'm not sure what I'm missing.

Again - Thanks for taking the time to respond.

Walter



________________________________
NOTICE -
This communication is intended ONLY for the use of the person or entity named above and may contain information that is confidential or legally privileged. If you are not the intended recipient named above or a person responsible for delivering messages or communications to the intended recipient, YOU ARE HEREBY NOTIFIED that any use, distribution, or copying of this communication or any of the information contained in it is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and then destroy or delete this communication, or return it to us by mail if requested by us. The City of Calgary thanks you for your attention and co-operation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/od-discuss/attachments/20130319/fabc32c0/attachment-0001.htm>


More information about the od-discuss mailing list