Should reference-board files work across apps? I published an open format proposal

While building ArtDeck, I ran into a broader problem: a board saved in one reference app usually cannot be opened in another. Exporting a flattened image preserves its appearance, but loses the layout, original media, notes, groups, links, and editability.

I have published an experimental proposal called the Open Reference Board Format, or ORBF. It defines a portable package containing JSON board data and its media. The current draft covers images, animated images, video, text, URLs, drawings, groups, transforms, and stacking order.

Long-term access is also one of the main goals. Users should not need the original reference-board app just to recover their content. A standalone ORBF file is a ZIP package that can be opened with an ordinary archive tool. The board description is readable JSON, and the media files can be extracted directly. Even if no compatible editor is available years later, the user is not locked out of the material stored in the board.

Applications can keep their native formats and store app-specific behavior separately.

ArtDeck motivated the work, so I have documented that relationship openly. It receives no privileged treatment in the format. ORBF is a separate open project, and I have not shipped ORBF support in ArtDeck yet. No other application currently claims support either.

I’m publishing the proposal now because this is the point where outside criticism can still change it. If you build a reference-board, moodboard, or canvas application, I would be interested in anything the current model gets wrong. If you use these tools, which parts of a board would you expect to survive when moving it to another app?

Repository:
https://github.com/AlexandreAlvesDB/open-reference-board-format

The project is open to discussion and contributions through GitHub. Private feedback is welcome too.