Baseline-information Obligations Mapping ontology

Model Openness Framework (MOF) 1.0 - SBOM Mapping

Namespace: https://w3id.org/bom/req/mof/  |  mof.ttl |  v0.1.0

SKOS concept scheme for the Model Openness Framework (MOF) Specification v1.0 (LF AI & Data Generative AI Commons, December 2024). MOF is a tiered assessment framework: if a model provides a required set of information elements under appropriate open licenses, it qualifies for a given tier (Class III: Open Model, Class II: Open Tooling Model, Class I: Open Science Model). Each tier specifies which of 17 components must be present and under which license category.

Concepts (21)

IDLabelNotationTypeDefinition
class-iClass I - Open Science ModelIThe highest class of openness. Adds 4 components (plus optional model metadata) enabling end-to-end analysis, reproduction of a similar model, and data exploration. All Class I + II + III components required.
research-paperResearch paperI.2RequirementA peer-reviewed or preprint research paper detailing model methodology, results and analysis. MUST be available in the distribution or on a permanent open access platform. MUST be released under CC-BY-4.0 or equivalent open content license. MAY replace the technical report (III.3).
datasetsDatasets (training, validation and testing)I.3RequirementAll data used for training, validation, fine-tuning, alignment (RLHF) and testing. Any media format. Includes tokenized datasets and any metadata (annotations, labels, bounding boxes, etc.). MUST be released under an appropriate open data or content license.
data-preprocessing-codeData preprocessing codeI.4RequirementAll code for preprocessing, cleaning and formatting training/validation/test data, fine-tuning data transformations, data ingestion, feature engineering, data augmentation and tokenization. MUST be released under an OSI-approved open source software license.
intermediate-parametersIntermediate model parameters (checkpoints)I.5RecommendationModel parameter checkpoints from key intermediate stages of training, in addition to the final parameters required by III.2. SHOULD be included to enable reproduction and analysis of training dynamics.
model-metadataModel metadataI.6PermissionStructured metadata about the model distribution (optional component for Class I). Provides machine-readable information about model components, their locations and relationships.
class-iiClass II - Open Tooling ModelIIBuilds on Class III. Adds 6 components enabling users to understand the training process, validate benchmarks and perform inference optimizations. All Class III + Class II components required.
training-codeTraining, validation and testing codeII.2RequirementFull code for training, validating and testing the model: model construction, training loop, hyperparameter selection, checkpointing, fine-tuning, RLHF and adapter code. MUST be released under an OSI-approved open source software license.
inference-codeInference codeII.3RequirementCode for performing inference including preprocessing, postprocessing, model optimizations and dependencies. MUST include code required to fully replicate benchmark results. MUST be released under an OSI-approved open source software license.
evaluation-codeEvaluation codeII.4RequirementCode for model evaluation and benchmarking. MUST be released under an OSI-approved open source software license.
evaluation-dataEvaluation dataII.5RequirementData used for model evaluation and benchmarking. MUST be included (standard benchmark datasets MAY be omitted if described in the report). MUST be released under a data or content appropriate open license (e.g. CDLA-Permissive-2.0 or CC-BY-4.0).
supporting-librariesSupporting libraries and toolsII.6RecommendationCode libraries, utilities and tools developed in the course of the model. SHOULD be released under an OSI-approved open source software license. Includes tokenizers, data loaders, visualisation code, container definitions, hyperparameter search code, monitoring code, frontend code.
class-iiiClass III - Open ModelIIIThe base class of openness. Requires 6 components (plus optional sample outputs) to be present and released under type-appropriate open licenses. Enables unrestricted usage, study, modification and redistribution.
model-architectureModel architectureIII.1RequirementThe ML algorithms, neural network layout, connectivity patterns, activation functions and other architectural elements. MUST be distributed as open source code under an OSI-approved open source software license.
model-parametersFinal model parameters (checkpoints and optimizer state)III.2RequirementTrained model weights and biases. At minimum the final model parameters and optimizer state MUST be distributed, compressed or uncompressed, in a format compatible with popular deep learning frameworks. MUST be released under an open license; SHOULD use an open data license (e.g. CDLA-Permissive-2.0) rather than a code license.
technical-reportTechnical reportIII.3RequirementDocumentation providing performance, usage and implication information. MUST be included in the distribution or made available on a permanent open access platform (e.g. arXiv). MUST be distributed under an open license (SHOULD be CC-BY-4.0). MAY be omitted if a research paper is provided.
evaluation-resultsEvaluation resultsIII.4RequirementDetailed quantitative metrics and qualitative results from evaluating the model. MUST include benchmark test results (standard or custom). Raw outputs MUST be distributed under an open license (SHOULD be CC-BY-4.0).
model-cardModel cardIII.5RequirementA document covering model details, intended uses, evaluation factors, risks and mitigations. MUST be distributed under an open license (SHOULD be CC-BY-4.0).
data-cardData cardIII.6RequirementSummary statistics and details about training datasets: features, instances, intended uses, motivation and collection process. MAY be combined with the model card. MUST be distributed under an open license (SHOULD be CC-BY-4.0).
sample-outputsSample model outputsIII.7RecommendationText, image, audio, code or other outputs generated by the model. RECOMMENDED but not required. If included MUST be shared publicly without copyright or restrictions where legally permitted.
mof-config-fileMOF configuration fileRecommendationA machine-readable configuration file declaring which MOF components are included in the distribution and their locations. SHOULD be included in every MOF-conformant distribution. (No direct bridge concept; closest is doc-identifier or component-external-ref.)