# items.properties.attachmentPointer.$comment
The absolute JSON Pointer, in string form, of the position to which this resolved link applies

# items.properties.contextPointer.$comment
The absolute JSON Pointer to the location in the instance that is the context of the link.  If the context resource supports JSON Pointer fragments, this will the string form of the identical JSON Pointer

# items.properties.contextUri.$comment
The fully resolved URI of the link context, including a fragment if it is possible to construct one for the given media type and instance

# items.properties.hrefInputTemplates.$comment
The list of partially resolved URI Templates, starting with "href", followed by applicable "base" values from nearest to furthest.

# items.properties.hrefPrepopulatedInput.$comment
The initial data set to be presented with the input form when URI Template input is accepted.

# items.properties.hrefPrepopulatedInput.propertyNames.$comment
These are all URI Template variable names, specifically the 'varname' production from RFC 6570, Section 2.3

# $defs.https://schemas.sourcemeta.com/jsonschema/2019-09/schema.title
Core and Validation specifications meta-schema

# $defs.https://schemas.sourcemeta.com/jsonschema/2019-09/schema.properties.dependencies.$comment
"dependencies" is no longer a keyword, but schema authors should avoid redefining it to facilitate a smooth transition to "dependentSchemas" and "dependentRequired"

# $defs.https://schemas.sourcemeta.com/jsonschema/2019-09/schema.properties.definitions.$comment
While no longer an official keyword as it is replaced by $defs, this keyword is retained in the meta-schema to prevent incompatible extensions as it remains in common use.