From 0c4664e6bc4d9212f8203633d336aa01dbcd3be4 Mon Sep 17 00:00:00 2001
From: David Waltermire <david.waltermire@nist.gov>
Date: Fri, 10 Nov 2023 12:32:45 +0100
Subject: [PATCH] Added let example to specification.

---
 .../specification/syntax/constraints.md       | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/website/content/specification/syntax/constraints.md b/website/content/specification/syntax/constraints.md
index 8a0e7d68..76456ffa 100644
--- a/website/content/specification/syntax/constraints.md
+++ b/website/content/specification/syntax/constraints.md
@@ -24,6 +24,37 @@ During constraint evaluation, each `let` statement MUST be evaluated in encounte
 
 During evaluation, when a variable is bound for a `let` statement, the variables value MUST be set to the result of evaluating the `@expression` using the current node as the Metapath evaluation focus.
 
+For example:
+
+Given the following fragment of a Metaschema module.
+
+```xml
+<define-assembly name="sibling">
+  <define-flag name="name" required="yes"/>
+  <constraint>
+    <let var="parent" expression=".."/><!-- stores the parent of the current node -->
+    <let var="sibling-count" expression="count($parent/sibling)"/>
+    <expect target="." test="$sibling-count = 3"/>
+  </constraint>
+</define-assembly>
+```
+
+And the following document.
+
+```xml
+<parent name="p1">
+  <sibling name="a"/>
+  <sibling name="b"/>
+  <sibling name="c"/>
+</parent>
+<parent name="p2">
+  <sibling name="x"/>
+  <sibling name="Y"/>
+</parent1>
+```
+
+The expect constraint would pass for each `sibling` in the `parent` named "p1", and would fail for each `sibling` in the `parent` named "p2".
+
 ## Enumerated values
 
 Additionally, flags may be constrained to a set of known values listed in advance.