use lowercase labels

Author: gregsdennis

specs/jsonschema-core.md

@@ -43,7 +43,7 @@ interpreted as described in [RFC 2119](https://www.rfc-editor.org/info/rfc2119).
 
 The terms "JSON", "JSON text", "JSON value", "member", "element", "object",
 "array", "number", "string", "boolean", "true", "false", and "null" in this
-document are to be interpreted as defined in [RFC 8259][RFC8259].
+document are to be interpreted as defined in [RFC 8259][rfc8259].
 
 ## Overview
 
@@ -301,7 +301,7 @@ identifier structures: plain names and JSON Pointers. The
 structure: JSON Pointers.
 
 The use of JSON Pointers as IRI fragment identifiers is described in [RFC
-6901][RFC6901]. For `application/schema+json`, which supports two fragment
+6901][rfc6901]. For `application/schema+json`, which supports two fragment
 identifier syntaxes, fragment identifiers matching the JSON Pointer syntax,
 including the empty string, MUST be interpreted as JSON Pointer fragment
 identifiers.
@@ -342,7 +342,7 @@ keyword](#anchors) section.
 
 ### Range of JSON Values
 
-An instance may be any valid JSON value as defined by [JSON][RFC8259]. JSON
+An instance may be any valid JSON value as defined by [JSON][rfc8259]. JSON
 Schema imposes no restrictions on type: JSON Schema can describe any JSON value,
 including, for example, null.
 
@@ -373,7 +373,7 @@ schema authors SHOULD limit themselves to the following regular expression
 tokens:
 
 - individual Unicode characters, as defined by the [JSON
-  specification][RFC8259];
+  specification][rfc8259];
 - simple atoms: `.` (any character except line terminator);
 - simple character classes (`[abc]`), range character classes (`[a-z]`);
 - complemented simple character classes (`[^abc]`);
@@ -909,7 +909,7 @@ identified by
 (without fragments). These identifiers are used to create references between
 schema resources. When comparing IRIs for the purposes of resource
 identification, implementations SHOULD first follow the IRI normalization
-procedures defined in [RFC 3987][RFC3987], section 5.3.
+procedures defined in [RFC 3987][rfc3987], section 5.3.
 
 Several keywords can accept a relative IRI reference, or a value
 used to construct a relative IRI reference. For these keywords, it is necessary
@@ -964,8 +964,8 @@ fragments, rather than absolute IRIs as seen with `$id`.
 keyword is appended to the IRI of the schema resource containing it. As
 discussed in {{id-keyword}}, this is either the nearest `$id` in the same or an
 ancestor schema object, or the base IRI for the document as determined according
-to [RFC 3987][RFC3987] and
-[RFC 3986][RFC3986].
+to [RFC 3987][rfc3987] and
+[RFC 3986][rfc3986].
 
 In contrast, `$dynamicAnchor` operates independently of resource IRIs and is
 instead dependent on the dynamic scope of the evaluation. `$dynamicAnchor`
@@ -1167,7 +1167,7 @@ expect such features to be interoperable across implementations.
 Schemas can be identified by any IRI that has been given to them, including a
 JSON Pointer or their IRI given directly by `$id`. In all cases, dereferencing a
 `$ref` reference involves first resolving its value as a IRI reference against
-the current base IRI per [RFC 3986][RFC3986].
+the current base IRI per [RFC 3986][rfc3986].
 
 If the resulting IRI identifies a schema within the current document, or within
 another schema document that has been made available to the implementation, then
@@ -1439,7 +1439,7 @@ all annotation results), would result in a resolution failure.
 JSON has been adopted widely by HTTP servers for automated APIs and robots. This
 section describes how to enhance processing of JSON documents in a more RESTful
 manner when used with protocols that support media types and [Web
-linking][RFC8288].
+linking][rfc8288].
 
 ##### Linking to a Schema
 
@@ -1448,7 +1448,7 @@ downloadable JSON Schema using the link relation "describedby", as defined by
 [Linked Data Protocol 1.0, section 8.1](https://www.w3.org/TR/2015/REC-ldp-20150226/#link-relation-describedby).
 
 In HTTP, such links can be attached to any response using the [Link
-header][RFC8288]. An example of such a header would be:
+header][rfc8288]. An example of such a header would be:
 
 ```
 Link: <https://example.com/my-hyper-schema>; rel="describedby"
@@ -1971,7 +1971,7 @@ SHOULD use the terms defined by this document to do so.
 ## Security Considerations {#security}
 
 Both schemas and instances are JSON values. As such, all security considerations
-defined in [RFC 8259][RFC8259] apply.
+defined in [RFC 8259][rfc8259] apply.
 
 Instances and schemas are both frequently written by untrusted third parties, to
 be deployed on public Internet servers. Implementations should take care that
@@ -2010,7 +2010,7 @@ Subtype name:: schema+json
 Required parameters:: N/A
 
 Encoding considerations:: Encoding considerations are identical to those
-specified for the `application/json` media type. See [JSON][RFC8259].
+specified for the `application/json` media type. See [JSON][rfc8259].
 
 Security considerations:: See {{security}} above.
 
@@ -2031,7 +2031,7 @@ Subtype name:: schema-instance+json
 Required parameters:: N/A
 
 Encoding considerations:: Encoding considerations are identical to those
-specified for the `application/json` media type. See [JSON][RFC8259].
+specified for the `application/json` media type. See [JSON][rfc8259].
 
 Security considerations:: See {{security}} above.
 
@@ -2069,7 +2069,7 @@ name fragment identifiers.
 ```
 
 The schemas at the following locations (indicated by plain
-[JSON Pointers][RFC6901] relative to the root document) have the following base
+[JSON Pointers][rfc6901] relative to the root document) have the following base
 IRIs, and are identifiable by any listed IRI in accordance with {{fragments}}
 and {{embedded}} above.
 
@@ -2508,8 +2508,8 @@ to the document.
 
 [^19]: This section to be removed before leaving Internet-Draft status.
 
-[RFC3986]: https://www.rfc-editor.org/info/rfc3986
-[RFC3987]: https://www.rfc-editor.org/info/rfc3987
-[RFC6901]: https://www.rfc-editor.org/info/rfc6901
-[RFC8259]: https://www.rfc-editor.org/info/rfc8259
-[RFC8288]: https://www.rfc-editor.org/info/rfc8288
+[rfc3986]: https://www.rfc-editor.org/info/rfc3986
+[rfc3987]: https://www.rfc-editor.org/info/rfc3987
+[rfc6901]: https://www.rfc-editor.org/info/rfc6901
+[rfc8259]: https://www.rfc-editor.org/info/rfc8259
+[rfc8288]: https://www.rfc-editor.org/info/rfc8288

specs/jsonschema-validation.md

@@ -354,9 +354,9 @@ custom format values.
 
 These attributes apply to string instances.
 
-Date and time format names are derived from [RFC 3339, section 5.6](https://www.rfc-editor.org/info/rfc3339).
-The duration format is from the ISO 8601 ABNF as given in Appendix A of RFC
-3339.
+Date and time format names are derived from
+[RFC 3339, section 5.6](https://www.rfc-editor.org/info/rfc3339). The duration
+format is from the ISO 8601 ABNF as given in Appendix A of RFC 3339.
 
 - *date-time*: A string instance is valid against this attribute if it is a
   valid representation according to the "date-time" ABNF rule (referenced above)
@@ -424,15 +424,15 @@ representation of an IP address as follows:
 #### Resource Identifiers These attributes apply to string instances.
 
 - *uri:* A string instance is valid against this attribute if it is a valid IRI,
-  according to [RFC 3987][RFC3987].
+  according to [RFC 3987][rfc3987].
 - *uri-reference:* A string instance is valid against this attribute if it is a
   valid URI Reference (either a URI or a relative-reference), according to
   [RFC 3986](https://www.rfc-editor.org/info/rfc3986).
 - *iri:* A string instance is valid against this attribute if it is a valid IRI,
-  according to [RFC 3987][RFC3987].
+  according to [RFC 3987][rfc3987].
 - *iri-reference:* A string instance is valid against this attribute if it is a
   valid IRI Reference (either an IRI or a relative-reference), according to
-  [RFC 3987][RFC3987].
+  [RFC 3987][rfc3987].
 - *uuid:* A string instance is valid against this attribute if it is a valid
   string representation of a UUID, according to
   [RFC 4122](https://www.rfc-editor.org/info/rfc4122).
@@ -741,8 +741,8 @@ authority).
 
 Processing a media type or encoding is subject to the security considerations of
 that media type or encoding. For example, the security considerations of [RFC
-4329 Scripting Media Types](https://www.rfc-editor.org/info/rfc4329) apply when processing JavaScript or
-ECMAScript encoded within a JSON string.
+4329 Scripting Media Types](https://www.rfc-editor.org/info/rfc4329) apply when
+processing JavaScript or ECMAScript encoded within a JSON string.
 
 ## %appendix% Acknowledgments
 
@@ -859,5 +859,5 @@ to the document.
 
 [^6]: This section to be removed before leaving Internet-Draft status.
 
-[RFC3987]: https://www.rfc-editor.org/info/rfc3987
-[RFC8259]: https://www.rfc-editor.org/info/rfc8259
+[rfc3987]: https://www.rfc-editor.org/info/rfc3987
+[rfc8259]: https://www.rfc-editor.org/info/rfc8259