aboutsummaryrefslogtreecommitdiff
path: root/_conclusion.qmd
diff options
context:
space:
mode:
Diffstat (limited to '_conclusion.qmd')
-rw-r--r--_conclusion.qmd24
1 files changed, 20 insertions, 4 deletions
diff --git a/_conclusion.qmd b/_conclusion.qmd
index 4dd8a8c..1ee0655 100644
--- a/_conclusion.qmd
+++ b/_conclusion.qmd
@@ -52,9 +52,20 @@ It has been established mainly for the next phases
that are expected to rely more heavily on newer libraries where possible
(see @sec-rdf).
-## Reflections on semantic annotations
+### Improved testing
-*TODO*
+The code as currently implemented
+does not allow for unit testing.
+It would be helpful to reorganize the codebase
+into smaller functions that each could be covered as units.
+
+The commonmark-spec project includes a large testsuite.
+It would certainly be useful
+to check the filter against that testsuite,
+to ensure no breakage of conventional Markdown markup.
+Useful here might be a draft work on rewritng the Semantic Markdown specification
+as an extension to the CommonMark specification
+[@Smedegaard2022cmark].
## Future works {#sec-future}
@@ -187,10 +198,15 @@ and also to explore possibilities of use with wrapper tools such as Quarto.
In other words,
try to prove the pessimistic usability analysis in @sec-pandoc-filter-versatile wrong.
-It might be helpful to try implement Semantic Markdown
+It might be helpful,
+both for authors in more widely enabling semantic text annotations
+and for testing the language design of the Semantic Markdown specification,
+to try implement Semantic Markdown
for other extensible Markdown parsers.
-Might also be fun to try implement Semantic djot
+Might also be fun to try implement Semantic Markdown as a patch for djot,
+a language derived from Markdown
+with the specific aim of being less ambiguous
[@MacFarlane2024djot].
### Nuanced citations in scholarly papers