- 
                Notifications
    You must be signed in to change notification settings 
- Fork 63
Description
@HolgerKnublauch wrote in #91:
- The prefixes are empty because your code just uses new PrefixMapStd() which is empty I guess.
- the SHACLC writer is really just a toy and will not work for many if not most real SHACL files... Once you convert shapes to SHACLC you'll possibly lose triples because SHACL is much richer than that.
Holger wrote "I regard the Compact Syntax as a decent way of getting definitions INTO a system, but not as an output format". However, SHACLC is much nicer to edit, so we (Onto) should fix the basic bugs, and should expand the SHACLC writer to cover as many cases as reasonable.
@yasengmarinov made a command-line tool shaclconvert that we should merge here.
@rdstn is working on SHACL generation from Ontotext Platform schemas, and we want to output both SHACL and SHACLC. Our schemas omit some "exotic" SHACL features like not and xone, and make limited use of or, so I think that's feasible.
I now have the hang of editing the spec https://w3c.github.io/shacl/shacl-compact-syntax/, so I could add bits to SHACLC if needed.