Merge pull request #480 from w3c/issue-479

#479: Clarified that sh:order can take xsd:integers

Author: VladimirAlexiev

shacl12-core/index.html

@@ -7492,7 +7492,7 @@ <h3>sh:order</h3>
 				<p>
 					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.
-					The values of <code>sh:order</code> are decimals.
+					The values of <code>sh:order</code> are <a>literals</a> with <a>datatype</a> <code>xsd:decimal</code> or <code>xsd:integer</code>.
 					<code>sh:order</code> is not used for validation purposes
 					and may be used with any type of subjects.
 					If present at property shapes, the recommended use of <code>sh:order</code> is to sort the
@@ -7970,6 +7970,7 @@ <h2>Changes between SHACL 1.0 Core and SHACL 1.2 Core</h2>
 				<li>The values of <a href="#ClassConstraintComponent"><code>sh:class</code></a> and <a href="#DatatypeConstraintComponent"><code>sh:datatype</code></a> can now also be lists, indicating a union of choices; see <a href="https://github.com/w3c/data-shapes/issues/160">Issue 160</a></li>
 				<li>Added the new constraint component <a href="#ReifierShapeShapeConstraintComponent"><code>sh:ReifierShape</code></a>; see <a href="https://github.com/w3c/data-shapes/issues/300">Issue 300</a></li>
 				<li>Added parameter <a href="#subClassOfInShapesGraph"></a> to look up rdfs:subClassOf triples in the union of the shapes graph and the data graph; see <a href="https://github.com/w3c/data-shapes/issues/185">Issue 185</a></li>
+				<li>Generalized <a href="#order"></a> to also allow xsd:integers; see <a href="https://github.com/w3c/data-shapes/issues/479">Issue 479</a></li>
 			</ul>
 		</section>