Graham Lauder napisał(a):
On Saturday 31 March 2007 22:17, Marcin Miłkowski wrote:
Hi Graham,
Warned? about what? If the Wordnet list is Opensource then what is the
issue?
I understood you want to start from _scratch_.
I never said that. In fact I said exactly the opposite. I'm not sure how you
could have drawn that inference, I apologise if I am not being clear enough.
Then it's really OK to proceed with your project. Sorry if I misunderstood.
Excuse me if I'm beginning to sound frustrated, as I already explained, we
have a team of people, paid people, that are willing to administer the setup.
They have project managers who will gather the linguists. What you are
talking about is frankly rather trivial in a corporate space. Assembling
project teams is a daily task in this environment You are seeing barriers
where there are none.
You're asking for advice so you're getting advice - I'm only saying that
gathering a skilled team is the most important issue here.
I understood that the company is only offering a technical environment,
and this technical environment is not really a bottleneck.
If therefore Openthesaurus is a bad option, the assumption I take from
what you are saying is; setting up a local Wordnet is the best
alternative.
It is not a bad option. I'm using OpenThesaurus myself. But if you want
to reuse Wordnet, you need to convert it into OpenThesaurus, and this is
a non-trivial task.
OK we seem to have gone in a circle. But the point is it's doable with the
right skills.
This is not a circle. See, OpenThesaurus is software, and Wordnet is
data. You need to convert the data to OpenThesaurus format (MySQL
database), and then possibly tweak OpenThesaurus code to map some of
Wordnet's relations (OpenThesaurus has only a limited set of relations).
And it's wiser to plan this beforehand, as adding relations afterward
could be harder.
You cannot setup a local Wordnet without any software as Wordnet is only
a file. You need an editing environment. You can use some other software
(there are many software packages for professional linguists - used for
building national wordnets - but they could be far too complicated for
an average user).
There you go again, barriers. Forget the barriers, I would like to see
solutions.
You'll find several tools to edit Wordnets online but some of them are
too advanced to be useful for enriching Wordnet for Australian, New
Zealand, or other version of English.
I'm suggesting that you should use OpenThesaurus. Is that clear now? And
you need a skilled NLP student to lead the team. Hire one, and the
problem is solved.
But note that this conversion does not allow any direct edition Wordnet
nor edition of OOo thesaurus.
Sorry, I'm not sure what you mean here, I'll look at Daniels scripts.
Let me reiterate: OOo thesaurus is only a file in a special format,
Daniel's scripts simply change original Wordnet format to OOo format.
There is no special editor for OOo thesaurus formatted files.
As I already said, the technical skills are available. Once the client knows
what skillset is needed he will assign the person most suitable for the job.
IT student or graduate that completed NLP courses will do, it's quite
easy to setup the environment, and quite hard to update the data when
Wordnet gets updated; relations have to be mapped thoughtfully, but it's
doable (it could be a good postgrad work). He can lead the technical
team. And several lexicographers or cognitive linguists could be needed
if you want to have it really good.
I would recommend you to contact linguistics (NLP) departments at
Australian universities.
Why Australia, I'm not Australian and surprising as it may seem, New Zealand
does have Universities.
I thought you are Australian, sorry for confusion. Take any university
from a country that needs a modified thesaurus.
Regards,
Marcin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
