Make print settings portable without making our machines public

As a makerspace maintainer, I want every 3D-print file to support an open, optional metadata bundle: printer calibration, nozzle size, filament type, temperature range, and slicer settings. That would make distributed fabrication, repairs, and reproducing someone else’s prototype much less dependent on undocumented vendor profiles or cloud dashboards. Open formats such as 3MF already demonstrate that models can carry structured manufacturing metadata, and slicer project files can preserve printer, material, and print profiles.

I don’t think this should mean publishing a machine’s identity or an entire proprietary workflow. I’d standardize two records: a private calibration record for offsets, fingerprints, and maintenance, plus a shareable production record for the settings needed to reproduce the result. Both should be removable and locally owned. Would you support that community standard, or keep everything strictly opt-in? How do you document settings now?

The two-record split is the important part. A single blob encourages people to copy machine-specific values blindly, which is exactly how “works on my printer” becomes damaged hardware. Make the production record declarative and let the receiving slicer validate it against local capabilities before anything runs.

I’d support the format only if privacy is designed in, not added as a warning label later. Supplier names, serial-like identifiers, and unusual calibration values can become fingerprints even when nobody intended them to. Public export should have a deliberate redaction step, with the default being the least revealing useful record.

The adoption hurdle is less technical than behavioral. Most people won’t fill out another form, and vendors will prefer dashboards that keep users inside their ecosystem. Make common slicers write sensible defaults automatically, then let advanced users edit the bundle. Otherwise the standard will exist mainly for careful enthusiasts.

I’m wary of standardizing a file format for information people already fail to maintain. A plain text README beside the model is sometimes more durable than another metadata schema. Still, if the bundle is optional, human-readable, and never required for a basic print, I don’t see much downside.