Improve meta-schema consistency

schemas/README.md

@@ -60,7 +60,7 @@ The following makefile target processes all Property Definitions (and other sche
 ```
 make schemas
 ```
-This command also generates documentation in markdown and HTML meant to be keept alongside the JSON definition files.
+This command also generates documentation in markdown and HTML meant to be kept alongside the JSON definition files.
 Once the generation is complete, the property definitions are found under `schemas/output/defs/` using the same directory structure as under `schemas/src`.
 
 You can browse the definitions by starting a browser with the generated index page, e.g.:

schemas/src/meta/v1.2/optimade/property_definition.yaml

@@ -227,7 +227,7 @@ $defs:
  - "iri": a string instance is valid against this attribute if it is a valid IRI according to RFC 3987.
  type: "string"
  enum: ["date-time", "date", "time", "duration", "email", "uri", "iri"]
- $id:
+ "$id":
  allOf:
  - $ref: '#/$defs/id_field'
  - description: |-
@@ -238,7 +238,7 @@ $defs:
  - The inclusion or omission of "null" in the type in the outermost layer of the definition.
  - Additions of annotating notes to end of the description field.
  - Changes to the following specific fields at any level: deprecated, examples, $comment, x-optimade-implementation, and x-optimade-requirements.
- $schema:
+ "$schema":
  description: |-
  A normalized URI for a meta-schema that validates the Property Definition.
  This SHOULD be https://schemas.optimade.org/meta/{OPTIMADE_VERSION}/optimade/physical_unit_definition.json
@@ -344,7 +344,7 @@ $defs:
  - "no"
  sortable:
  type: boolean
- $comment:
+ "$comment":
  type: string
  type: object
  x-optimade-requirements:
@@ -396,7 +396,7 @@ $defs:
  - should
  - may
  type: string
- $comment:
+ "$comment":
  type: string
  type: object
  x-optimade-metadata-definition:
@@ -408,7 +408,7 @@ $defs:
  type:
  enum:
  - ["object", "null"]
- $comment:
+ "$comment":
  description: |-
  A human-readable comment relevant in the context of the raw definition data.
  These comments should normally not be shown to the end users.

schemas/src/meta/v1.2/optimade/unit_entity_definition.yaml

@@ -19,7 +19,7 @@ $defs:
  patternProperties:
  "^_": {}
  properties:
- $id:
+ "$id":
  allOf:
  - $ref: "#/$defs/id_field"
  - description: |-
@@ -33,9 +33,9 @@ $defs:
  - Changes to the fields `deprecated` and `$comment` on any level.
 
  Note that this means that the version number part of the URL is *retained* even in newer releases of the OPTIMADE standard as long as the definition remains functionally identical.
- $comment:
+ "$comment":
  type: string
- $schema:
+ "$schema":
  description: |-
  A normalized URI for a meta-schema that validates the definition.
  approximate-relations: