OCWG Meeting № 8 Recap

[devhelpr]

Meeting № 8 Summary

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.

Meeting 8 Summary

Major Discussion Points

• Screen Sharing and Meeting Overview: The meeting begins with screen sharing and a review of the previous meeting, including discussions on schema extensions, asset handling, and Z ordering for 2D and 3D canvases.

• JSON Schema Definitions and Validations: The group discusses the need to formalize JSON examples into a JSON schema to facilitate validation and better interoperability across different tools and systems. It was noted that JSON Schema is well-supported across various programming environments.

• Asset Handling and MIME Types: The discussion includes the decision on file naming conventions, MIME types, and how these choices affect interoperability. The group considers using ".canvas.json" as a file extension and "application/json" as a MIME type to ensure compatibility.

• Potential Collaboration with Obsidian: There is a discussion on the potential overlap and collaboration with Obsidian, which already uses a .canvas file extension. The group suggests building trust and demonstrating success before formalizing this collaboration.

• Bringing in External Experts: The idea of involving external experts, such as Brooklyn Zelenka, to provide insights on spec building and validation is discussed. The group agrees that expert feedback would be valuable before locking down the specifications.

• Extension System for JSON-Based Formats: There is a detailed discussion about creating an extension mechanism similar to GLTF to enhance interoperability and extend functionality within Open Canvas. This includes how extensions could handle various aspects like schema extensions and additional functionalities.

• Use of Resources in Canvas Specifications: The concept of separating data into resources or assets and referencing them within the canvas is explored, using GLTF as a model. This approach would allow multiple instances of the same item across different locations within a canvas.

• Examples of Extensions: The group discusses potential examples of extensions, such as adding audio functionality or enhancing visual representations, and how these could be managed within the schema.

• Importance of Validation Tools: The group emphasizes the need for a validator tool similar to the GLTF validator, which would allow for testing and validating Open Canvas files, ensuring conformance to the agreed-upon standards.

Action Items

• Create a JSON Schema: Formalize the current JSON examples into a JSON schema to validate exports and facilitate further discussions.

• Determine File Naming Conventions and MIME Types: Decide on the file extension and MIME type for Open Canvas files, with a leaning towards ".canvas.json" and "application/json".

• Setup a Pull Request: Prepare a basic starting point for JSON schema on the spec repository and iterate on it.

• Coordinate with External Experts: Reach out to Brooklyn Zelenka or other experts to get feedback and insights on the current spec building process.

• Develop a Validator Tool: Work on creating a validator tool similar to the GLTF validator for testing and validation of Open Canvas files.

Takeaways

• JSON Schema provides a robust foundation for validation and can be supported across multiple programming languages, making it a versatile choice for Open Canvas.

• Establishing clear file naming conventions and MIME types is crucial for ensuring compatibility and ease of use across different platforms and tools.

• Collaboration with tools like Obsidian could enhance the utility and adoption of Open Canvas but requires establishing trust and demonstrating value.

• Bringing in external experts can provide valuable feedback and ensure that the specifications are robust and well-considered before finalizing them.

• A well-defined extension system will be key to extending Open Canvas functionality and maintaining interoperability across various platforms and applications.

The next meeting is scheduled for Sep 5, 2024 @ 12:00 ET.