|
85 | 85 | {
|
86 | 86 | name: "Holger Knublauch",
|
87 | 87 | company: "TopQuadrant, Inc.",
|
88 |
| - companyURL: "http://topquadrant.com/", |
| 88 | + companyURL: "https://topquadrant.com/", |
89 | 89 |
|
90 | 90 | w3cid: 46500
|
91 | 91 | },
|
|
118 | 118 | w3cid: 58399
|
119 | 119 | }
|
120 | 120 | ],
|
121 |
| - testSuiteURI: "http://w3c.github.io/data-shapes/data-shapes-test-suite/", |
| 121 | + testSuiteURI: "https://w3c.github.io/data-shapes/data-shapes-test-suite/", |
122 | 122 |
|
123 | 123 | lint: {
|
124 | 124 | "no-unused-dfns": false, // This should be removed near the end of the process
|
@@ -500,7 +500,7 @@ <h3>Terminology</h3>
|
500 | 500 | <div class="def">
|
501 | 501 | <div class="term-def-header">Binding, Solution</div>
|
502 | 502 | <div>
|
503 |
| - A <dfn data-lt="bindings">binding</dfn> is a pair (<a data-cite="sparql12-query/#defn_QueryVariable">variable</a>, <a>RDF term</a>), consistent with the term's use in [[!sparql12-query]]</a>. |
| 503 | + A <dfn data-lt="bindings">binding</dfn> is a pair (<a data-cite="sparql12-query/#defn_QueryVariable">variable</a>, <a>RDF term</a>), consistent with the term's use in [[!sparql12-query]]. |
504 | 504 | A <dfn data-lt="solutions">solution</dfn> is a set of bindings, informally often understood as one row in the body of the result table of a SPARQL query.
|
505 | 505 | Variables are not required to be bound in a solution.
|
506 | 506 | </div>
|
@@ -1312,6 +1312,7 @@ <h4>Subjects-of targets (sh:targetSubjectsOf)</h4>
|
1312 | 1312 | ex:Bob ex:livesIn ex:NewYork .
|
1313 | 1313 | </div>
|
1314 | 1314 | </div>
|
| 1315 | + </aside> |
1315 | 1316 | <p>
|
1316 | 1317 | In the example above, only <code>ex:Alice</code> is validated against the given shape,
|
1317 | 1318 | because it is the <a>subject</a> of a <a>triple</a> that has <code>ex:knows</code> as its <a>predicate</a>.
|
@@ -1764,7 +1765,7 @@ <h5>sh:name and sh:description</h5>
|
1764 | 1765 | <h5>sh:order</h5>
|
1765 | 1766 | <p>
|
1766 | 1767 | Property shapes may have one <a>value</a> for the property <code>sh:order</code> to indicate the relative order of the property shape for purposes such as form building.
|
1767 |
| - The values of <code>sh:order</code> are decimals. |
| 1768 | + The values of <code>sh:order</code> are literals with datatype <code>xsd:decimal</code> or <code>xsd:integer</code>. |
1768 | 1769 | <code>sh:order</code> is not used for validation purposes and may be used with any type of subjects.
|
1769 | 1770 | If present at property shapes, the recommended use of <code>sh:order</code> is to sort the property shapes in an ascending order, for example so that
|
1770 | 1771 | properties with smaller order are placed above (or to the left) of properties with larger order.
|
@@ -2637,6 +2638,7 @@ <h4>sh:maxCount</h4>
|
2637 | 2638 | ex:Bob ex:birthDate "May 5th 1990" .
|
2638 | 2639 | </div>
|
2639 | 2640 | </div>
|
| 2641 | + </aside> |
2640 | 2642 | </section>
|
2641 | 2643 | </section>
|
2642 | 2644 |
|
@@ -3022,6 +3024,71 @@ <h4>sh:pattern</h4>
|
3022 | 3024 | </aside>
|
3023 | 3025 | </section>
|
3024 | 3026 |
|
| 3027 | + <section id="SingleLineConstraintComponent"> |
| 3028 | + <h4>sh:singleLine</h4> |
| 3029 | + <p class="issue"> |
| 3030 | + This feature is "at risk" pending a WG resolution on this (and similar) convenience features. |
| 3031 | + The WG is not sure yet where to draw the lines between features that should go into Core versus some other document. |
| 3032 | + Originally discussed as <a href="https://github.com/w3c/data-shapes/issues/177">Issue 177</a>. |
| 3033 | + </p> |
| 3034 | + <p> |
| 3035 | + When set to <code>true</code>, <code>sh:singleLine</code> specifies that the <a>value nodes</a> must not contain line breaks. |
| 3036 | + In addition to constraint validation, this information can be exploited by user interface builders to select between (single-lined) text fields and (multi-lined) text areas. |
| 3037 | + </p> |
| 3038 | + <p> |
| 3039 | + <span class="component-class">Constraint Component IRI</span>: <code>sh:SingleLineConstraintComponent</code> |
| 3040 | + </p> |
| 3041 | + |
| 3042 | + <div class="parameters">Parameters:</div> |
| 3043 | + <table class="term-table"> |
| 3044 | + <tr> |
| 3045 | + <th>Property</th> |
| 3046 | + <th>Summary and Syntax Rules</th> |
| 3047 | + </tr> |
| 3048 | + <tr> |
| 3049 | + <td><code>sh:singleLine</code></td> |
| 3050 | + <td> |
| 3051 | + <code>true</code> to activate this constraint. |
| 3052 | + <span data-syntax-rule="singleLine-datatype">The values of <code>sh:singleLine</code> in a shape are literals with datatype <code>xsd:boolean</code>.</span> |
| 3053 | + <span data-syntax-rule="singleLine-maxCount">A shape has at most one value for <code>sh:singleLine</code>.</span> |
| 3054 | + </td> |
| 3055 | + </tr> |
| 3056 | + </table> |
| 3057 | + <div class="def def-text"> |
| 3058 | + <div class="def-header">TEXTUAL DEFINITION</div> |
| 3059 | + <div class="def-text-body" data-validator="SingleLine"> |
| 3060 | + If <code>$singleLine</code> is <code>true</code>, then, for each <a>value node</a> that is a literal where the lexical form matches the |
| 3061 | + regular expression (as defined by the <a data-cite="sparql12-query/#func-regex">SPARQL REGEX function</a>) <code>[\f\r\n\v]</code>, there is a validation result. |
| 3062 | + </div> |
| 3063 | + </div> |
| 3064 | + <p><em>The remainder of this section is informative.</em></p> |
| 3065 | + <aside class="example"> |
| 3066 | + <p> |
| 3067 | + In this example, the valid target nodes of the shape can only contain single-lined values for <code>rdfs:label</code>. |
| 3068 | + The values of <code>rdfs:comment</code> are explicitly allowed to contain line breaks, indicating to form builders that |
| 3069 | + those values should be edited in a multi-line (text area) input widget. |
| 3070 | + </p> |
| 3071 | + <div class="shapes-graph"> |
| 3072 | + <div class="turtle"> |
| 3073 | +ex:SingleLineExampleShape |
| 3074 | + a sh:NodeShape ; |
| 3075 | + sh:property [ |
| 3076 | + a sh:PropertyShape ; |
| 3077 | + sh:path rdfs:label ; |
| 3078 | + sh:datatype xsd:string ; |
| 3079 | + sh:singleLine true ; |
| 3080 | + ] ; |
| 3081 | + sh:property [ |
| 3082 | + a sh:PropertyShape ; |
| 3083 | + sh:path rdfs:comment ; |
| 3084 | + sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; |
| 3085 | + sh:singleLine false ; |
| 3086 | + ] . |
| 3087 | + </div> |
| 3088 | + </div> |
| 3089 | + </aside> |
| 3090 | + </section> |
| 3091 | + |
3025 | 3092 | <section id="LanguageInConstraintComponent">
|
3026 | 3093 | <h4>sh:languageIn</h4>
|
3027 | 3094 | <p>
|
@@ -4753,10 +4820,10 @@ <h2>Revision History</h2>
|
4753 | 4820 | <section class="appendix informative" id="changes-12">
|
4754 | 4821 | <h2>Changes between SHACL 1.0 Core and SHACL 1.2 Core</h2>
|
4755 | 4822 | <ul>
|
| 4823 | + <li>Added the new constraint component <a href="#SingleLineConstraintComponent"><code>sh:singleLine</code></a>, see <a href="https://github.com/w3c/data-shapes/issues/177">Issue 177</a></li> |
4756 | 4824 | <li>Added the new class <a href="#ShapeClass"><code>sh:ShapeClass</code></a> for implicit class targets, see <a href="https://github.com/w3c/data-shapes/issues/212">Issue 212</a></li>
|
4757 | 4825 | </ul>
|
4758 | 4826 | </section>
|
4759 |
| - |
4760 | 4827 | </body>
|
4761 | 4828 |
|
4762 | 4829 | <script type="text/javascript">
|
|
0 commit comments