From 85e5c51dab5877362afc3203b84dc56a4e6cf2c8 Mon Sep 17 00:00:00 2001 From: Jonas Smedegaard Date: Sat, 24 May 2025 11:14:08 +0200 Subject: add TODOs for problem formulation --- _intro.qmd | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/_intro.qmd b/_intro.qmd index 5e4e4be..c39a6cd 100644 --- a/_intro.qmd +++ b/_intro.qmd @@ -55,13 +55,19 @@ So, * What are the core qualities of Markdown, and how can a Markdown dialect express semantic text annotations while maintaining those qualities? -* How do Pandoc convert Markdown to HTML or PDF, - and how can this workflow be extended +* *TODO: Analysis of spec, phrased as a question* +* How do Pandoc parse Markdown into a generalised content structure, + and how can that process be extended to handle semantic text annotations? * Which approach to extending Pandoc is more likely long-term sustainable? * How can the reliability of a Pandoc extension be evaluated? +*TODO: Maybe reframe as investigation of the spec, +implementing it to identify its strengths and weaknesses* + +*FIXME: align above questions with actual findings* + ## Project constraints Driven by an interest in sustained development of this research project -- cgit v1.2.3