Figure shows a JSON-LD snippet of valid metadata expressing the measured variable/parameter using the "variablesMeasured" property of the schema.org "Dataset" Class. The workflow of defining maturity indicators as depicted in Figure starts with the identified sources of minimum reporting standards. Next, for each source, a unique identifier is created to identify the list of maturity indicators that will be created from it. The identifier is created by computing the SHA256 hash of the DOI if the source is a publication or the URL of the main website of the source otherwise. Next, the first ten characters of the hash are used as a list identifier. Next, the source is thoroughly examined to identify the variables/parameters that should be measured or reported and thus should be described as maturity indicators. After that, an identifier for each candidate maturity indicator is created according to the following template: MI-R1.3-LIST IDENTIFIER-INDICATIVE STRING. For example, in the following identifier "MI-R1.3-649848907b-MEDIA PH", the list identifier is "649848907b," and the indicative string is "MEDIA PH." Next, a copy of the properties file template is made, renamed to the created MI identifier, and filled with the extracted information from the source. The process is repeated for each variable and each source. Finally, an in-house developed Java tool is used to convert the properties files into the final formats of Markdown and Nanopublication RDF. The generator of the MIs from properties file is a command-line tool written in Java and hosted also on GitHub. The tool can be used by executing the following command from terminal: