MIRIAM n/a http://biomodels.net/miriam/ Taken direct from the web-available version (HTML) on 2011-06-14 by Chris Taylor (chrisftaylor@gmail.com). Reference correspondence The model must be encoded in a public, standardized, machine-readable format SBML, CellML, GENESIS The model must comply with the standard in which it is encoded The model must be clearly related to a single reference description If a model is composed from different parts, there should still be a description of the derived/combined model. The encoded model structure must reflect the biological processes listed in the reference description The model must be instantiated in a simulation All quantitative attributes have to be defined, including initial conditions. When instantiated, the model must be able to reproduce all results given in the reference description within an epsilon (algorithms, round-up errors) Attribution annotation The model has to be named A citation of the reference description must be joined The citation should permit to identify the authors of the model. complete citation, unique identifier, unambigous URL The name and contact of model creators must be joined The date and time of creation and last modification should be specified A history is useful but not required. The model should be linked to a precise statement about the terms of distribution MIRIAM does not require “freedom of use” or “no cost”. External resource annotation The annotation must permit to unambiguously relate a piece of knowledge to a model constituent The referenced information should be described using a triplet (i) The data type should be written as a Uniform Resource Identifier (URI). (ii) The identifier is analysed within the framework of the data type. (iii) Data type and identifier can be combined in a single URI, such as: urn:miriam:dataType:identifier. For example: urn:miriam:uniprot:P62158. (iv) Qualifiers (optional) should refine the link between the model constitutent and the piece of knowledge: “has a”, “is version of”, “is homolog to”, etc. {data type, identifier, qualifier} The community has to agree on a set of standard valid URIs A database and the associated API (Web Services) have been developed at the EBI to provide the generation and interpretation of URIs.