meta_header_filename is provided for this schema, its
meta root parameter
is used to replace the schema’s
TODO: merge meta entries
The class name is derived from the file’s “$id” value, assuming a canonical
path structure with the class name post-pended with a version:
Processing is skipped if the class name does contain other than word / dot / dash characters, or if a filter had been provided and the class name does not match.
The documentation is extracted from the YAML schema file and formatted into markdown content, producing
.mdfile in the output directories of the original repository (
A rudimentary CURIE to URL expansion is performed for prefixes defined in the configuration file. An example would be the linking of an ORCID id to its web address.
Paths for output files are created based on the values (e.g.
provided in the configuration file.
The web files for the Jekyll / GH-pages processing receive a prefix, to ensure
that auto-generated and normal pages can co-exist. The
provided in the YAML header of the Jekyll file provides a “nice” and stable
name for the generated HTML page (independent of the original file name).
The class “$id” values are assumed to have a specific structure, where
The property overview is followed by the listing of the properties, including descriptions and examples.
A version of the Markdown inline documentation is added to the Github (or alternative), Jekyll based website source tree.
The page will only be generated into an HTML page if it contains a specific header written in YAML.
_create_jekyll_header function will pre-pend such a header to the Markdown
page, including some file specific parameters such as the
permalink address of
In the current JSON Schema specification there is a problem with “$ref”-type attribute types: If a reference is given, additional attributes of the property (examples, description) are being ignored. This isn’t very helpful, since information specific to the property’s instantiation will not be displayed.
This behaviour can be alleviated by wrapping the
$ref and other attributes
allof statement (which is interpolated in the following, to expose
the attributes). We’ll hope for a more elegant solution …
This function remaps the list of property attributes required from using a ‘$ref’ property definition to a standard object, which is then processed for documentation in the usual way.
This function expands prefixes in identifiers, based on the parameters provided
config.yaml. This is thought as a helper for some script/website specific
linking, not as a general CURIE expansion utility.