Showing posts with label licensing. Show all posts
Showing posts with label licensing. Show all posts

Monday, November 02, 2026

Unlike the complete MediaWiki software stack, AI is not freely licensed

One of the cornerstones of our processes in the Wikimedia world are its licenses. Both he content and the software is freely licensed. It is why artificial intelligence companies are enabled to use all of the Wikimedia content for its training material.

The functionality of  AI products are not freely licensed, not for its software nor for its content. As relevant is that American models cannot be altered while some of the Chinese models can be altered. It follows that Chinese models are more open.

I have observed that so far American AI is used. However, the USA considers AI strategic and as a consequence AI functionality provided by USAmerican compnies is not globally available. This is in stark contrast with how the Wikimedia foundation has always maintained its ethics.

We should use for instance the Chinese DeepSeek functionality because we can adapt its functionality and we can make it available to all our communities.

Thanks,

        GerardM

Sunday, May 27, 2018

#Wikidata - No #copyright on common knowledge

The approach on copyright for text and data is imho utterly different. For your text you seek a reputable source, you cite it. All in all a lot of work.

A proper approach to data is that you seek confirmation on what you already know and it is encouraging when there are many sources that agree on what is common to all of them. When you add new data, typically most of what you care for you will find through links from existing shared data probably in multiple sources. This is not done by hand, too much work, it is done by bot and consequently there is not even some "sweat on the brow".

Arguably, common data exists as common knowledge. It is not proprietary to any one of these sources and consequently claiming copyright let alone a license is at least problematic.

When data is specific to one data source, it is inherently problematic. It may be wrong, particularly when it differs from what other sources state. It follows that there is a need for care before this data is used. You then get into a manual process of reconciling and curating the data, you may even decide to diverge from what all the others say. The confirmation and the creation of new data both is actually research. It is not the using of data from the other source. In my mind this means that there is no burden of copyright applicable.

When data is considered from Wikipedias for Wikidata, the same considerations apply. When you think about it, it is quite bizarre; you take expressions in words and convert it into a qualifier that represent said words, words that can be in any language. Words that may not even be what you see on your screen. The processing of texts may be automated and, it is easy to understand that from the input of all the Wikipedias alone a superset of data is created that is more than any one article. The notion that copyright can be legitimately claimed is problematic at best.

When you take all this on board, and the fact that individual facts cannot be copyrighted, it is obvious to me that the choice for a CC-0 licence for Wikidata is fortunate. A license implies copyright but it is given away with this licence. The claim of the copyright is at best a defensive strategy.
Thanks,
       GerardM

Saturday, June 25, 2016

#Wikidata has a CC-0 license. This should not change II

Wikidata is becoming a repository where people may choose to share their data .. or not. When they do not want to share their data with Wikidata, it is their choice and that is fine.

The bottom line of copyrights for databases is that single facts cannot be copyrighted. It is only the whole of a database that can be under a copyright. When you look at the data of Wikidata and its structure, it is in many ways a reflection of all the Wikipedias. Increasingly its data finds its way into Wikidata and as a consequence data that may be found in a specialised database gets included in Wikidata.

Wikidata also has the habit of including identifiers to external sources on an item level. As a consequence people can see what other sources have to say about the same source. It also enables bots to make a comparison. When it writes a report about the differences, it is original research and consequently it does not violate any copyright. When based on such a report people make changes, it takes an effort to find what is correct and consequently it does not violate copyright either. When an agreement is in place, it is possible to add missing data to Wikidata. When done properly there will be an attribution of the original source and, when it is done by a bot, it may be a bot dedicated to that resource.

The objective of the Wikimedia Foundation is to share data. This is why it makes so much sense for Wikidata to have a CC-0 license. As the quality improves, as more and more comparisons are made and the differences are reconciled the data becomes more valuable. Given its scope, not much is out of scope and it is obvious that Wikidata needs to include data from other sources wholesale. It may get information in so many ways. With the CC-0 license it is obvious. Use our data, compare our data, improve our data and this will bring more power to us all.
Thanks,
      GerardM

Wednesday, May 04, 2016

#Wikimedia - [[citation needed]]


Our articles in any #Wikipedia can be trusted when an effort has gone into providing sources. Sources or citations are very much needed because help us distinguish fact from fiction. Finding sources exposes an origin and it helps us debunk fiction. The result of this continued effort is content that can be trusted as a sincere attempt to achieve a neutral point of view.

There are very practical problems. Sources are not always easy to find and they do not exist in every language. Sources are often behind a "pay wall” making access to the body of knowledge is very much restricted. Sources, particularly sources on the web do not exist forever. The consequence is that sources are problematic and, not everybody is equally able to help us with sources for the content we have.

When we are to improve the current, unsatisfactory situation we have to address multiple problems.
  • Once sources are lost we rely on the internet archive for an historic view. It has policies that allow for the removal of content and this is often the content that is controversial and removal is often intended to rewrite history. What to do?
  • Access to restricted sources is provided to the privileged few who have access to libraries. The WMF has a program that enables some of our editors access to a few pay-walled sources.
  • When this proves insufficient, it is great to know that  Sci-hub among others provides “illegal” access to any and all sources.
Open access to sources is very much what we as a community care for. One of our own died in the struggle for this access so I do not think we should be deferential to an industry that is despicable. We should teach people how to find sources and ignore licensing as much as possible.
Thanks,
      GerardM

#Wikipedia / #Commons - Brigadeer General Loree K. Sutton

Mrs Sutton is psychiatrist who is a specialist on PTSD. When you read her CV, it is impressive. She no longer works for the US Army, she works for the City of New York.

When you read the article on Wikipedia, you find her picture. It is marked as Public Domain and it is not on Commons. Given that Wikidata is working towards the point where copyright and license information one can only hope that images like this can be easily shared based on the license.

When Commons started, it was intended as a repository that prevented the same file to be uploaded to all the Wikipedias. As such it served its purpose remarkably well. With Wikidata it becomes trivial to share images like the one of Mrs Sutton.

I fear that for some this reads as frightening. It undermines the one thing they love. It actually does not need remove the need for Commons as a platform. Quite the opposite; it will bring new tools to finally leverage all the data on images. It may bring this image of Mrs Sutton to Wikidata for starters.
Thanks,
      GerardM

Thursday, April 17, 2014

#Wikimedia #Commons - Mr Tadeusz Łobos

The picture that illustrates the article about Mr  Łobos is licensed under the CC-by-sa license. Consequently it is a picture that should be available for use in Wikidata. It is not because it was not uploaded to Commons.

When a picture like this one is to be made generally available, it has to be uploaded again to Commons. It is a hassle and another round of bureaucracy will decide if this picture may remain at Commons.

There are many pictures that should be generally available and are not. In a similar way there are many pictures that are considered to be not generally available and as a consequence are no longer available at all.

All media files are equal in that they are in need of the same quality of meta-data and they are all equal in that their copyright and license situation is the same never mind where they have been uploaded.

The consequence is that the scope of a Wikidata approach to media files should not restrict itself to Commons.
Thanks,
       GerardM

Wednesday, November 20, 2013

#Wikidata & #Freebase - an #interview with Denny Vrandečić

When Denny signalled the availability of data that links Wikidata to Freebase, there was a lot of follow up and several questions were left unanswered.  So I asked my questions and, I am happy with the answers I received. So enjoy this interview about the Wikidata and Freebase connection. 
Thanks,
       GerardM

By moving to California you embrace yet another culture, language.What does it do to you, your family
My wife is from Uzbekistan, I am from Croatia. We met in Israel. She has lived the last few years in Estonia, I in Germany. We have moved to California, and we are very excited about this move. Finally to live in a country where we both speak the language! And also, we have high hopes with regards to the weather.
The US in general, and San Francisco in particular, is a real melting pot - or rather fruit salad, as they say these days - of people from all over the world. This seems to be a good match to our own background, so we are looking forward to see what this will mean for us.
What is your job description and title at Google (and what is it you actually do)
My job title is "Ontologist". I am working on Google's Knowledge Graph. The Knowledge Graph for Google is basically what Wikidata is for the Wikimedia projects: a repository of structured knowledge about the world, that is used in many different ways in various different applications. I am working, together with a great team, on the schema and ontology of the Knowledge Graph: its data model, schema, and the way it captures and represents knowledge.
What is Freebase and how does it compare with Wikidata
Freebase is the publicly available and editable part of the Knowledge Graph. Freebase and Wikidata are very similar. At the same time, there are quite a few differences: the user communities, the incentive architecture, the license, the way sources and knowledge diversity are handled, to name the big differences. There are also minor differences in the data model, the way classes, properties, types interact with each other, the UI, the workflows, the prominence of internationalization, currently also the size and scope of the knowledge bases, etc. Wikidata currently has 22 Million statements, Freebase has 2 Billion facts. Now one should always be careful with such simple metrics, and especially these numbers are not comparable, but it hints at some differences in the knowledge base.
Do you work on FB or is this only an outward facing project
Freebase is a part of the Knowledge Graph, and I work on the Knowledge Graph, so yeah, I also work on Freebase.
With a link between FB and WD it will be possible data can flow from WD because of its license. How is it for a flow from the other direction
I am not a lawyer, but unfortunately it seems that the licenses used by Freebase and Wikidata would not allow for that direction. We are aware that this is not good, and we are working on ways to fix this.
But even without actually letting data flow from Freebase to Wikidata, such an alignment can be valuable for the Wikidata editors: bots could compare the data, and flag inconsistencies. Bots could do simple comparisons, like, go through all the countries, compare the capitals, and report on the differences. And this can be done not only with Freebase, but with any other structured or semi-structured base that Wikidata connects to. One example is the work that Maximilian Klein did, comparing the sex/gender of authors connected through the VIAF ID.
The data for the FB<->WD connection is based on a WD dump, How will it be maintained in the future 
This is not decided yet. In principle, we could create this dump regularly, but I am unsure if this will be needed. We will have to see how things develop before deciding on what to do next.
When info exist in both WD and FB and it differs, what would you like to see done
The difference to be fixed, obviously! Both knowledge bases may and do contain errors, and the ability to compare them can lead to an increased quality level in both. It is obvious that the respective communities should take care of such errors in their knowledge bases. By providing links between the knowledge bases, this should get easier to automate.
Would that be a model for collaboration with other sources like VIAF
Yes, in many cases that should work. It is clear that some sources and their communities are more open to corrections than others. Wikidata can become a central hub for identity on the Web, collecting and reconciling IDs from many different sources. What makes Wikidata so interesting in itself is its commitment to let everyone share in the sum of all knowledge - both in participating in creating it as well as in accessing it. The barriers are so much lower than almost anywhere else. In which other knowledge base can you easily fix an error?
Does FB have sources for its statements
Yes, but this is quite a different notion from what Wikidata does with sources. When a dataset is being uploaded to Freebase, the source for this upload is usually recorded. It is closer to what is usually called "provenance", whereas Wikidata's notion of a source is closer to what is called a "reference", an external authority that makes the given claim. A strength of Wikidata is the diversity of the sources, and that they can be refined later by the community. A statement in Wikidata can have several sources (which makes sense if you think of them as references supporting the statement), but in Freebase every statement only has one source (which again makes sense if you think about it being the provenance of that statement, from where this statement came from).
spot the differences
What do you prefer, no diffs or sourced diffs
(I don't understand the question, and rephrase it to: do you prefer an unsourced statement over no statement?)
In most cases, yes, I'd rather have an unsourced statement than no statement at all. In a perfect world, all statements in Wikidata would have great, authoritative sources. But for now, I really think that Wikidata should be lenient with regards to unsourced statements in most cases. There are obvious cases where this is not true: data about living persons has to be more carefully sourced, especially when it has the opportunity to hurt the person. Also, we have to remember, that a Wikipedia community can decide to use a statement from Wikidata only if it is sourced, and to drop it otherwise. Once Wikidata has matured a bit, I expect it to move towards a more stricter policy, and to see tools develop that help with getting there. That will be a quite exciting time.
What FB feature would you LOVE to have in Wikidata
The expressive query features of Freebase. The Wikidata team is hard on working towards enabling this, and I am very much looking forward to see it happen: this will open a whole new world of possibilities for everyone using Wikidata's data, and it will lead to much more visibility of the data and help to refine the Wikidata properties.

Wednesday, October 23, 2013

#SignWriting is free to use - please use it and publish with it! ;-)

This message so deserves to be heard far and wide. So I make use of the license and republish :)
Thanks,
      GerardM


SignWriting List
October 23, 2013

Dear SignWriting List -
Did you know that you all have my FULL permission to use and publish with SignWriting and Sutton Movement Writing? Some of you know that, but in our crazy world not everyone can believe it ;-)

Sometimes I receive emails from people who want so badly to use SignWriting, but are fearful that I will be mad at them if they use it…they want legal proof that they have permission to use the system. I feel sad when I receive those emails because I want so much for people to use the system freely, and there are no restrictions whatsoever… of course I always give my full permission.

I encourage you all to use the materials on our sites freely and to write freely in all of your languages… and then in return I am delighted to post your new work using the system…it is a great sharing of information …. 

Have you heard about the free contracts or licenses now available on the web to help people feel secure and not concerned? They are "free licenses" with logos that can be placed on a web site that shows that the information on that web site is free to use… apparently these free licenses are an easy way to communicate "permissions" ...

Therefore, I am showing you here the three free licenses I have chosen for our web sites and for our system…they are all free licenses….meaning that nothing has changed….You were free to use it before, and you are free to use it now …. But the licenses simply state this officially. You can find these licenses as the bottom of signwriting.org, for your information:

Tuesday, October 08, 2013

Hassanal Bolkiah, the Sultan of #Brunei

The #Commonweath has a new repository of images. It includes many interesting images like the picture to the right of the 29th and current Sultan and Yang Di-Pertuan of Brunei.

There are many pictures available and partcularly when they are used for educational use, you should have a look. Sadly, for use in Wikipedia these pictures are off limit as they are not freely licensed.

The way it works is, 
  • you create yourself a profile
  • you select the pictures you are interested in
  • you indicate what you will use the pictures for
  • you wait for permission to use them
  • you download the picture
  • you add an attribution
Compare this with the pictures of Mr Hassanal Bolkiah on Commons; 
  • this is the category of pictures of the Sultan
  • you select one of the pictures like this one..
  • you download the picture
  • you add an attribution
Thanks,
     GerardM

Wednesday, September 11, 2013

#SignWriting organisation adopts #CC-by-sa

The problem with "#Free content" is that some people do not appreciate its meaning. Free means: you can do whatever you like with this. The problem these people face is that they apply what their understanding of copyrights is and insist on a license.

Only for these people, the CC-by-sa license has been added. It is to make sure that it is understood that all the information is there to be used. It is to make sure that you can and are encouraged to make it your own and adapt it as you see fit.

For everyone else, there is no way where the SignWriting Foundation will enforce the legalities of the license. Yes, it is nice to be acknowledged but please do share SignWriting as widely as possible because it is a gift to be able to write the language you sign. You are *FREE* to write without any thought or any further consideration. Please do write your sign language.
Thanks,
       GerardM

Tuesday, May 15, 2012

Legacy projects II

When tools are no longer maintained, when they are no longer promoted, they die. The good news is that the tools created for the Myanmar language created by Keith Stribley have found a new home.

The question is to what extend are they salvageable and is it worth the effort. For software there are two primary considerations; copyright and licensing and, the source code.


Without source code the first question is less relevant and, the reference to the mercurial repositories is a reference to Keith's old website. This old website is gone. There are references to the CC-by-sa license on some pages but for software such a license is not really appropriate.

When you look at the subjects Keith covered, they are still very much relevant and impressive. At the Myanmar Wikipedia two out of three webfonts do not work for me. We do not have an input method yet. It will be great when we find that the tools Keith created can find another use.

The result of my previous post is this update. I hope that there will be a future update to this post bringing you more positive news.
Thanks,
     GerardM

Sunday, March 18, 2012

The #Santali language and the Ol Chiki script

At first the Santali language was hardly written and when it was, it was written in the Bengali alphabet, Oriya alphabet, or the Latin alphabet. As Santali is not an Indo-Aryan language (like most other languages in the north of India), Indic scripts do not have letters for all of Santali's phonemes, especially its stop consonants and vowels, which made writing the language accurately in an unmodified Indic script difficult. 


The  Ol Cemet', Ol Chiki or simply Ol was created in 1925 by Raghunath Murmu specifically for the Santali script one letter is assigned to each phoneme.

A Wikipedia has been requested for the Santali language and it will be localised in the script that is popular with most people. Apparently this is the Latin script. This does not mean that the Ol Chiki script is not relevant for use within a Santali Wikipedia.

There is a font that is available for free. Sadly it is not available under a free license. Finding the copyright holder for these fonts allows us to request a change of the license. Once the license is changed, we can make the font available as a web font.
Thanks,
     GerardM

Wednesday, July 06, 2011

#CTM11 Museums do not pay license fees

A museum in Belgium specialised in modern art was send a bill for 6000 EURO per annum to pay for using images of art in its collection on its website.

Guess what: they shut down their website removed all the offending imagery and despaired a bit. A museum makes the name of an artist, when an artist can be found in a museum his value increases.

The one reason for not paying the license fee is because a typical museum does not have the money for such silliness. If an artist wants to be known, it has to license its collectors for their work. That is how they make their name. The money through license fees is a pittance anyway when you deduct the administrative cost.

Really license fees are a pain, a pain that hurts. A pain that prevents artists from making their name. A pain preventing artists from finding their public.
Thanks,
      GerardM

Sunday, May 01, 2011

#Copyright and the family album

The #Wikipedia articles on Alice Ricciardi-von Platen do not have an illustration. When my friend Jan Velterop asked me for help getting her article written, I asked him if he could get me a picture.

Alice von Platen

This picture of a young Alice was taken probably in 1939. The photographer is unknown and this picture was taken from a family album with the intention to make it publicly available. If there must be a copyright, it would be licensed as CC-sa but for all intends and purposes it can be considered to be in the public domain.
Thanks,
      GerardM

Wednesday, April 06, 2011

What is the point of publishing cultural heritage on the web

A rich resource with material about the Dutch cultural heritage published a new website. The "Rijksdienst voor het Cultureel Erfgoed", a Dutch governmental organisation is quite pleased with its new website.

It has reason to be pleased because they bring half a million photos to the web. These are taken in the last sixty years. In addition to this there are drawings and maps of buildings.

The sad thing is that all this material is hidden behind a paywall. When you buy pictures, there is a further restriction because of its licence (cc-by-nc).


This picture of a church in Diever was drawn by C. van Noordt in 1756 and sadly the license is said to be applicable here as well. When you part with your money, you get not even a truly high resolution scan.

While I am happy with the existence of these digitisations, there are issues and missed opportunities:
  • the license prevents cooperation with Wikipedia
  • the claim of a license on material that is in the public domain is copyfraud
  • the low resolution does not lend itself for digital restorations
  • tax money is wasted because the public does not benefit from this public work
The Dutch government makes our cultural heritage available in this way and they provide a substandard product for commercial purposes. They are happy because they make all this material available but because of the license chosen it is not available for use in education. I hope that the Rijksdienst will study the examples of the Library of Congress and closer to home the Tropenmuseum to learn that it can be done differently.
Thanks,
      GerardM

Tuesday, November 30, 2010

#Copyright and #GLAMWiki

Pictures on #Commons have two purposes; the use as illustrations on Wikimedia projects and, the use as illustrations elsewhere. Most of these pictures place requirements on the user like attribution. Many people do not bother with such stuffiness. Many Wikipedians can get quite incensed about that particularly when the media is used for a commercial purpose.

Magnus Manske did a great job making it easy to use pictures from Commons. As you can see, nice icons that provide different ways of using the wealth that Commons has to offer.


When you use a picture "on the web" like I did recently in this blog post, you are provided with a neat attribution to the copyright holder and with a nice indication of the applicable license.


This is absolutely fabulous but still, there are a few things that would make it absolutely awesome..
  • Show the license information on the Wikimedia projects as well
  • Having these share options on the wikis of all Wikimedia projects
  • Having the copyright message in the language of the Wiki, or a language that can be selected
  • Including information about the GLAM that has it in its collection
For our GLAM partners the traffic numbers of their collection on our projects is important as is the number of articles their pictures are used in. References to the GLAM who has something in collection is important to us to us and vital to them.

We are adamant that citations are used to assert the validity of facts. It is how we provide a reason why our articles can be trusted. A similar assertion is needed for illustrations; Jimbogoesswimming.jpg is not the 1873 image by William-Adolphe Bouguereau that can be found in the Sterling & Francine Clark Art Institute in Williamstown, Massachusetts.

William-Adolphe Bouguereau (1825-1905) - Nymphs and Satyr (1873)

This picture does not attribute the Clark and neither does the one on the article about nymphs on the Esperanto Wikipedia. It is relatively easy to recognise the GLAM that conserve a work like this. Such recognition makes a massive difference to our GLAM partners who struggle to maintain their collection and who need recognition to justify their partnership with us.
Thanks,
      GerardM

Wednesday, October 27, 2010

Stimulating the #Commons stock photo functionality

A company that sells pictures, makes sure that they have visually stunning images that can illustrate the most weird and wonderful subjects. Take a subject like dyslexia; how to illustrate this? A friend send me this wonderful example of a photoshopped picture that does this really well.


When you read the Wikipedia article, there is no illustration. This is where visually stunning pictures that express the issue are needed because this article is factually correct, it is hard reading with the key facts hidden behind all kinds of classification.

Stock photography is about illustrations. When there are many pictures that illustrate a subject, it is indeed the most visually attractive picture that will be sold. When you seek an illustration, you will find that historic pictures are an important part of a collection. They are because they provide a view that is no longer there.


With the arrival of sharing options at Commons, we have the opportunity to strengthen its stock functionality. With over 270 Wikipedias our own need for multiple pictures for one subject is intrinsically high.

Commons is slowly becoming a stable source of freely licensed pictures. We have the opportunity to make it the "goto" place for quality illustrations. With 7,626,589 freely usable media files, the basis for such a function exists. What is left is profiling and marketing us as a source for great illustrations.
Thanks,
        GerardM

Thursday, September 30, 2010

#UK Open Government License


The news is good. It is even great. The question is: "now what? " It is not a Creative Commons license. It does have all the things that you find in the CC-by-sa license with some extra bits.

These extra bits make sense in a way; you are not to pretend that your use of the data has the approval of the UK government. You are also not allowed to mislead others or misrepresent the information or its source. The problem is, that spinning data is what governments and politicians do. I do believe that when a "misrepresentation" is truly problematic, the law does allow for legal sanctions.

The question is: will UK governmental data licensed in this way be usable in Wikipedia.
Thanks,
      GerardM

Wednesday, September 29, 2010

Using #Wikimedia #Commons for stock photography

Illustrations are a vital ingredient of blogs. The promotion of the freely licensed content of Wikimedia's Commons is important because we want people to use our illustrations, our maps, our photos. Use them outside of Wikipedia, use them in project, use them on blogs.

Grote Grazers

On this blog I prefer to use pictures from Commons however, I cannot be bothered with all the associated crap I should do. Thanks to some clever work by Magnus Manske, I am now able to have the picture in my blog and, have some license indications as well.


For my favourite picture I changed some values on the example Magnus provided to let you share my picture of big grazers. As you can see, there are many options available for reuse. This functionality is a big improvement and it deserves to be implemented so that we can promote Commons and have an added incentive for people to upload their work so that we have even more pictures to choose from.
Thanks,
        GerardM

Saturday, June 26, 2010

#ASCAP undermines its own foundation


ASCAP advertises itself as the "worldwide leader in performance royalties, service and advocacy for songwriters, composers and music publishers". Fine. The basis of performance royalties is copyright. In order to legally extract payment there is a need for a license that insists on this. There is a quid pro quo; you sell a license to me and I pay you money.

To grant a license is the prerogative of a copyright holder. ASCAP is an organisation that is owned and run by "songwriters, composers and music publishers" and as such they have a monopoly by their own admission. Recent publications indicate that ASCAP is raising funds to fight organisations like Creative Commons.

What they seem to forget is that it is the copyright holder that decides what license to give to its work. When this connection is lost, when ASCAP takes the position that music must mean royalties and royalties to be paid to ASCAP, they clearly behave like a monopolist.

The record of organisation like ASCAP is less then stellar. There have been frequent law suits intended to get major amounts of royalties paid to the rights holder.

PS it is odd for a music related website where no music is to be heard.
Thank,
     GerardM