Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for OWL files #122

Open
Bleyddyn opened this issue Aug 18, 2024 · 4 comments
Open

Add support for OWL files #122

Bleyddyn opened this issue Aug 18, 2024 · 4 comments
Labels
suggested enhancement Enhancement, which is not planned yet for being worked on

Comments

@Bleyddyn
Copy link

I'm planning on trying to add support for reading and maybe writing OWL files. A very simple example is at https://www.ibm.com/docs/en/wsr-and-r/8.5.0?topic=wsrr-example-owl-file

I realize this is a bit out of the way for VYM, so if there's no interest I'll stick to my own fork.

Knowledge Graphs (OWL files are sometimes used to store KG data) and Mind Maps are at least related concepts, and I have another project that I hope will be working with that kind of data, so I thought I'd give it a shot.

@insilmaril insilmaril added the suggested enhancement Enhancement, which is not planned yet for being worked on label Aug 20, 2024
@insilmaril
Copy link
Owner

Certainly an interesting idea. When vym was very young (nearly 20 years ago...) The former CTO of the company where I worked suggested to use RDF, so somehow this would close a circle ;-)

For parsing OWL files maybe a modified version of the xml-vym.cpp parser could be used, which I rewrote to use QXmlStreamReader. Not sure what would be best approach for saving in .vym files, using branches and xlinks or introducing a new type to reflect the ontologies. Guess this depends on you use case, if you rather would use vym to display only or really work with it.

I'd just try to keep the overhead as small as possible avoid slowing down working with "normal" maps.

Btw. ksemantic also aimed for semantic maps, but I haven't checked it for years now...

I'd help where I can.

So far I have been basically working alone on vym, very rarely getting a patch. If you join I'd be a bit more careful with the develop branch ;-)

My plan is at the moment to stabilize vym for a 3.0 release, especially the MapDesign elements and also some rare crash on Windows I haven't been able to locate really so far. On develop branch I am also playing a bit with scripting an elastic animated layout (faster than recompiling for every change, but here again something causes a crash after a number of iterations.

@Bleyddyn
Copy link
Author

Thanks for the pointers. I would like to be able to read and write OWL files, as well as saving them as .vym, but we'll see how well that fits.

If there are any other issues you want help with for 3.0, let me know.

@insilmaril
Copy link
Owner

Oh, I have tons of ideas :-)

The next couple of weeks I won't have much time and at least on Windows executing scripts (e.g. for function key macros and undo/redo) crash sporadically. Trace is deep in QJSEngine usually and could be a race condition, I'll open an issue in the next days, so if you have experience there... I am bit lost with ideas how to fix that atm.

@insilmaril
Copy link
Owner

The new crash bug: #124

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggested enhancement Enhancement, which is not planned yet for being worked on
Projects
None yet
Development

No branches or pull requests

2 participants