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

[Feature Request]: N3 Support using vscode-extension-n3 #9

Closed
jeswr opened this issue Jan 11, 2023 · 3 comments
Closed

[Feature Request]: N3 Support using vscode-extension-n3 #9

jeswr opened this issue Jan 11, 2023 · 3 comments

Comments

@jeswr
Copy link
Contributor

jeswr commented Jan 11, 2023

As I raised in william-vw/vscode-extension-n3#1; it would be great of this extension could support Notation3 syntax by using the https://github.com/william-vw/vscode-extension-n3 extension.

@RinkeHoekstra
Copy link
Collaborator

I had a quick look at the n3 extension, interesting stuff!

What features would you like this extension to support? I don't immediately have a good idea of how useful it would be to convert from n3 to other formats, as the rules are not supported in any of the others. Also, visualising rules as a graph is tricky.

Ideas welcome :-)

@jeswr
Copy link
Contributor Author

jeswr commented Apr 1, 2023

What features would you like this extension to support?

The main one would be syntax highlighting so you get that out of the box when installing this extension.

I don't immediately have a good idea of how useful it would be to convert from n3 to other formats, as the rules are not supported in any of the others.

The way libraries like N3.js treat this is by interpreting { :a :b :c } => { :d :e :f }

as the following n-quads

@prefix log: <http://www.w3.org/2000/10/swap/log#> .

:a :b :c _:b0 .
:a :b :c _:b1 .
_:b0 log:implies _:b1 .

There are a bunch of edge cases where N3 doesn't interoperate with generalized RDF (e.g. how do you express the empty graph in an example like this); which I would like to see resolved at the N3 standard level in the long term, but I don't think this is something that needs to be worried about in this extension, it can just use the existing behavior of N3.js (I'm currently working to make it comply with the latest version of the N3 standard btw rdfjs/N3.js#341).

@RinkeHoekstra
Copy link
Collaborator

@jeswr I still like your N3 extension (though I'm not using it myself), but wouldn't anyone who wants this support just install your extension?

I can't think of anything that my extension would offer above and beyond yours. Happy to be proven wrong though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants