-
Notifications
You must be signed in to change notification settings - Fork 5
Maintain updated list of SHACL implementations #78
Comments
I wanted to mention an "awesome" list. Maybe we could simply have an "Awesome SHACL" in a repo. Easy to maintain, easy to contribute |
Yeah the original impl report was obviously only created to pass the W3C process for SHACL 1.0. Yes it would be great to have a better, living document somewhere. |
@tpluscode I like Awesome lists, as soon as we agree to add basic info like latest version and last update date, link to Playground implementation (if any).
|
Turns out that I posted an internal task 3.5y ago. Here are details from that task. Why:
Task
Sources:
Tech notes
|
@tpluscode can you check https://github.com/sindresorhus/awesome to see whether an Awesome list should be in its own repo? @tpluscode and @HolgerKnublauch what'd be a good location for our awesome list? Maybe https://github.com/w3c/data-shapes/awesome-semantic-shapes ? |
On the location, I consider the data-shapes repo historic and done. The shacl repo would IMHO be better, |
I really like the idea of an awesome-semantic-shapes repo and I think if you want to include resources about SHACL and ShEx, it would make sense to call it semantic shapes so it could include resources from both. I would be happy to contribute or help maintaining it as well. |
Maybe its better to go with https://github.com/w3c/awesome-semantic-shapes? (if W3C allows it on a top level) There are some advantages in a 'separate repo' approach:
|
Another option is to create a vendor-neutral GitHub organization like 'swcommons' or something similar, separate from w3c. An organizaion, open to all representatives from SW and related vendors and established experts. Then it will be https://github.com/swcommons/awesome-semantic-shapes. |
A working group or a community group can have several repos - the RDF-star working group has one repo per document. The charter for the SHACL-WG could include the possibility of becoming a "maintenance and new feature" on-going working group after the charter for new work has been completed. This enables errata to be handled in a timely manner. SHACL issue : #80 It may be possible to put community reviewed, non-specification, material under that group. It could also be under a Community Group (this repo is owned by the SHACL Community Group; other community groups can be created). The RDF tests maintenance works on this basis. |
@pchampin or @iherman can you please make a repo @amivanoff could you please take a first stab at it? Make the structure as per Then it will be much easier for me to add content. |
Remove my name from the owners list. |
Removed Andy and added @tpluscode to "owner list". JS implementations:
|
I'm assuming that this repo would be owned by the SHACL CG, correct? |
Created the repo: https://github.com/w3c-cg/awesome-semantic-shapes |
w3c-cg/awesome-semantic-shapes#1 . Mentioned @amivanoff but cannot assign yet. |
Sorry for mis-posting, I moved questions to a separate issue |
The final location is https://github.com/w3c-cg/awesome-semantic-shapes and it's looking pretty good! |
The official Implementation Report https://w3c.github.io/data-shapes/data-shapes-test-suite/ is 5 years old and badly obsolete. validatingrdf/validatingrdf.github.io#14 collected
https://github.com/validatingrdf/validatingrdf.github.io/wiki/Updated-list-of-implementations that is perhaps 3 years newer has these rubrics:
But it has several defects:
The text was updated successfully, but these errors were encountered: