search

shexSpec / spec

ShEx specification
https://shexspec.github.io/spec/
Other
14 stars 10 forks source link

Why not use ShExC for the readable spec? #11

Closed patrickdlogan closed 5 years ago

patrickdlogan commented 7 years ago

It's not clear to me why the spec states that ShExC is intended for human readability vs. ShExJ but then proceeds to use ShExJ for the human-readable spec. I appreciate the Primer provides an option to switch between the two formats. It could be helpful for the spec to have this option or to use ShExC exclusively.

If this is desired and there is some effort involved I would like to make the conversion as part of learning more about ShEx.

ericprud commented 6 years ago

(Apologies for taking so long to mention this but...) the ShEx spec includes buttons to switch between ShExJ and ShExC. The definitions are still in terms of the ShExJ because they rely on the specificity of e.g. EachOf([TE1, TE2]) vs. something that would include parsing a la { TE1 ; TE2 }.

ericprud commented 5 years ago

Given that the primer defaults to ShExC and that the spec requires an AST, I'm closing this issue with no change. If this is not satisfactory, please re-open the issue and provide an example of how ShExC could be used for e.g. triple expression semantics.