An extension is only a clue
MIME type, signature, PUID, version and technical properties form the format profile.
BronVast Formats & Preservation
A file becomes sustainably manageable when its format, dependencies and history are known.
BronVast identifies formats by technical characteristics, validates internal structure where possible and records every preservation action. Original and derived versions remain demonstrably connected.
2dA BronVast
Retain, migrate or emulate
The route follows value, functionality, risk, receiving requirements and available software.
Every change as an event
Checksums before and after, tool, settings, result and responsible agent are recorded.
The route from source to lasting organisational capability
Identify
signature, PUID, MIME and version
Validate
structure, profile and readability
Assess risk
dependencies and sustainability
Perform action
retain, migrate or isolate
Validate package
object, metadata, events and manifest
Example: mixed collection
Office, email, images and databases each get the right route
One flow may suit PDF/A, while another requires the original, TIFF or a structured database export. Target format, validation and evidence are agreed for each content type.
Format policy by content type
Text, image, audio, video, databases, email, GIS/CAD and software-dependent objects each require their own assessment.
- PDF/A profiles for suitable document flows
- TIFF, JPEG and PNG according to purpose and source quality
- WAV/BWF and suitable video profiles for audiovisual material
- EML/MBOX/PST with relations, headers and attachments
- SIARD or an agreed export route for relational databases
No blind normalisation
A preferred format is not automatically the correct one. Functionality and authenticity can outweigh standardisation.
- retain original bitstream where required
- technical and functional comparison after migration
- link source, preservation and access representations
- report exceptions and failed validation explicitly
- record receiving requirements before production
What the organisation retains
Exact versions and risks
PUIDs, MIME types, signatures, profiles and dependencies per object or series.
Actions remain explainable
Events, agents, tools, checksums, results and exceptions.
Transfer without context loss
SIP, AIP, DIP, BagIt or a customer profile as agreed.
From policy to reuse
Format knowledge can check new intake immediately
Recorded signatures, validators, exceptions and acceptance rules can later flag on arrival whether a file is readable, complete and suitable for the agreed archival route.
Local by design
Format validation and migration can also run locally
Tooling, workspace, checksums, reports and migration output can stay in a segregated environment. Only validated results enter the next zone.
01Source object02Format registry03Validator04Preservation event05Information package
Technical reference points
We align the route with recognised standards and specifications where they fit the source, destination and customer responsibility. This is never presented as automatic certification.
Questions about this route
Does BronVast convert everything to PDF/A?
No. Target format depends on content, functionality, source quality, risk and receiving requirements. PDF/A fits some document flows, not every digital object.
Are original files retained?
This is decided per collection. Where authenticity, evidential value or functionality requires it, the original bitstream can remain beside preservation or access representations.
Is every package automatically E-ARK conformant?
No. BronVast can align with E-ARK structures, but conformance requires an explicit profile, implementation decisions and validation against agreed requirements.
Next step
Choose the right starting point
Start with one source, one process or a read-only assessment. We will define what should remain local, what evidence is required and which route creates value first.