Comments (1)
If interoperability is the main goal than CommonMark would be the best choice. As JSON Canvas is created by Obsidian, I guess the Markdown dialect is Obsidian Flavored Markdown . In theory this requires applications to recreate parts of Obsidian. Furthermore Obsidian Markdown seems to be extensible via plugins so perfectly processing arbitrary Canvas files from Obsidian seems to be impossible. In practice I bet each application will use its own preferred Markdown variant so there will be a mess as soon as you use non-trivial Markdown elements. Possible solutions:
- Agree on one Markdown dialect (this won't happen)
- Pray and guess when processing markdown
- Add a field to denote the markdown variant(s) used in a JSON Canvas file (e.g CommonMark or Obsidian + Citation-plugin) so the content can be processed e.g. with remark
I think solution 3 is most feasible to get 99% interoperability but only 1 would give 100% and in the end we will have 2 anyway as Markdown is not interoperable and people don't strictly follow standards (disclaimer: I'm a big fan of both Markdown, standards, and interoperability).
P.S: The JSON Canvas homepage seems to use it's own Markdown subset as well.
from jsoncanvas.
Related Issues (20)
- Create JSON Schema to further define and constrain the spec. HOT 7
- List of implementations HOT 2
- question: Are the preset color values part of the spec? HOT 1
- Custom node types or additional metadata? HOT 2
- BGL and jsoncanvas HOT 2
- node width and height should be optional HOT 11
- group types nodes are containing types but don't specify dimensions HOT 4
- are file nodes always local relative paths? HOT 2
- spec: Add an optional $schema property at top level HOT 3
- Properly reference standards JSON Canvas is based on
- Proposal: Edges additional properties HOT 3
- Proposal: Edge offset property
- What is the purpose of the numerical color values? HOT 6
- Proposal: canvasz — a zipped canvas file, which packages a the markdown files along with it HOT 2
- Doc: add link to sourcecode HOT 1
- Need for clarification: toEnd & fromEnd HOT 1
- Canvas Spec should include version for migrations purposes. HOT 1
- Diagram Types HOT 2
- Version property
- Define coordinate system HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jsoncanvas.