Closed icornelius closed 3 years ago
@icornelius Based on our e-mail discussion, we have decided that note
will be retained for its original purpose. @dbdennis and I also think there is no good reason to deprecate note
after all.
The Markdown payload will just be treated entirely as a new property, document
, and exclusively for writing purposes. document
should not be used in the YAML header, and note
is still fully supported. I see no reason not to support both as ZettelGeist can pretty much be expanded at will to include new fields.
If you agree with me, I think I'm going to mark this as closed, pending your follow-up. I actually could be talked into adding an optional quote
to the cite
block. But since we plan to retain note
, do you see this as a necessary addition?
@gkthiruvathukal I support this solution. If note
is retained I don't see quote
as a necessary addition. Thanks!
Thanks, @icornelius! I will close this out then.
I carry over a concern I raised in #18, regarding expansion of ZettelGeist from note-taking system to writing system. The problem is that, after the deprecation of
note
and migration of the contents of that field todocument
, there is not a field dedicated exclusively to language extracted from sources. The cordon sanitaire between my words and my source's words is compromised:I think @gkthiruvathukal is right to deprecate
note
in the new version of ZettelGeist, but I'd like to see a dedicated field for quoted language. Perhaps the field could even be a child ofcite
, like so:Users who, like me, have used the
note
field to record quoted language will then want to migrate the content of that field toquote
, notdocument
. This will free up the new markdowndocument
element for own writing.