Descriptive metadata associated with the workflow makes it easier to find over different search engines and repositories, so providing as much relevant metadata as possible is recommended. The metadata can include information and contact of developers, detailed descriptions and types of input and output data, names and versions of different tools, packages, and software integrated into the workflow, keywords, context, and the software's licence, and more. Obliging to the best practices, specific ontologies are used to represent certain digital objects consistently. For MAW, we integrated the EDAM ontology to describe the .mzML format for input files, a specific format for LC-MS data. An .mzML file uses XML Schema to describe comprehensive information for a single LC-MS run, including data and metadata. This can be achieved via CWL (details in the subsequent section on 2.2.3 Interoperability subsection I1). The EDAM ontology is added to the input YAML file for CWL as the format for the .mzML file using the full URL: . The descriptive metadata is also used for making the workflow findable over the "web of life sciences". To achieve this, Bioschemas domain-specific profiles make available semantic markup, consisting of metadata, to the web search engines specific to the life sciences domain . Bioschemas provide community-specific types and profiles with agreed vocabularies that can be required, recommended, or optional. WorkflowHub initiated the type and profile for workflows, termed "ComputationalWorkflow". This Bioschemas document can be generated using the examples in .