search

goodmami / wn

A modern, interlingual wordnet interface for Python
https://wn.readthedocs.io/
MIT License
197 stars 19 forks source link

Graph Vizualization #149

Open fcbond opened 2 years ago

fcbond commented 2 years ago

It would be great to add the graph visualization code @ekaf added to NTLK.

See: https://github.com/nltk/nltk/commit/8f9132589700205c3387f303a5a282f3221c70b6

Although @goodmami may consider this out of scope, ...

goodmami commented 2 years ago

Yes, those graphs look very nice and useful.

And you're right that I currently consider it out of scope, but I'll think about it as I reevaluate the role Wn serves (for instance, I'm adding the describe() function and wn.validate module). One thing I've thought about is adding some web API endpoints for relation paths so that a web frontend could construct the visualizations (e.g., in SVG) using the data in the response.

arademaker commented 2 years ago

An web interface would be nice! Is there any general documentation about the architecture of the lib and plans?

arademaker commented 2 years ago

On the other hand, another project for a web interface can be a wrapper to wn

goodmami commented 2 years ago

@arademaker The idea is that the web client would be a separate project, similar to how delphin-viz works on top of the web API provided by other tools.

On the topic of scope creep, the existing wn.web module is already a bit excessive, and it could easily be spun out into a separate package. If we start having multiple related codebases, it might make sense to create a GitHub organization for them, or maybe put them under globalwordnet or something.

edit: note that the above paragraph is just some thoughts, and not concrete plans

goodmami commented 2 years ago

After talking with @fcbond, I think we'll stick with with a monolithic model for now and spin out modules later if we need a leaner package. So I think this could be included somehow in Wn. To that end, some notes: