Kotava is a constructed language. There is yet not article in the English Wikipedia, there is an article in eight other language.. (myth busting; if it is not in the English Wikipedia, it is not in Wikipedia).
At this moment Kotava is not eligible for a Wikipedia, it will not be enabled for editing in OmegaWiki. It does not have an ISO-639-3 code yet. What is special is that there are clear indications that the process for a code is under way. The code is likely to be "avk".
At OmegaWiki there is a Kotava enthusiast who has started a lot of the preparations for another language. It will be given once the code is official. For a Wikipedia, they may ask for a Kotava Wikipedia. With the ISO process under way, the language committee does not have to do anything until the code is granted.
It is great that the language committee has reserved the right to do nothing..
Thanks,
GerardM
Tuesday, October 30, 2007
WCN, the network - an unsung hero
When you are at a conference and the networking just works, you will not hear anyone about it. At the Wikimedia Conferentie Nederland NOBODY mentioned the network; it was just there and it just did what it was supposed to do.
GREAT :)
Thanks,
GerardM
GREAT :)
Thanks,
GerardM
Sunday, October 28, 2007
Google docs - published presentation
Saturday, October 27, 2007
WCN
Today the Wikimedia Conferentie NL was held in Amsterdam. It was a great occasion. It was impossible to do justice to the program; they had three tracks and to chose one presentation over the other was an injustice to what was missed.
I had the privilege to give a presentation, and as I had to do some serious travelling to be there, I considered to what extend I could reduce what I took with me. I decided that with the latest Google application I did not need to bring anything. I could rely on there being a network, Kim brought his Merakis who are still on the old functional software and assuming one functional lap top should not be a problem either.
To prove that it was indeed the Google presentation tool. I selected one of the available backgrounds. It is different. What I need in a presentation is basic. I need to show some texts and some screen dumps. I think there is some need to polish the handling of the screen dumps.
One of the nice things is that the presentation can be made available. So have a look and let me know what you think.
Thanks,
GerardM
I had the privilege to give a presentation, and as I had to do some serious travelling to be there, I considered to what extend I could reduce what I took with me. I decided that with the latest Google application I did not need to bring anything. I could rely on there being a network, Kim brought his Merakis who are still on the old functional software and assuming one functional lap top should not be a problem either.
To prove that it was indeed the Google presentation tool. I selected one of the available backgrounds. It is different. What I need in a presentation is basic. I need to show some texts and some screen dumps. I think there is some need to polish the handling of the screen dumps.
One of the nice things is that the presentation can be made available. So have a look and let me know what you think.
Thanks,
GerardM
Monday, October 22, 2007
Breton
Breton is is a Celtic language spoken by some of the inhabitants of Brittany (Breizh) in France. According to Ethnologue over half a million people speak the language.
There is an organisation that is actively promoting the Breton language. I am really happy to inform you that they have taken the trouble to localise the system messages of OmegaWiki and have started to add translations in Breton. I have send a file with many of the languages that are in the ISO 639-1. This combination will localise most of OmegaWiki in Breton.
The argument that proved convincing is that you get all the information we have. By steadily increasing the translations available in Breton, the experience will improve.
Thanks,
GerardM
There is an organisation that is actively promoting the Breton language. I am really happy to inform you that they have taken the trouble to localise the system messages of OmegaWiki and have started to add translations in Breton. I have send a file with many of the languages that are in the ISO 639-1. This combination will localise most of OmegaWiki in Breton.
The argument that proved convincing is that you get all the information we have. By steadily increasing the translations available in Breton, the experience will improve.
Thanks,
GerardM
Saturday, October 20, 2007
Import, export
In OmegaWiki we provide some statistics. One of them is a breakdown of the Expressions per language. It is interesting because it shows what people are working on. It is a good indicator because after the initial import from GEMET, all the new work was done by hand. We are now experimenting with the import and export of data that are in collections and this will change things quite a bit.
The export creates a txt file with the columns separated by tabs. The columns are the number identifying the DefinedMeaning, and combinations of the Expressions and Definitions. The reason why we start with this export is because it is still much quicker to translate in a spreadsheet then it is to translate on the web. These experiments are done in a test environment and, we hope to bring it life soon. I can already send you a file when you are interested :)
When we start to import, it is likely that languages can make quite a jump in the statistics. I hope it will encourage people to help us by providing translations particularly for the less resourced languages.
Thanks,
GerardM
The export creates a txt file with the columns separated by tabs. The columns are the number identifying the DefinedMeaning, and combinations of the Expressions and Definitions. The reason why we start with this export is because it is still much quicker to translate in a spreadsheet then it is to translate on the web. These experiments are done in a test environment and, we hope to bring it life soon. I can already send you a file when you are interested :)
When we start to import, it is likely that languages can make quite a jump in the statistics. I hope it will encourage people to help us by providing translations particularly for the less resourced languages.
Thanks,
GerardM
Friday, October 19, 2007
Dbpedia
I chatted with Duesentrieb the other day. He mentioned dbpedia. I had another look and it is really a great resource. For those that do not know, dbpedia is a community effort to extract structured information from Wikipedia and to make this information available on the Web.
It does a great job and it is different from that other project that deals with structured information, Semantic MediaWiki, in that it does operate by data mining information from Wikipedia while Semantic MediaWiki is an integral part of a MediaWiki project.
The great thing of dbpedia is that it explicitly encourages interlinking. With interlinking data, data that can be found in another resource, becomes available limited by the quality of the interface.
You might ask how OmegaWiki fits into all this. Dbpedia's information is in English while OmegaWiki allows for the representation of information in any language . Both OmegaWiki and dbpedia link to Wikipedia articles and consequently where the two share a link, the information can be mashed together.
In Wikiprotein there is a large amount of medical information available. This information does link to external databases. Given that the medical articles relate to external databases, there is an opportunity to link the data to Wikipedia articles. With Wikipedia articles linked in this way, more specialists will find their way to the Wikipedia medical articles and this in turn will make more enriched information available.
The thing to consider now is how OmegaWiki can benefit from dbpedia.. one of the issues is the difference in license. Then again, dbpedia provides its algorithms and consequently the result is not necessarily the license that dbpedia posts.
Thanks,
GerardM
It does a great job and it is different from that other project that deals with structured information, Semantic MediaWiki, in that it does operate by data mining information from Wikipedia while Semantic MediaWiki is an integral part of a MediaWiki project.
The great thing of dbpedia is that it explicitly encourages interlinking. With interlinking data, data that can be found in another resource, becomes available limited by the quality of the interface.
You might ask how OmegaWiki fits into all this. Dbpedia's information is in English while OmegaWiki allows for the representation of information in any language . Both OmegaWiki and dbpedia link to Wikipedia articles and consequently where the two share a link, the information can be mashed together.
In Wikiprotein there is a large amount of medical information available. This information does link to external databases. Given that the medical articles relate to external databases, there is an opportunity to link the data to Wikipedia articles. With Wikipedia articles linked in this way, more specialists will find their way to the Wikipedia medical articles and this in turn will make more enriched information available.
The thing to consider now is how OmegaWiki can benefit from dbpedia.. one of the issues is the difference in license. Then again, dbpedia provides its algorithms and consequently the result is not necessarily the license that dbpedia posts.
Thanks,
GerardM
Friday, October 12, 2007
Domain names in other scripts
The Washington Post is reporting that ICANN is experimenting with URLs in other scripts. This is good news. For people that do not read or write in a language that uses the Latin script, it is a big handicap to have to type for instance http://ar.wikipedia.org also http://ar.ويكيبيديا.org is problematic. In order to enable people, you have to have the whole string in the appropriate script.
From a localisation point of view, this is one of the ultimate challenges. Consider; the .org has two components, the dot (.) and the org. The org needs an equivalent in all scripts. This top level domain or TLD is just one of many. The ISO 15924 defines many scripts and, a particular combination that is auspicious in one language can be the equivalent of wtf in another. Choosing these codes is not trivial. There are not only TLDs but also ccTLDs or country code top level domains.
We have agreed that ويكيبيدي is Arabic for Wikipedia .. Wikipedia is very much an international movement. We have agreed that Wikipedia is to be used for the Latin script in our domain name. The question is, if ويكيبيدي will be accepted to represent Wikipedia in the Arab script and, when there are multiple ways of writing Wikipedia, do we need to register for all these domains?
To make it even more confusing, what will the rules be when it comes to domain squatting. I can imagine that a brand is only registered for one script and not necessarily for another. I wonder what the position of the WMF will be; I am sure that it has not been considered yet.
ICANN is courageous, they are now experimenting with the technical issues and this will show that it can be done. I expect that the next part will be a proposal on how all the top level domain names are to be "transscripted". Then, it will become interesting because from that moment onwards the Internet will be truly global in its reach and no longer centered on one language or script.
Thanks,
GerardM
From a localisation point of view, this is one of the ultimate challenges. Consider; the .org has two components, the dot (.) and the org. The org needs an equivalent in all scripts. This top level domain or TLD is just one of many. The ISO 15924 defines many scripts and, a particular combination that is auspicious in one language can be the equivalent of wtf in another. Choosing these codes is not trivial. There are not only TLDs but also ccTLDs or country code top level domains.
We have agreed that ويكيبيدي is Arabic for Wikipedia .. Wikipedia is very much an international movement. We have agreed that Wikipedia is to be used for the Latin script in our domain name. The question is, if ويكيبيدي will be accepted to represent Wikipedia in the Arab script and, when there are multiple ways of writing Wikipedia, do we need to register for all these domains?
To make it even more confusing, what will the rules be when it comes to domain squatting. I can imagine that a brand is only registered for one script and not necessarily for another. I wonder what the position of the WMF will be; I am sure that it has not been considered yet.
ICANN is courageous, they are now experimenting with the technical issues and this will show that it can be done. I expect that the next part will be a proposal on how all the top level domain names are to be "transscripted". Then, it will become interesting because from that moment onwards the Internet will be truly global in its reach and no longer centered on one language or script.
Thanks,
GerardM
Saturday, October 06, 2007
A picture paints a thousand words
I think the Georgian script is pretty :)
Thanks,
GerardM
Now with grammatical gender
In Omegawiki we now have support for grammatical gender. When we now how to say it in "your" language, we can show it. :)
Thanks,
GerardM

Thanks,
GerardM
OmegaWiki vs Semantic MediaWiki
Both OmegaWiki and Semantic MediaWiki are providing semantic support. There are people that have expressed that OmegaWiki should not include particular types of data because Semantic MediaWiki does a better job.
Both OW and SMW are extensions to MediaWiki, so at first face it seems like a reasonable suggestion. The two extensions however do completely different things.
Semantic MediaWiki will shine when it becomes part of a project like the English Wikipedia; when key data that is in the article is marked, it will provide a great improvement in making these facts available. SMW even provides a really rich environment to query the information. It is absolutely great and it is absolutely mono-lingual.
OmegaWiki is at this moment very much a stand alone application. It does not derive data from anything, it is great at presenting the same data in many languages. This means that when we know that the information exists, we will show it in "your" language.
SMW can export and when OW can import, we have the best of both worlds; that is to say we have the best of both worlds when we can link the resources to each other. As OmegaWiki is not encyclopaedic and does not want to be, it is our stated intention to link to Wikipedia articles. As the SMW is tightly linked to the Wikipedia articles, this may be just the trick.
The suggestion that OmegaWiki would only have the semantic information that is in Wikipedia is incorrect. In Wikiprotein we already have a real rich set of annotations of proteins. This is the kind of information that is not encyclopaedic. It enables scientists to maintain information on "their" proteins. The language of the science of proteins is English, however many are known in other languages. It is rich that all this can integrate as it brings diverse information together.
Both OmegaWiki and Semantic MediaWiki have their own, and different strengths. Within Open Progress we use Semantic MediaWiki for our internal wiki. It works absolutely fabulous. I love both MediaWiki extensions!
Thanks,
GerardM
Both OW and SMW are extensions to MediaWiki, so at first face it seems like a reasonable suggestion. The two extensions however do completely different things.
Semantic MediaWiki will shine when it becomes part of a project like the English Wikipedia; when key data that is in the article is marked, it will provide a great improvement in making these facts available. SMW even provides a really rich environment to query the information. It is absolutely great and it is absolutely mono-lingual.
OmegaWiki is at this moment very much a stand alone application. It does not derive data from anything, it is great at presenting the same data in many languages. This means that when we know that the information exists, we will show it in "your" language.
SMW can export and when OW can import, we have the best of both worlds; that is to say we have the best of both worlds when we can link the resources to each other. As OmegaWiki is not encyclopaedic and does not want to be, it is our stated intention to link to Wikipedia articles. As the SMW is tightly linked to the Wikipedia articles, this may be just the trick.
The suggestion that OmegaWiki would only have the semantic information that is in Wikipedia is incorrect. In Wikiprotein we already have a real rich set of annotations of proteins. This is the kind of information that is not encyclopaedic. It enables scientists to maintain information on "their" proteins. The language of the science of proteins is English, however many are known in other languages. It is rich that all this can integrate as it brings diverse information together.
Both OmegaWiki and Semantic MediaWiki have their own, and different strengths. Within Open Progress we use Semantic MediaWiki for our internal wiki. It works absolutely fabulous. I love both MediaWiki extensions!
Thanks,
GerardM
Thursday, October 04, 2007
Changes in the user interface
A DefinedMeaning in OmegaWiki can have a lot of data associated with it. China borders on so many countries and seas that it is just a bit much. So it makes sense to bundle certain types of information together and keep them separately. This has a profound impact on what the data looks like. So far I was happy when we had the data on the screen but now it becomes possible to think where does it makes sense to have the data. I asked Erik if the incoming messages could be at the bottom of the page..
Well some things seem like miracles and we can have them in five minutes.. The problem with the collations is that at this moment it has to be by hand. This makes that it does not scale. With the "borders on" example however, we have a great showcase WHY we need to be able to sort these texts and also why they should be Expressions in OmegaWiki like all the other information that we hold.
Really, I could not be more happy with the progress that started to happen.. :)
Thanks,
GerardM
Well some things seem like miracles and we can have them in five minutes.. The problem with the collations is that at this moment it has to be by hand. This makes that it does not scale. With the "borders on" example however, we have a great showcase WHY we need to be able to sort these texts and also why they should be Expressions in OmegaWiki like all the other information that we hold.
Really, I could not be more happy with the progress that started to happen.. :)
Thanks,
GerardM
Wednesday, October 03, 2007
Is it a Wiki ?
OmegaWiki is a wiki. Some people however disagree; they consider the fixed format conclusive evidence why it is not. As the software is maturing, this argument loses a lot of its lustre. Obviously we have been saying that these people are wrong all along :)
The best argument why OmegaWiki is a wiki is because people can add/ change little items one at a time, they are not compelled to do everything at one go. As this is acceptable, our data has to be correct but does not necessarily need to be complete.
With the new terminological support; we can now indicate that a language is a language, all kinds of additional information can be added once you have stated that it is a language. Have a look at French for instance, the "incoming relations" and the annotations provide a lot of information. As the moment of writing it is not yet clear that French is an official language of France for instance.
With the expansion of existing classes, with the expansion of the class attributes information will become more available and integrated. The best bit is that as the OmegaWiki specific user interface can be translated in many language people will be challenged to ensure that the right terminology is used in translation.
With the new functionality OmegaWiki became much more wiki. It is there for every one to see, and everyone is cordially invited to have a look, create a user, add some Babel templates and have a go at it.
Thanks,
Gerard
The best argument why OmegaWiki is a wiki is because people can add/ change little items one at a time, they are not compelled to do everything at one go. As this is acceptable, our data has to be correct but does not necessarily need to be complete.
With the new terminological support; we can now indicate that a language is a language, all kinds of additional information can be added once you have stated that it is a language. Have a look at French for instance, the "incoming relations" and the annotations provide a lot of information. As the moment of writing it is not yet clear that French is an official language of France for instance.
With the expansion of existing classes, with the expansion of the class attributes information will become more available and integrated. The best bit is that as the OmegaWiki specific user interface can be translated in many language people will be challenged to ensure that the right terminology is used in translation.
With the new functionality OmegaWiki became much more wiki. It is there for every one to see, and everyone is cordially invited to have a look, create a user, add some Babel templates and have a go at it.
Thanks,
Gerard
Monday, September 24, 2007
Self promotions on BBC-News
The BBC-news website is my primary website for news. It provides great information and I have read it for many years. As I am driving less nowadays, I do not listen as often as I used to to the BBC-Worldservice (648 AM).
Recently there has been an increase in the number of video fragments. At the same time I find that I am less likely to watch them. The reason; every fragments is now preceded with a promotion and it is annoying and distracting to the point where I do not bother any more.
Thanks,
GerardM
Recently there has been an increase in the number of video fragments. At the same time I find that I am less likely to watch them. The reason; every fragments is now preceded with a promotion and it is annoying and distracting to the point where I do not bother any more.
Thanks,
GerardM
Sunday, September 16, 2007
Zuckertüte
When kids go to school for the very first time in Germany, they get a " Zuckertüte". A Zuckertüte is a big carton cornet filled with sweets and little gifts.The word Zuckertüte is a good example of a word where I do not expect translations in any other language as it is a real German tradition. This does not mean that there cannot be translations of the definition.
I hope that the grandchildren of this little lady have a great day at school tomorrow :)
Thanks,
GerardM
Friday, September 14, 2007
Shtooka
When I started to record pronunciations for Wiktionary, I used Audacity. It is a great tool but hey when you are a serial recorder, you want to have a tool that assist and helps you to do it it efficiently. Shtooka is a great tool. I think I blogged it in the past.
Now they have surpassed themselves. There is now the Shtooka explorer. It allows you to listen to the many, many pronunciations in several languages they have recorded. It is an absolutely gorgeous application that really shows off an already great project :)
Thanks,
Gerard
Now they have surpassed themselves. There is now the Shtooka explorer. It allows you to listen to the many, many pronunciations in several languages they have recorded. It is an absolutely gorgeous application that really shows off an already great project :)
Thanks,
Gerard
Thursday, September 13, 2007
Social networks
I have been using social networks for some time now, LinkedIn, Plaxo, ecademy and facebook is where you can find me. As I have invested a considerable amount of time, it is relevant to consider if they are worth the time and effort.
LinkedIn, Plaxo and ecademy are at a considerable disadvantage because in order to get the full functionality, you have to spend money. It then becomes relevant to understand the potential benefits for these networks. All three provide basic functionality that is for free and as there is no real overlap yet, I maintain a presence there.
Facebook is what I have been looking at lately. What it has right is that it tries to connect people, the groups they belong to, the causes they champion and the organisations they are associated with. When you combine it with the potential to program extra functionality for facebook, you get a more compelling package then its competition.
It is however lacking in other ways. For one the way it has its security is minimal. I do not mind to tell the world that I am on facebook, but I prefer that only friends and friends of friends can see who my friends are. I would happily leave Plaxo behind when facebook had the same security for sharing personal and work information.
The one thing all the social networks have in common is that they are proprietary. To make their functionality useful to me, I have to trust it with my information. I do however not know if the implementation of their security can be trusted. Were they to use something like A-Select I would feel more comfortable because it would allow enough eye balls to vouch for the authentication process. Even though it would be a great step forward, it would be better if all the software were Open / Free software. Authentication is one aspect, the authorisation within the application itself can still make my data insecure.
Who to trust, why to trust ...
Thanks,
GerardM
LinkedIn, Plaxo and ecademy are at a considerable disadvantage because in order to get the full functionality, you have to spend money. It then becomes relevant to understand the potential benefits for these networks. All three provide basic functionality that is for free and as there is no real overlap yet, I maintain a presence there.
Facebook is what I have been looking at lately. What it has right is that it tries to connect people, the groups they belong to, the causes they champion and the organisations they are associated with. When you combine it with the potential to program extra functionality for facebook, you get a more compelling package then its competition.
It is however lacking in other ways. For one the way it has its security is minimal. I do not mind to tell the world that I am on facebook, but I prefer that only friends and friends of friends can see who my friends are. I would happily leave Plaxo behind when facebook had the same security for sharing personal and work information.
The one thing all the social networks have in common is that they are proprietary. To make their functionality useful to me, I have to trust it with my information. I do however not know if the implementation of their security can be trusted. Were they to use something like A-Select I would feel more comfortable because it would allow enough eye balls to vouch for the authentication process. Even though it would be a great step forward, it would be better if all the software were Open / Free software. Authentication is one aspect, the authorisation within the application itself can still make my data insecure.
Who to trust, why to trust ...
Thanks,
GerardM
Tuesday, September 11, 2007
Hehe
Hehe is a language spoken in the Iringa Region, south of Gogo in Tanzania by some 750.000 people. There is no article about this language on the English Wikipedia but there is an article on the people who speak this language; the Hehe.
Even though there are many references at the back of the article, it is marked as not citing references or sources. I do agree however that this article would benefit a lot from wikifying and the creation of supporting articles. It is a good example of the amount of work that needs doing to make the English Wikipedia relevant as a resource for Africa.
Thanks,
GerardM
Even though there are many references at the back of the article, it is marked as not citing references or sources. I do agree however that this article would benefit a lot from wikifying and the creation of supporting articles. It is a good example of the amount of work that needs doing to make the English Wikipedia relevant as a resource for Africa.
Thanks,
GerardM
Monday, September 10, 2007
Sassarese and Sardinian
There is a Wikipedia in the Sardinian language. It uses the sc ISO-639-1 code. What was known as Sardinian became srd in the ISO-639-2. In the ISO-639-3 it was recognised as a macrolanguage; practically what was called Sardinian was split into four languages.
The Italian government has officially recognised the Sardinian language or the "Limba Sarda Comune". This is in essence a constructed language as it tries to make one language out of the four "dialects". One of the effects has been that some people prevent others from writing in one of the four languages on the sc.wikpedia.
The language committee of the Wikimedia Foundation has a request to approve a new language; one of the Sardinian languages, Sassarese with ISO code sdc.
There are two problems to deal with:
Given that the language committee has as one of its rules that political arguments are not accepted, there are a few conclusions that we should make.
Thanks,
GerardM
The Italian government has officially recognised the Sardinian language or the "Limba Sarda Comune". This is in essence a constructed language as it tries to make one language out of the four "dialects". One of the effects has been that some people prevent others from writing in one of the four languages on the sc.wikpedia.
The language committee of the Wikimedia Foundation has a request to approve a new language; one of the Sardinian languages, Sassarese with ISO code sdc.
There are two problems to deal with:
- The "Limba Sarda Comune" is not recognised as a language
- The proponents of the "Limba Sarda Comune" reserve the sc.wikipedia for their language
Given that the language committee has as one of its rules that political arguments are not accepted, there are a few conclusions that we should make.
- Sassarese can have a conditional approval
- We urge the proponents of the Limba Sarda Comune to ask for the recognition of this newly constructed language from ISO.
Thanks,
GerardM
Saturday, September 08, 2007
Wikizine but more relevant WalterBE
Walter is a long-standing member of the Wikimedia Foundation. He is a steward, he is the editor-in-chief of Wikizine. He organised the first official meeting of people of the nl.wikipedia .. there were only two people and we had fun.
People who know Walter know him as a soft spoken can-do person. He has done much of the organisational work on the Dutch Wikipedia, organising elections, being involved in OTRS from the start. He is the press contact for Belgium ... As a steward he did much good, he is a member of the communication committee ...
Walter has indicated that he has grown away from the community and as such his motivation for Wikipedia and Wikimedia stuff has gone downhill. He does not feel that he can properly represent the WMF and the community, he is disappointed in the lack of cooperation around Wikizine ... What has prevented him so far to stop is his sense of responsibility to the Wikizine readers. Wikizine has been a labour of love for Walter, there has been little input from the community to inform Walter about the latest, no people except for proof readers who shared the burden of this well received periodical.
Well, I can only be sad that Walter finds his commitments a burden. I do hope that he will know and remember how much he is appreciated for the work that he does and has done. Really, to me Walter is one of the most important Wikimedians.
Thanks,
GerardM
People who know Walter know him as a soft spoken can-do person. He has done much of the organisational work on the Dutch Wikipedia, organising elections, being involved in OTRS from the start. He is the press contact for Belgium ... As a steward he did much good, he is a member of the communication committee ...
Walter has indicated that he has grown away from the community and as such his motivation for Wikipedia and Wikimedia stuff has gone downhill. He does not feel that he can properly represent the WMF and the community, he is disappointed in the lack of cooperation around Wikizine ... What has prevented him so far to stop is his sense of responsibility to the Wikizine readers. Wikizine has been a labour of love for Walter, there has been little input from the community to inform Walter about the latest, no people except for proof readers who shared the burden of this well received periodical.
Well, I can only be sad that Walter finds his commitments a burden. I do hope that he will know and remember how much he is appreciated for the work that he does and has done. Really, to me Walter is one of the most important Wikimedians.
Thanks,
GerardM
Subscribe to:
Posts (Atom)
