Meeting №2 Recap
Designing interoperable extensible formats for spatial canvases to support diverse tools and handle unknown objects effectively.
If you have any questions, comments, or corrections, please add them to the discussion post on GitHub.
Meeting №2 Recap
Here's the recording of the meeting, if you'd like to watch.
Here's a transcript of the meeting, if you'd prefer to read.
Agenda
Alignment on what "interop" means for OCWG
Exploring the needs of "non-whiteboard" canvases
Handling unknown shapes/objects (should we show positions? bounding boxes? nothing at all?)
Freehand drawing support
Global vs localised and per-shape schemas
Meeting 2 Summary:
The shared goal for the group is to design a least-common denominator extensible format that sits between visual and structural canvases, allowing them to interoperate.
Defining Interop: Discussion opened on defining what interoperability between spatial canvas tools entails, focusing on non-whiteboard types like system diagrams. Concerns include integrating new schema versions and handling objects unsupported by some tools.
Utility Libraries and Integration: Suggestion to create utility libraries to aid integration and manage schema migrations, reflecting a need for ongoing support as tools evolve.
Schema Scope and Localization: Debated whether a unified base schema suffices or if more localized schemas are necessary, considering the diversity in canvas tool functionalities and the specific requirements of certain shapes or objects. One major point in favor of localized schemas was copy-paste support, where the content being added is individual objects, not a whole document.
Visual and Structural Integrity in Interop: Discussed how to maintain visual properties across different tools without compromising the structural and relational integrity.
Nodes and Edges Representation: Extensive debate on whether nodes and edges should be distinct or unified in schemas, reflecting varying approaches in different tools.
External File Handling and Asset Management: Challenges related to managing external files and assets across different tools discussed, emphasizing the need for robust asset handling and portability. For example, should we bundle external files into a single, flat file and base64 encode the attachments?
Action Items:
Refine Interop Demonstrations: Continue developing demonstrations between tools like Excalidraw and TLDraw to identify and resolve interop challenges.
Schema Development: Iterate on a least-common denominator extensible schema, attempting to satisfy the needs of the initial tools that are participating.
File and Asset Management: Investigate approaches for handling external files and assets, ensuring portability, flexibility and robustness over time.
Discussions
Some discussions started in the OCWG GitHub org:
The next meeting is currently scheduled for April 30th.