We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The ShEx 2.0 grammar included a construct to prevent a shapeExpression label from referring directly to another shapeExpression label, e.g.
<S1> @<S2>
The construct in question:
[10] shapeExpression ::= "NOT"? shapeAtomNoRef shapeOr? | "NOT" shapeRef shapeOr? | shapeRef shapeOr [12] shapeOr ::= ("OR" shapeAnd)+ | ("AND" shapeNot)+ ("OR" shapeAnd)*
These patches remove that restriction:
PROPOSE: accept this [pending] change for ShEx 2.1
The text was updated successfully, but these errors were encountered:
~ grammar cleanup before addressing [shexSpec/shex#88]
8e20754
~ Allow direct shapeExpression aliases [shexSpec/shex#88]
d5490da
867bb94
+ directShapeExpression negative syntax
304a069
[shexSpec/shex#88]
Note also that if we wanted to allow annotations/semActs on start rules without this change, we can't se shapeExpression directly:
shapeExpression
- [6] | start | ::= | "start" '=' inlineShapeExpression + [6] | start | ::= | "start" '=' shapeAnd ("OR" shapeAnd)*
Sorry, something went wrong.
No branches or pull requests
The ShEx 2.0 grammar included a construct to prevent a shapeExpression label from referring directly to another shapeExpression label, e.g.
The construct in question:
These patches remove that restriction:
This never made it into the Antlr Grammar
PROPOSE: accept this [pending] change for ShEx 2.1
The text was updated successfully, but these errors were encountered: