This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| CF (file format) | |
|---|---|
| Name | CF |
| Extension | .cf |
| Mime | application/x-cf |
| Owner | Common Format Consortium |
| Released | 1998 |
| Genre | container file format |
| Latest | 2.4 |
CF (file format) is a binary container and exchange format designed for cross-platform storage of structured content, metadata, and embedded resources. It facilitates interoperability among applications from vendors, open-source projects, and standards bodies by defining a compact serialized layout, schema bindings, and extension mechanisms. CF is used across publishing, scientific data interchange, multimedia production, and archival workflows.
CF is specified by the Common Format Consortium, a standards-oriented organization associated with firms such as IBM, Microsoft, Google, Apple Inc., and consortia like W3C, OASIS, IEEE, ISO. The format combines concepts from container formats pioneered by Adobe Systems, Apple Inc.'s QuickTime, and archive styles popularized by PKWARE and Rufus. CF supports hierarchical objects, typed metadata, and optional compression profiles aligned with Deflate and LZMA techniques promoted by 7-Zip contributors and SESAME research groups. The design reflects influences from scientific interchange formats used by NASA, CERN, NOAA, and academic labs at MIT, Stanford University, Harvard University, and UC Berkeley.
Work on CF began in the late 1990s as a collaboration among corporations and institutions including Sun Microsystems, Intel, Oracle Corporation, Siemens, General Electric, Siemens Healthineers, NIST, and academic partners at University of Cambridge, ETH Zurich, University of Tokyo, and Tsinghua University. Early drafts drew on archival research from Library of Congress initiatives and interoperable metadata efforts championed by Dublin Core advocates and the Getty Research Institute. Formalization occurred through workshops hosted at Internet Engineering Task Force and meetings at International Organization for Standardization panels, with influence from specifications emerging from IETF working groups and W3C community groups. Major version milestones were announced at conferences such as SIGGRAPH, USENIX, ACM SIGMOD, and IEEE VIS.
A CF file is organized as a header, a primary object table, optional chunked resource sections, and a footer index. The header contains magic bytes and version identifiers influenced by formats from Adobe Systems and Apple Inc.; it also references MIME registration practices advocated by IANA. The object table uses typed records with identifiers drawn from registries maintained by ISO and IETF and supports schemas authored in serializations similar to JSON, XML, and Protocol Buffers from Google. Resource sections embed codecs compatible with MPEG, JPEG, PNG, H.264 specifications ratified by MPEG LA and ITU. The footer index supports random access like ZIP central directory structures and optional cryptographic hashes following NIST guidance. Extensions allow binding to ontologies published by W3C members, Dublin Core, and domain authorities such as HL7 and Dublin Core projects.
Tooling for CF includes libraries, command-line utilities, and GUI integrations from vendors and open-source communities including projects hosted by Apache Software Foundation, Mozilla Foundation, Canonical Ltd., Red Hat, KDE, and GNOME. Major commercial software with import/export capabilities include suites from Adobe Systems, Microsoft, Apple Inc., Autodesk, and Avid Technology. Scientific ecosystems incorporate CF readers and writers in platforms such as MATLAB, Wolfram Research, R Project, NumPy, and SciPy-based tools developed at Los Alamos National Laboratory and Lawrence Berkeley National Laboratory. Archival and library systems at British Library, National Archives (United Kingdom), and Bibliothèque nationale de France use CF-aware ingest modules from vendors like Ex Libris and Preservica.
CF is employed in digital publishing workflows used by publishers like Penguin Random House, Elsevier, Springer Nature, and Wiley. In audiovisual production, post-production houses working with Pixar Animation Studios, Industrial Light & Magic, and broadcasters such as BBC and NBCUniversal use CF for metadata-rich asset exchange. Scientific collaborations at CERN, European Space Agency, NASA Jet Propulsion Laboratory, and Max Planck Society use CF to package simulation outputs, observational datasets, and provenance records. Government agencies such as USGS, NOAA, and European Commission adopt CF profiles for regulatory filings, compliance documents, and long-term preservation.
CF provides compatibility layers enabling interoperation with legacy formats like ZIP, TAR, RIFF, and container approaches from Matroska and ISO Base Media File Format. Gateways and converters have been implemented by open-source projects affiliated with GitHub, SourceForge, and GitLab communities, and commercial integrators from Accenture and IBM Global Services. Interoperability testing is coordinated through plugfests sponsored by W3C, Open Data Institute, European Telecommunications Standards Institute, and industry consortia including MPEG and IETF working groups.
Security considerations for CF follow guidance from NIST and follow best practices derived from incidents involving file parsing vulnerabilities reported by CERT Coordination Center and security researchers at Google Project Zero and Microsoft Security Response Center. Threats include malformed object tables, resource exhaustion attacks similar to exploits found in Adobe Reader, ImageMagick, and FFmpeg, and supply-chain concerns highlighted in reports by Krebs on Security and ENISA. Mitigations include signed manifests using cryptographic methods standardized by IETF and ISO/IEC committees, sandboxing techniques advocated by OpenBSD and Google Chrome security teams, and automated fuzzing performed by groups at University of Michigan and Carnegie Mellon University.
Category:File formats