From 8673af893754e2a893f0f09bf63809a14077d5f7 Mon Sep 17 00:00:00 2001 From: Ben Hamill Date: Mon, 17 Mar 2014 00:49:52 -0500 Subject: [PATCH] Add a range base-level constraint. --- proposals/uber-templates-mca.asciidoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/proposals/uber-templates-mca.asciidoc b/proposals/uber-templates-mca.asciidoc index 88e98a5..d7bb35d 100644 --- a/proposals/uber-templates-mca.asciidoc +++ b/proposals/uber-templates-mca.asciidoc @@ -142,6 +142,9 @@ Below is a list of proposed base-level constraints that MUST be supported if an ++:: The contents of the +value+ property contains a <> regular expression that SHOULD be applied to the field. +++:: + The contents of the +value+ property contains a range expression: a number followed by a - followed by a number. Ranges are always inclusive. For instance, +12-15+ would be satisfied by any of: 12, 13, 14 or 15. + ==== Constraint Extensibility Since constraints are established using reserved words for the +name+ property of a +data+ element, extending the list of supported constraints is done by registering a new reserved word and documenting how implementors can author and interpret that element and any possible child elements.