You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So you can write nonsense like deactivated <foo> or even minInclusive (<foo> <bar>).
Tighten the grammar to provide appropriate value type per property.
This way LSP (#50) can validate and guide the user into entering an appropriate value.
The text was updated successfully, but these errors were encountered:
VladimirAlexiev
changed the title
SHACLCL: tighten grammar re nodeValue, propertyValue
SHACLC: tighten grammar re nodeValue, propertyValue
Apr 12, 2024
@jeswr
Currently nodeValue, propertyValue take the same values (iri, literal, array)
regardless in which nodeParam, propertyParam they are used.
So you can write nonsense like
deactivated <foo>
or evenminInclusive (<foo> <bar>)
.Tighten the grammar to provide appropriate value type per property.
This way LSP (#50) can validate and guide the user into entering an appropriate value.
The text was updated successfully, but these errors were encountered: