-
Notifications
You must be signed in to change notification settings - Fork 30
Add something similar to dash:singleLine
#177
New issue
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
Labels
Core
For SHACL 1.2 Core spec
Comments
dash:singleLine
HolgerKnublauch
added a commit
that referenced
this issue
Feb 23, 2025
HolgerKnublauch
added a commit
that referenced
this issue
Feb 24, 2025
HolgerKnublauch
added a commit
that referenced
this issue
Feb 25, 2025
HolgerKnublauch
added a commit
that referenced
this issue
Feb 25, 2025
* #177: Added sh:singleLine * #177: Added \f and \v * Update shacl12-core/index.html Co-authored-by: Ted Thibodeau Jr* Update shacl12-core/index.html Co-authored-by: Ted Thibodeau Jr * Update shacl12-vocabularies/shacl.ttl Co-authored-by: Ted Thibodeau Jr * #177: Marked feature "At Risk" --------- Co-authored-by: Ted Thibodeau Jr
In the Feb 24 meeting the WG accepted this feature into core, but marked as "At risk" which means that the WG will revisit the inclusion of this feature when it has gathered more evidence about the actual need. In a nutshell, the concern is where to draw the line and whether adding too many little features will open the floodgates. |
HolgerKnublauch
added a commit
that referenced
this issue
Mar 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dash:singleLine (https://datashapes.org/constraints.html#SingleLineConstraintComponent) can be used to specify that string values must not contain line breaks. This is commonly used for things like labels or ID strings.
While this can be expressed with sh:pattern, it is better to have an explicit boolean for this. For example, user interface builders can determine whether they should display a textfield vs a textarea.
The text was updated successfully, but these errors were encountered: