You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As best I can tell, MultiMarkdown uses a subset of YAML for metadata headers. There's this guide section on the topic, but it's from MultiMarkdown 4, not MultiMarkdown 6.
The Markdown-based notes editor Joplin is currently in the process of working on YAML compatibility. Could you perhaps pop in and give your thoughts on interoperability with MultiMardown? (YAML aside, it would be nice to have some guidance on packaging multiple markdown files with attachments.)
Something I mentioned in the Joplin issue comment thread is the possibility of using Schema.org for metadata formatting. In the case of Joplin, this would most likely default to NoteDigitalDocument, but MultiMarkdown presumably supports a wider range of use cases. While the metadata fields supported by Schema.org are... quite numerous, MultiMarkdown and/or Joplin could choose their supported fields from the Schema.org list and define behavior for losslessly handling valid metadata fields that aren't supported by a particular client.
I guess, in summary:
Can you coordinate with Joplin to some extent so that Joplin's exports can be agreeable with MultiMarkdown and vice versa?
Can you provide perspective and guidance on packaging?
Can you consider using Schema.org for defining standardized metadata fields? And,
Can you update the MultiMarkdown guide for version 6 to define the current practices with regard to metadata headers?
Thanks!
The text was updated successfully, but these errors were encountered:
At this time I am not interested in modifying MultiMarkdown's metadata approach, nor does it require any sort of standardization. MultiMarkdown's metadata is designed to be flexible and support many different use cases. It's up to the user to decide whether to standardize on certain metadata keys.
As for interoperability, I believe the MultiMarkdown metadata syntax is fairly well documented, and there are a few test cases in the test suite.
I am happy to answer any specific questions that are sent my way.
As best I can tell, MultiMarkdown uses a subset of YAML for metadata headers. There's this guide section on the topic, but it's from MultiMarkdown 4, not MultiMarkdown 6.
The Markdown-based notes editor Joplin is currently in the process of working on YAML compatibility. Could you perhaps pop in and give your thoughts on interoperability with MultiMardown? (YAML aside, it would be nice to have some guidance on packaging multiple markdown files with attachments.)
Something I mentioned in the Joplin issue comment thread is the possibility of using Schema.org for metadata formatting. In the case of Joplin, this would most likely default to
NoteDigitalDocument
, but MultiMarkdown presumably supports a wider range of use cases. While the metadata fields supported by Schema.org are... quite numerous, MultiMarkdown and/or Joplin could choose their supported fields from the Schema.org list and define behavior for losslessly handling valid metadata fields that aren't supported by a particular client.I guess, in summary:
Thanks!
The text was updated successfully, but these errors were encountered: