|
143 | 143 | <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
|
144 | 144 | <table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
|
145 | 145 | <tr><td class="header">Internet Engineering Task Force</td><td class="header">fge. Galiegue</td></tr>
|
146 |
| -<tr><td class="header">Internet-Draft</td><td class="header">January 21, 2013</td></tr> |
| 146 | +<tr><td class="header">Internet-Draft</td><td class="header">January 25, 2013</td></tr> |
147 | 147 | <tr><td class="header">Intended status: Informational</td><td class="header"> </td></tr>
|
148 |
| -<tr><td class="header">Expires: July 25, 2013</td><td class="header"> </td></tr> |
| 148 | +<tr><td class="header">Expires: July 29, 2013</td><td class="header"> </td></tr> |
149 | 149 | </table></td></tr></table>
|
150 | 150 | <h1><br />JSON Schema: interactive and non interactive validation<br />json-schema-validation</h1>
|
151 | 151 |
|
@@ -175,7 +175,7 @@ <h3>Status of This Memo</h3>
|
175 | 175 | It is inappropriate to use Internet-Drafts as reference material or to cite
|
176 | 176 | them other than as “work in progress.”</p>
|
177 | 177 | <p>
|
178 |
| -This Internet-Draft will expire on July 25, 2013.</p> |
| 178 | +This Internet-Draft will expire on July 29, 2013.</p> |
179 | 179 |
|
180 | 180 | <h3>Copyright Notice</h3>
|
181 | 181 | <p>
|
@@ -758,7 +758,7 @@ <h3>Table of Contents</h3>
|
758 | 758 | <p>
|
759 | 759 | A string instance is considered valid if the regular
|
760 | 760 | expression matches the instance successfully. Recall: regular
|
761 |
| - expressions are not anchored. |
| 761 | + expressions are not implicitly anchored. |
762 | 762 |
|
763 | 763 | </p>
|
764 | 764 | <a name="anchor36"></a><br /><hr />
|
@@ -1234,7 +1234,7 @@ <h3>Table of Contents</h3>
|
1234 | 1234 |
|
1235 | 1235 | </p>
|
1236 | 1236 | <p>
|
1237 |
| - The set still contains two elements, "" and "fiddle". Validation |
| 1237 | + The set "s" still contains two elements, "" and "fiddle". Validation |
1238 | 1238 | therefore fails.
|
1239 | 1239 |
|
1240 | 1240 | </p>
|
@@ -1620,14 +1620,22 @@ <h3>Table of Contents</h3>
|
1620 | 1620 | Implementation requirements</h3>
|
1621 | 1621 |
|
1622 | 1622 | <p>
|
1623 |
| - Implementations MAY support the "format" keyword. If they choose to support this |
1624 |
| - keyword, they MUST implement validation for attributes defined below. They MAY |
1625 |
| - add custom format attributes. |
| 1623 | + Implementations MAY support the "format" keyword. Should they choose to do so: |
| 1624 | + |
| 1625 | + </p> |
| 1626 | +<blockquote class="text"> |
| 1627 | +<p>they SHOULD implement validation for attributes defined below; |
| 1628 | +</p> |
| 1629 | +<p>they SHOULD offer an option to disable validation for this keyword. |
| 1630 | +</p> |
| 1631 | +</blockquote><p> |
| 1632 | + |
1626 | 1633 |
|
1627 | 1634 | </p>
|
1628 | 1635 | <p>
|
1629 |
| - Save for agreement between parties, schema authors SHALL NOT expect a peer |
1630 |
| - implementation to support this keyword and/or custom format attributes. |
| 1636 | + Implementations MAY add custom format attributes. Save for agreement between |
| 1637 | + parties, schema authors SHALL NOT expect a peer implementation to support this |
| 1638 | + keyword and/or custom format attributes. |
1631 | 1639 |
|
1632 | 1640 | </p>
|
1633 | 1641 | <a name="anchor107"></a><br /><hr />
|
|
0 commit comments