I love #Wikidata, it gets so many things right. At the same time it fails by design. Consider; there is this article about a woman. In English she may have a spouse. In translation there is a problem; because the spouse has a spouse and it is a different word depending on the gender of the person involved.
This is the kind of problem that has been solved for the MediaWiki software. It means that you consider the sex of the person involved. Applying this principle on Wikidata is possible because we do register if a person is male or female.
It seems obvious; sex matters. In many languages you address people based on their sex. As long as Wikidata is not able to address this issue, it is broken. When this is intentional, it is broken by design.
Thanks,
GerardM
Sunday, April 28, 2013
Thursday, April 25, 2013
#OmegaWiki works and so can #Wikidata
OmegaWiki provides functionality that is on the agenda for Wikidata. The OmegaWiki community has ALWAYS wanted to be a Wikimedia project.
What it already provides is:
What it already provides is:
- links to Wikipedia articles in other languages when the article does NOT exist in the preferred language
- links to a commons category associated with a concept
- a picture painting the thousand words associated with the concept
Yes, it is quite shocking; it also provides multi lingual dictionary support. OmegaWiki has even been described in a book on the development of lexicography.
Both OmegaWiki and Wikidata are "right in front of us" and, the functionality described above is imho "right for us". The challenge we face is to do something that is "shockingly rare"; meet halfway.
The road towards such a meeting could be:
- Adopt OmegaWiki by the WMF in a labs kinda construction
- Create the logical requirements of OmegaWiki data in Wikidata
- Convert the OmegaWiki content to Wikidata technology
- See how it fits in the big picture
- Make it fit in the big picture
We do not need much talk and, the amount of work needed is relatively minor. The benefits are legion because even when all the OmegaWiki data is not used in the end, the lessons learned will be.
Thanks,
GerardM
Machine translation for #Wikipedia
The Wikimedia Foundation suggests that machine translation is the kind of infrastructure that makes sense to it. Given what it aims to do: making knowledge available to everyone, this makes perfect sense. A lot of translation has already been going on in order to fill many gaps in the many Wikipedias and machine translations were often an important part of this.
One of the arguments why the WMF could enter the fray is that it has something to add. It does have monetary reserves but more importantly it has several resources that may make a difference. The biggest two are Wikipedia itself and the other are its awesome communities.
When translating a Wikipedia article, the concepts that are specific to a subject are likely to be found in that article. Similarly when such concepts have their own article, they will contain a similar set of concepts. Combine this with a multi-lingual dictionary build with Wikidata technology along OmegaWiki lines and it will be relatively easy to find the corresponding expressions in articles in different languages on the same subject.
The point here is that the meanings of words do not exist in a vacuum.
When such concepts have been identified and linked to Wikipedia articles and dictionary meanings it becomes possible to help people understand a text in a different language by providing native language support.
<GRIN> I know Erik Moeller has a lot of experience in this field and I know mutual friends are quite interested to help </GRIN>
Relevant is that we do not have to invent something new; it has been part and parcel of things we have done before. The difference is that we gained in experience and, technology has evolved as well.
Thanks,
GerardM
One of the arguments why the WMF could enter the fray is that it has something to add. It does have monetary reserves but more importantly it has several resources that may make a difference. The biggest two are Wikipedia itself and the other are its awesome communities.
When translating a Wikipedia article, the concepts that are specific to a subject are likely to be found in that article. Similarly when such concepts have their own article, they will contain a similar set of concepts. Combine this with a multi-lingual dictionary build with Wikidata technology along OmegaWiki lines and it will be relatively easy to find the corresponding expressions in articles in different languages on the same subject.
The point here is that the meanings of words do not exist in a vacuum.
When such concepts have been identified and linked to Wikipedia articles and dictionary meanings it becomes possible to help people understand a text in a different language by providing native language support.
<GRIN> I know Erik Moeller has a lot of experience in this field and I know mutual friends are quite interested to help </GRIN>
Relevant is that we do not have to invent something new; it has been part and parcel of things we have done before. The difference is that we gained in experience and, technology has evolved as well.
Thanks,
GerardM
Sunday, April 14, 2013
#Wikivoyage #statistics revisited
I am happy to report that many of the issues with several statistics have been resolved. The most visible improvement is that the page views for Wikivoyage are now available and updated on a daily basis. When you check out these statistics you notice that Wikivoyage got the most attention when it was started. Now in the fourth month we can notice some stabilisation.
The latest Wikivoyage projects in Hebrew and Ukrainian are now included as well and it will be interesting to follow how they will do in the future.
I am really happy that many issues have been resolved. If anything, statistics are trusted because of the consistency and quality of the presentation. When you follow developments regularly you get a feeling for the underlying data. Waiting for the resolution of what seems like cosmetic issues destroys that feeling.
Thanks,
GerardM
Wednesday, April 10, 2013
Sign languages are important everywhere
When in 2005 the Austrian Sign language was constitutionally acknowledged, there was a curious second sentence added: "The Austrian Sign language is acknowledged. All details are determined by law". This sentence was a puzzle from the begin, because either it was trivial (then now one would add it because it should be found after every single point of the constitution) or there was some hidden intent behind it.
Now there is proof for the hidden intent by letters coming from "horrible jurists" of two ministries: They tell us that since there is no respective law, Austrian Sign Language cannot be established as a mother tongue in schools for deaf pupils. The jurists use the tardiness of the education ministry (this would have been obliged to develop realization laws for deaf people) as an argument that the Austrian government now dismisses the language rights of deaf people in the education process.
I read this news and, I am sure that these jurists have no clue why it is so important for children to learn to read and write in their mother tongue.. It is beneficial for all of their academic career. This is known to be true in the USA, Tunisia and Saudi Arabia ... it is also true for Austrians.
Thanks,
Gerard
Now there is proof for the hidden intent by letters coming from "horrible jurists" of two ministries: They tell us that since there is no respective law, Austrian Sign Language cannot be established as a mother tongue in schools for deaf pupils. The jurists use the tardiness of the education ministry (this would have been obliged to develop realization laws for deaf people) as an argument that the Austrian government now dismisses the language rights of deaf people in the education process.
I read this news and, I am sure that these jurists have no clue why it is so important for children to learn to read and write in their mother tongue.. It is beneficial for all of their academic career. This is known to be true in the USA, Tunisia and Saudi Arabia ... it is also true for Austrians.
Thanks,
Gerard
Thursday, March 28, 2013
I want #Wikimedia #statistics I can rely on
Erik Moeller asked the question; "what statistics do you like best, do you think most relevant". My answer is: statistics I can rely on.
There are several developers working on statistics. Many more than several years ago. I am sure that there is a need for data driven development and I am sure that the underlying numbers for many projects require time and effort. It does not mean that the statistics that are updated on a daily basis can be neglected.
Today I learned that two new Wikivoyage projects were created; one in Hebrew and one in Ukrainian. And after more than a month I checked the statistics for pageviews for Wikivoyage. They are still very much broken. There are other bugs that I reported as well. I cannot be bothered to check their continued existence.
Erik really, having statistics is wonderful. Having many statistics is evn better. It does not matter at all if you cannot rely on them. That way they become the infamous mantra of "Lies, damned lies and statistics".
Hmmm, I am complaining here. Check out my blog; I use statistics frequently to report on things Wiki.
Thanks,
GerardM
#ASL; the most challenging language at #Translatewiki II
An effort is underway to localise American Sign Language at translatewiki.net. It is a challenge and at this stage, it works by copy and pasting translations from Signpuddle. The result at twn looks really weird; it is a string of numbers.
To learn if these numbers actually work, I copied the localisation for Wednesday to my userpage on the ase.testproject. It did not work. The copied content did not create something in SignWriting. What I got were some numbers and to make it work I needed something else..
Not only knowing that something is in SignWriting but also what sign language it is will be really powerful.
Thanks,
GerardM
To learn if these numbers actually work, I copied the localisation for Wednesday to my userpage on the ase.testproject. It did not work. The copied content did not create something in SignWriting. What I got were some numbers and to make it work I needed something else..
- M512x531S2e508489x504S18600492x470
- <signtext clear=0>M512x531S2e508489x504S18600492x470</singtext>
- <lang=ase-Sgnw>M512x531S2e508489x504S18600492x470</lang>
Not only knowing that something is in SignWriting but also what sign language it is will be really powerful.
Thanks,
GerardM
Saturday, March 23, 2013
#ASL; the most challenging language at #Translatewiki
A #Wikipedia in "our" language is what people are working towards in the incubator. There are many challenges that need to be taken before this dream is fulfilled. Messages need to be localised, articles need to be written and finally the text has to be proven to be in "my" language. Several challenges that take time and effort, all for the big moment when one more Wikipedia is created.
They are challenges but they are dwarfed by the challenges facing the people working towards a Wikipedia in American Sign Language. First of all, their effort cannot be part of the incubator. Their incubator project is in a Wikimedia Labs environment. An environment with experimental software that allows them to write their own language.
The SignWriting script is written from top to bottom as you can see in the screenshot. This is not supported by MediaWiki. The SignWriting script is not yet part of Unicode. MediaWiki only supports scripts that are encoded in Unicode.
Consider what it does to localising the software at translatewiki.net. Below you find what Wednesday looks like for Adam, who is working on the localisation of the most used messages. It must be copying data from one environment to the next, not even knowing what the effect will be when it finally shows in the labs environment.
If anything I know how much hard work goes into new projects. The effort for the Wikipedia in American Sign Language is probably the most complicated of them all.
Thanks,
GerardM
They are challenges but they are dwarfed by the challenges facing the people working towards a Wikipedia in American Sign Language. First of all, their effort cannot be part of the incubator. Their incubator project is in a Wikimedia Labs environment. An environment with experimental software that allows them to write their own language.
The SignWriting script is written from top to bottom as you can see in the screenshot. This is not supported by MediaWiki. The SignWriting script is not yet part of Unicode. MediaWiki only supports scripts that are encoded in Unicode.
Consider what it does to localising the software at translatewiki.net. Below you find what Wednesday looks like for Adam, who is working on the localisation of the most used messages. It must be copying data from one environment to the next, not even knowing what the effect will be when it finally shows in the labs environment.
If anything I know how much hard work goes into new projects. The effort for the Wikipedia in American Sign Language is probably the most complicated of them all.
Thanks,
GerardM
Friday, March 22, 2013
#FUEL makes for standards in localisations
#RedHat and #Wikimedia Foundation engineers have been collaborating on providing support for the languages of India for some time now. However, both Red Hat and the Wikimedia Foundation support people from all over the world. Both organisations know the perils of internationalisation intimately well.
As this cooperation is progressing nicely, one of the early results can be found at translatewiki.net. This is where MediaWiki is localised and this is where software is localised in more languages than anywhere else. What you will find is that the Fuelproject can now be localised in other languages than the languages from India.
This project "aims at solving the Problem of Inconsistency and Lack of standardization in Software Translation across the platform". For this to work optimally, such an approach should not be restricted to India but it should be aimed to any and all languages.
How the terminology defined in FUEL will be used in translatewiki.net is not yet clear. What is obvious is the intention to standardise terminology as much as possible. This will make using software more predictable and that is very much to the benefit of everyone.
Thanks,
GerardM
As this cooperation is progressing nicely, one of the early results can be found at translatewiki.net. This is where MediaWiki is localised and this is where software is localised in more languages than anywhere else. What you will find is that the Fuelproject can now be localised in other languages than the languages from India.
This project "aims at solving the Problem of Inconsistency and Lack of standardization in Software Translation across the platform". For this to work optimally, such an approach should not be restricted to India but it should be aimed to any and all languages.
How the terminology defined in FUEL will be used in translatewiki.net is not yet clear. What is obvious is the intention to standardise terminology as much as possible. This will make using software more predictable and that is very much to the benefit of everyone.
Thanks,
GerardM
#MediaWiki powers #jQuery for language support
#Wikipedia is powered by MediaWiki. Wikipedia has a version in over 280 languages and, more languages are waiting in the wings. All these languages need support. This support is needed in all the computer languages used for Wikipedia; in PHP, Javascript even Lua.
With so many languages to support, you really need a standardised way to provide the support. Support for localisation, for input methods, for fonts.
One of the really brilliant software projects provides language support in jQuery and consequently in Javascript. It is under active development and consequently more and more languages are supported in this way. Currently there are over 155 input methods for over 75 languages - it is already the largest repository of input methods on the Web and, it is open source ...
This development has not gone unnoticed. People who support languages and scripts not supported by the Wikimedia Foundation have a hard time finding support for their languages, for their fonts and input methods. I have seen an implementation for the Thuɔŋjäŋ languages developed by Andrew Cunningham.
Even better, Andrew was happy enough to talk to Martin and this may result in even more collaboration on languages that deserve the same support just like any other language.
Do you want to experience the full power of jQuery.ime like me? We just have to wait for the Wikimedia Foundation to roll it out to its own websites. It is great dogfood, they just have to eat it.
Thanks,
GerardM
With so many languages to support, you really need a standardised way to provide the support. Support for localisation, for input methods, for fonts.
One of the really brilliant software projects provides language support in jQuery and consequently in Javascript. It is under active development and consequently more and more languages are supported in this way. Currently there are over 155 input methods for over 75 languages - it is already the largest repository of input methods on the Web and, it is open source ...
This development has not gone unnoticed. People who support languages and scripts not supported by the Wikimedia Foundation have a hard time finding support for their languages, for their fonts and input methods. I have seen an implementation for the Thuɔŋjäŋ languages developed by Andrew Cunningham.
Even better, Andrew was happy enough to talk to Martin and this may result in even more collaboration on languages that deserve the same support just like any other language.
Do you want to experience the full power of jQuery.ime like me? We just have to wait for the Wikimedia Foundation to roll it out to its own websites. It is great dogfood, they just have to eat it.
Thanks,
GerardM
Monday, March 18, 2013
Endowment and #Wikimedia
Every so often, there is talk about an endowment fund for the Wikimedia Foundation. This means that a huge pile of money is kept is reserve for a rainy day.
There are a few problems as far as I am concerned. It makes sense when there is a reasonable fear that we will not be able to fund the projects of the WMF in the future. It assumes all the things the WMF could fund are being funded and are competently managed. The return on investment of putting money in an investment fund .. eh .. endowment fund are better than the return on investment of putting this money to work. People who administer investment funds are bankers.
Given the success of the fundraisers of the WMF, the question if the WMF cannot raise enough funds for its current activities is a joke.
What the WMF currently does and what it could do are two different things. Answering the second can only be answered by looking at what the WMF is there for. I refer to the mission statement on Meta.
When I look at this text, the last two words can be seen a reason for an endowment.
However, I am certain that we can do more to "empower and engage people around the world". Just consider how much we do in the United States and compare it to Africa, Asia and South America combined. The WMF works in collaboration with a network of chapters.. Most countries do not have a chapter or another organisation .. yet.
Given that realistically the WMF is only investing in Wikipedia, it can not be said that we are doing everything possible to realise the mission statement. It can be argued that we do everything we can manage at this time.
There is enough room for growth and much of it does not need to cost us anything but time and effort. What is needed is the coordination, the planning and the will to go where Wikimedians have not gone before.
Thanks,
GerardM
PS for an endowment to work well you have to trust and pay a banker. Personally I have more trust in us spending money wisely.
There are a few problems as far as I am concerned. It makes sense when there is a reasonable fear that we will not be able to fund the projects of the WMF in the future. It assumes all the things the WMF could fund are being funded and are competently managed. The return on investment of putting money in an investment fund .. eh .. endowment fund are better than the return on investment of putting this money to work. People who administer investment funds are bankers.
Given the success of the fundraisers of the WMF, the question if the WMF cannot raise enough funds for its current activities is a joke.
What the WMF currently does and what it could do are two different things. Answering the second can only be answered by looking at what the WMF is there for. I refer to the mission statement on Meta.
The mission of the Wikimedia Foundation is to empower and engage
people around the world to collect and develop educational content under
a free license or in the public domain, and to disseminate it effectively and globally.
In collaboration with a network of chapters, the Foundation provides the essential infrastructure and an organizational framework for the support and development of multilingual wiki projects and other endeavors which serve this mission. The Foundation will make and keep useful information from its projects available on the Internet free of charge, in perpetuity.
In collaboration with a network of chapters, the Foundation provides the essential infrastructure and an organizational framework for the support and development of multilingual wiki projects and other endeavors which serve this mission. The Foundation will make and keep useful information from its projects available on the Internet free of charge, in perpetuity.
When I look at this text, the last two words can be seen a reason for an endowment.
However, I am certain that we can do more to "empower and engage people around the world". Just consider how much we do in the United States and compare it to Africa, Asia and South America combined. The WMF works in collaboration with a network of chapters.. Most countries do not have a chapter or another organisation .. yet.
Given that realistically the WMF is only investing in Wikipedia, it can not be said that we are doing everything possible to realise the mission statement. It can be argued that we do everything we can manage at this time.
There is enough room for growth and much of it does not need to cost us anything but time and effort. What is needed is the coordination, the planning and the will to go where Wikimedians have not gone before.
Thanks,
GerardM
PS for an endowment to work well you have to trust and pay a banker. Personally I have more trust in us spending money wisely.
Help #Wikipedia Zero and localise the #mobile software
Learning about the current state of Wikipedia Zero can be done through this presentation. It is well worth it. The things that I found most interesting are:
- The use of mobile phones is different from what was expected
- The Wikipedia Zero project has a measurable and positive impact
- There are things that can be improved upon, things like localisation
What many people do not realise is that the localisation of the mobile software is not part of the MediaWiki software. Traffic from mobile devices is what grows traffic for Wikipedia a lot. The experience is that when the software has been properly localised, it has a big impact.
In India we have had multiple localisation drives. Every time we ask the same things;
- please do the most used messages first, they are what people see the most
- then do the rest of the MediaWiki messages
- The extensions used by Wikipedia are the next lot that need doing
- Yes, there are all these other MediaWiki messages as well
Localisation has a clear impact on the number of readers and that is what ultimately grows the community.
So what we really, really need are for the mobile messages to be localised as well because this is where the new readers for our projects can be found.
Thanks,
GerardM
Friday, March 15, 2013
#Pope Francis on #Wikidata
The good news of Wikidata is that it may become the repository of data on many subjects. The bad news; it can get it wrong.
Pope Francis is the new pope of the Roman Catholic church. He is not the pope of Catholicism. This is rather basic.
There are all kinds of identifiers associated. Ever heard of a "Viaf identifier", a "GND identifier", "SUDOC" or a "GND identity type" and really should they be so prominently displayed?
The picture is not of the pope, it is of the former cardinal. The coat of arms is the coat of arms of the former cardinal..
The picture in my blog is of pope Francis; he is smiling.. And yes, I can edit Wikidata.
Thanks,
GerardM
Pope Francis is the new pope of the Roman Catholic church. He is not the pope of Catholicism. This is rather basic.
There are all kinds of identifiers associated. Ever heard of a "Viaf identifier", a "GND identifier", "SUDOC" or a "GND identity type" and really should they be so prominently displayed?
The picture is not of the pope, it is of the former cardinal. The coat of arms is the coat of arms of the former cardinal..
The picture in my blog is of pope Francis; he is smiling.. And yes, I can edit Wikidata.
Thanks,
GerardM
Saturday, March 02, 2013
Using #Wikidata in #OmegaWiki
Wikidata knows about the existence of #Wikipedia articles. One really nice side effect is that OmegaWiki will point you to the article in your language, Arabic in the example, even when OmegaWiki does not have a translation in your language.
Thanks,
GerardM
Thursday, February 28, 2013
A challenge for #Wikidata
Not only #Wikipedia but also #Wikisource and #Wikiquote are in need for the #Wikidata treatment. OmegaWiki can demonstrate why. Julius Caesar has an article in all the languages with a translation. All that is needed is a link to Wikidata where Julius is known as "Q1048".
Linking to the quotes of Caesar on Wikiquote is not so easy; it has to be done for each language to the Wikiquote where there are quotes by Caesar. This is also needed for Wikisource for books or other publications. You may notice that Julius Caesar is a writer and a person. A writer publishes and any person may produce quotable quotes.
The challenge for Wikidata is to go the extra mile and rid us from those pesky interwiki links... on all the Wikimedia projects. These links can in return be used on all the projects. It also makes searching more interesting... Julius Caesar; what do you want? An article about him, his sources, his quotes..
What we at OmegaWiki would like is for Wikidata to go even further and incorporate our data. This will be a big benefit because it will allow people to search in Nepali for जुलियस सिजर and have a similar result at no extra cost as in English.
Thanks,
GerardM
Denny, I do not agree
#Wikidata is a wiki and consequently Caesar can have a capitol according to Denny's blogpost. While I applaud the sentiment, it is not really practical.
Denny is the big man for Wikidata and he is a human and, he can be both right and wrong. So let me suggest why I do not support him in this and, let me suggest a compromise.
The one thing that will help is when there are classes and when those classes have attributes. For instance; a country has a national anthem, a capitol, a currency, a head of state etcetera. When you state that Caesar is a country, it then follows that he has a capitol, a currency, a head of state.. For Wikipedia this is really powerful. When all the countries have been labelled as such, it is easy and obvious to fill in the missing values for use in an info-box. The most valuable part of it is, that these values can be translated for use in info-boxes in other languages. Yes, the values can have their own Wikipedia articles as well as a label to use in an info-box.
When a label is used in an info-box, in any language, these labels are obviously of higher value than the labels that are not used. So Denny can have his way and as long as labels are values when they are used in a Wikipedia all the extra labels will not be very much in the way. Hard-drives are cheap. It is possible to have classes with associated labels. These classes can be a associated with a particular info-box.
This is what Julius Caesar looks like at OmegaWiki. As you can see it is linked to Wikidata, it is linked to Wikipedia and, it is linked to Commons. It would be so cool when we have the best of both worlds in a joined project.
Please Denny, lets cross the Rubicon.
Thanks,
GerardM
Denny is the big man for Wikidata and he is a human and, he can be both right and wrong. So let me suggest why I do not support him in this and, let me suggest a compromise.
The one thing that will help is when there are classes and when those classes have attributes. For instance; a country has a national anthem, a capitol, a currency, a head of state etcetera. When you state that Caesar is a country, it then follows that he has a capitol, a currency, a head of state.. For Wikipedia this is really powerful. When all the countries have been labelled as such, it is easy and obvious to fill in the missing values for use in an info-box. The most valuable part of it is, that these values can be translated for use in info-boxes in other languages. Yes, the values can have their own Wikipedia articles as well as a label to use in an info-box.
When a label is used in an info-box, in any language, these labels are obviously of higher value than the labels that are not used. So Denny can have his way and as long as labels are values when they are used in a Wikipedia all the extra labels will not be very much in the way. Hard-drives are cheap. It is possible to have classes with associated labels. These classes can be a associated with a particular info-box.
This is what Julius Caesar looks like at OmegaWiki. As you can see it is linked to Wikidata, it is linked to Wikipedia and, it is linked to Commons. It would be so cool when we have the best of both worlds in a joined project.
Please Denny, lets cross the Rubicon.
Thanks,
GerardM
Wednesday, February 27, 2013
What statistics for #Wikipedia
The question was: "What statistic inspires you most". My answer; it depends what hat I am wearing.
The statistic that means a lot to me are the page views. However, they do not truly show how many PEOPLE view the pages. There are the bots that spoil the view. But there is so much history there.. Even with the bots you get a picture of growth.
However, wearing another hat, I want to see an aggregation of views of GLAM objects for the GLAM's we cooperate with. This is so vital for making the point that Wikipedia is making cultural heritage visible. It is the one argument everyone "understands".
Yes, there are many languages but for this I want to know how well does MediaWiki work for a language and this can be found best in the stats at translatewiki.net.
Really Erik, there is no one statistic that is best. There are horses for courses. What is vital that the statistics can be trusted. If anything, improved reliability of the data is what would help us most.
Thanks,
GerardM
The statistic that means a lot to me are the page views. However, they do not truly show how many PEOPLE view the pages. There are the bots that spoil the view. But there is so much history there.. Even with the bots you get a picture of growth.
However, wearing another hat, I want to see an aggregation of views of GLAM objects for the GLAM's we cooperate with. This is so vital for making the point that Wikipedia is making cultural heritage visible. It is the one argument everyone "understands".
Yes, there are many languages but for this I want to know how well does MediaWiki work for a language and this can be found best in the stats at translatewiki.net.
Really Erik, there is no one statistic that is best. There are horses for courses. What is vital that the statistics can be trusted. If anything, improved reliability of the data is what would help us most.
Thanks,
GerardM
Wednesday, February 06, 2013
More traffic for the smaller #Wikipedia projects
The biggest Wikipedia in pageviews is the English language Wikipedia. Last month it generated 49.36% of all the traffic. This left 40.34% for the numbers 2 to nine and 10.3% for all the other Wikipedias.
Traffic is growing really well; 19% on a year to year basis for all the Wikipedias and 20% for the English Wikipedia. What the chart to the left shows is that slowly but surely the "other" languages are doing better than the top 10.
The current picture will change as it did in the past. Consider that the Dutch Wikipedia was bigger than the Chinese Wikipedia. The Dutch is growing at 16% while the Chinese is powering up the ladder with a healthy 46%.
There are many languages that have the potential to move on in the traffic rankings. This may be because the content in those languages improves or because the infrastructure in a country changes. I have reliable information that in India mobile traffic went from 55m to 85m in a matter of 6 months and this while it is too soon to attribute this to Wikipedia Zero. This is not obvious from the statistics published for India.
In a way I have been cheating; the numbers in the charts above exclude mobile traffic. This is because these numbers make it more obvious how well the "other" languages are doing. However, as you can see something similar is happening when mobile traffic is included.
With Wikipedia Zero growing in relevance, it seems obvious that content that is relevant to the people who use this service will grow in demand. As this is addressed in the languages people read, it will mean that the growth of popularity of Wikipedia articles will continue for some time. I also expect that the "other" languages will become more relevant and assertive.
Thanks,
GerardM
Traffic is growing really well; 19% on a year to year basis for all the Wikipedias and 20% for the English Wikipedia. What the chart to the left shows is that slowly but surely the "other" languages are doing better than the top 10.
The current picture will change as it did in the past. Consider that the Dutch Wikipedia was bigger than the Chinese Wikipedia. The Dutch is growing at 16% while the Chinese is powering up the ladder with a healthy 46%.
There are many languages that have the potential to move on in the traffic rankings. This may be because the content in those languages improves or because the infrastructure in a country changes. I have reliable information that in India mobile traffic went from 55m to 85m in a matter of 6 months and this while it is too soon to attribute this to Wikipedia Zero. This is not obvious from the statistics published for India.
In a way I have been cheating; the numbers in the charts above exclude mobile traffic. This is because these numbers make it more obvious how well the "other" languages are doing. However, as you can see something similar is happening when mobile traffic is included.
With Wikipedia Zero growing in relevance, it seems obvious that content that is relevant to the people who use this service will grow in demand. As this is addressed in the languages people read, it will mean that the growth of popularity of Wikipedia articles will continue for some time. I also expect that the "other" languages will become more relevant and assertive.
Thanks,
GerardM
Sunday, February 03, 2013
#Wikivoyage #statistics II
The first month of Wikivoyage statistics is in. The page views statistics are now regularly updated. There is now a baseline to compare future months with. Last week I blogged about Wikivoyage statistics and at that time traffic was expected to reach 12.8 M. As you can see in the screen dump, it ended up at 17.3 M.
Over time Wikivoyage will become increasingly Wikivoyage. It will slowly but surely morph into something that can be distinguished from Wikitravel. Once that process is well under way, I am sure that there will be a growing public for this Wikimedia project.
Thanks,
GerardM
Subscribe to:
Posts (Atom)




















