Dear All,
my name is Stefan Jensen, I work for the European Environment Agency in Copenhagen DK, responsible among other things for the GEneral Multilingual Environmental Thesaurus. More on GEMET from http://eionet.eu.int/GEMET .
I came across Wiki type approaches recently and I am getting exited about the "open content" possibility this offers to maintain and share environmental terminologies.
Just now I am sitting in a meeting where many providers of environmental terminologies as well as technical solutions providers gather under a UNEP umbrella. (see also the thesaurus workshop under http://ecoinfo.eionet.eu.int ). I presented the Wiki-way to the group and there was interest and criticism alike.
I promised to explore the feasibility of such a thing...
Rough scetch of a process to pilot this would be:
- use Wiki open source software - preferable ZOPE based - to "publish" our material (5200 terms in 22 languages with 5 languages carrying alsodefinitions for the terms)
> How easy is it to get such stuff (available in XML/RDF) into it?
- after establishing this core, let people contribute terms, languages, definitions, concepts ...
> While we could test this, we would probably introduce some moderation to avoid chaos (but hopefully this is not even necessary). Any ideas on that one?
Well, this is a bit of the story for a start - Anybody out there with some ideas / suggestions e.g.
grateful
stefan
Dear Admins
I have had many problems with users from Portugal in pt.wikipedia.com about the differences of portuguese at Brazil and Portugal.
My suggestion was create the Wikitionary entries that community accepted.
We could setup de Wikitionary in portuguese language?
Tnks
Paulo Colacino
The Text Encoding Initiative Consortium has a very well developed XML DTD and
Schema for dictionaries, words, definitions, etc. I know one of the ideas for
the wiktionary redesign was simplicity, but this could be a good building block
for some of the back-end stuff, or even exporting some of the information out
to users.
[1] - http://www.tei-c.org/
--
brian suda
http://suda.co.uk
On 18 Mar 2004 at 14:25, Ray Saintonge wrote:
> Nicolas Weeger wrote:
(...)
> > Also, when will the 'real' fr.wiktionary (or other languages :)) be
> > available?
>
> I know that I've heard this several times since Wiktionary was started.
> The only thing that's needed is for someone who wants them to take the
> initiative and get working on them.
There are at least four persons who want to start Polish version of Wiktionary
see: http://pl.wikipedia.org/wiki/Wikipedia:Polska_wersja_s%C5%82ownika_Wiktiona…
So you see... there's much more than one person asking
for a new incarnation of Wikipedia.
We are looking forward to any new installations of Wikitionary
e.g. pl.wiktionary.org :)
Discussions about the interface/technology suitable to edit dictionaries
in a wiki way are very valuable and necessary
(as far as I know this is the main obstacale that hods back creation of new
dictionaries) but before new solution pops up our ethnusiasm might be lost.
Can anybody install a new DB for Polish Wiktionary, please?
We would be very grateful.
Integration of wiktionaries would be a far future.
We've got a lot of material in our minds
and we have no place where we can put it!
Regards
Youandme
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
When will a multilingual wiktionary be put in place?
This was already requested several times for German and French languages.
I think that the same set up than Wikipedia can be used, i.e.
http://de.wiktionary.org/, http://fr.wiktionary.org/...
Thanks,
Yann
- --
http://www.non-violence.org/ | Site collaboratif sur la non-violence
http://www.forget-me.net/ | Alternatives sur le Net
http://fr.wikipedia.org/ | Encyclopédie libre
http://www.forget-me.net/pro/ | Formations et services Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAM9ohm4KYjQo0y9oRAs7QAJ4oLAIJiwdAVOvy/jp5lT6J7KvwzACeKJvV
TSpk5F1HBn5NMYX8cQT+gOU=
=zgsY
-----END PGP SIGNATURE-----
Salve Wiktionary-people,
it`s great to have an own mailinglist. I what you to know that I like to join
and share some ideas for wikitionary soon. I came to wikipedia to find an
explaination for words that I haven`t found with ispell... more about this
visit (still only in German): http://de.wikipedia.org/wiki/
Benutzer:RobertMichel
At the moment I try to get a 25.000 word-list (catchwords) from a geology
bibliothek for a use with GNU-FDL. Beside of wikitonary, I have at he moment
a disput on the German Wikipedia Mailinglist - about a better reserch of
catchwords and an algorithmen how to give names to articels with less as
posible subjectivity. *g*
Because of making my mind about more systematic I tried to scan (manualy) all
wetterforcast region of an german wetterreport:
http://de.wikipedia.org/wiki/Wettervorhersage_(deutsche_Vorhersagegebiete)
Theses regions are not realy a good example for translations, but it should be
an example to scan the text of national radiostation for words of one field.
With such kontext is it more easy to translate and more usefull for learning
vocabulary. The sum of all fields could build the wiktionary, and one link of
rain could show a list of meterologic words (rain, snow, storm...)
I think the software should support the research of the words and the wictors
(viktors (what is the name for wikitonary people ?)) should work as
systematic as posible and build wordlists for seperate sujects bevore to link
them to another language. To build software for Wikitonary is definitive more
dificult than for the wikipedia, and beside of software-tools giving
software-skills to the wictors should have the same priority.
So with "quick and dirty" we won`t have succsess, and we should take time for
think about
- how to get lists of words (scaning ebooks,news, catchwords form bibliotheks)
- how to split these list in fields
- how to work with them
....
When we find all ways how to find words systematicaly, for every way we should
creat a dummy wordlist to know how to handel these.
Back to the 25.000, I want to add statisticaly informations to these words,
how many books, news, articals, dissertation, webpages, newsgroups-posting
this words are used.
Greetings from Aachen,
rob
PS: I study civil ingeneering ;)
This wiktionary mailing list was created to discuss some possible changes,
implementations, and improvements to the current Wiktionary. The idea is to
transform the current freeform wiki-dictionary into a more formal structured
format. That way things can be more easily searched, linked, and managed.
The debate is how simple or complex should the system be. If it is too complex
no one will add to it, if it is too simple, then the conversion from wiki-system
to the new format was in vain. We also don't want to reinvent the wheel, there
are several other dictionary format available. One for example is the DICT
protocol[1]. The Dictionary Server Protocol (DICT) is a TCP transaction based
query/response protocol that allows a client to access dictionary definitions
from a set of natural language dictionary databases. RFC 2229 has more
information.[2] This might be an intersting format to follow, or maybe not?
The system should be fairly simple and expanded later. The major points to be
broken down are: Words (terms, various prononciations, language), Definitions
(part of speach, definition, example), synonyms, antonyms, etymologies,
translations? Each would be it's own table keyed by the word. This is a very
simple system, and it is a good point to start a discussion.
The other table i would suggest is some sort of 'See Also'. This would be used
for things like mutiple spellings, or plurals. So if i enter 'colour' and color
is already in the dictionary, i can add a definition to 'colour' as "The british
spelling of color"... SEE ALSO: color. The same would work for plurals (goose,
geese). This doesn't force any weird root word constrains, and allows for some
miskates by people NOT check for alternate spellings first, but is easily
fixable with a 'see also' link.
that's my two cents, any suggestions?
-brian
[1] - http://www.dict.org/bin/Dict
[2] - http://www.dict.org/rfc2229.txt
--
brian suda
http://suda.co.uk