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

consider edmondchuc/shaclc #69

Open
VladimirAlexiev opened this issue Aug 2, 2024 · 1 comment
Open

consider edmondchuc/shaclc #69

VladimirAlexiev opened this issue Aug 2, 2024 · 1 comment

Comments

@VladimirAlexiev
Copy link
Contributor

hi @edmondchuc!
I'll add your implementation https://github.com/edmondchuc/shaclc/ to the list that we keep

@edmondchuc
Copy link

Hi @VladimirAlexiev, thanks for considering my implementation. I currently don't have a use for SHACLC, so can't really provide any meaningful input as to what a SHACLC 1.2 should look like. But I am happy to stay up to date with what you and the rest of the SHACLC WG propose and potentially implement those new additions to my python lark implementation and provide it as implementation evidence to the WG.

From memory, I think the lark grammar is faithfully produced from https://w3c.github.io/shacl/shacl-compact-syntax/#grammar-section. The only thing I remember deviating from the grammar is to allow for case-insensitive keywords. For example, PREFIX, Prefix, prefix are all valid.

You can play around with the lark grammar by using this browser IDE and pasting the lark grammar there to see what AST is produces.

There's also a shaclc playground online here where you can see how the shaclc syntax is converted into normal RDF SHACL syntax.

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