diff options
| -rw-r--r-- | _conclusion.qmd | 112 |
1 files changed, 55 insertions, 57 deletions
diff --git a/_conclusion.qmd b/_conclusion.qmd index d34481b..86cf163 100644 --- a/_conclusion.qmd +++ b/_conclusion.qmd @@ -1,76 +1,74 @@ -*TODO* +*TODO: summarize work, uses and weaknesses* ## Perspectives -The existence of a filter to simply silence semantic text annotations -is arguably helpful in breaking the chicken-and-egg problem -between authors finding it relevant to annotate their texts -and renderers to take annotations into account in their renderings. -What immediately follows, then, -is to address the other half of that problem: -Implement renderers that makes use of Markdown with embedded annotations. +This work is part of a series of works +to integrate semantic text annotations with creative textual interactions. +Concretely building upon this work are projects extending the same codebase +to support extracting or converting annotations. +Beyond these concrete projects, +the ability to author semantic text annotations and process them +allows for improvements in related workflows, +including interactive collaborative authoring +and streamlining of automated document layout. -Beyond both authoring and rendering of annotations, -several already emerging use cases may be aided by this work. +### This work as basis of others -### Further annotation processing {#sec-rdf} +Authors interested in authoring with semantic annotations +have been discouraged by the lack of tools supporting it +(beyond specific narrow scopes like hypermedia and citations). +Tools have been discouraged in implementing general-purpose support +for semantic annotations, probably by a perceived lack of demand for it. +This work can be seen as an initial solution to that chicken-and-egg problem; +further work is needed to evaluate +the usability of authoring as Markdown with this semantic extension, +and to assess whether there is an interest in this approach to authoring. -*FIXME: rewrite and reduce -to describe concrete future works -of extracting RDF and and rendering as RDFa and XMP.* +Parallel to that, +follow-up works are planned to extend this Pandoc-based setup +to support not only tolerate semantic annotations in source +but take them into account when parsing and rendering output documents. -1. Restore non-annotated Markdown structure - * strip annotations from Markdown structure -2. extract annotations as document-wide metadata - * extract annotations from Markdown structure - * structure semantic metadata as RDF triples - * Markdown output: save RDF triples serialized as turtle - in YAML document header - * PDF output: embed RDF triples serialized as XMP - in document-wide XMP -3. convert annotation to target-specific annotations - * read semantic metadata from Pandoc YAML document header - * structure semantic metadata as RDF triples - * Markdown output: preserve annotations, - and also save RDF triples serialized as turtle - in YAML document header - * HTML output: embed RDF triples serialized as RDFa - inline at text strings. - * PDF output: embed RDF triples serialized as XMP - inline at text strings. -See @fig-phases +### Parsing and rendering annotations {#sec-rdf} + +This work has been phase 1 of a larger set of projects, +all building on the same codebase, +illustrated in @fig-phases. {#fig-phases} -Some document containers support metadata -expressed in some serialization of the abstract language RDF, -e.g. as XMP metadata in PDF output -[@PDFAssociation2020 chapter 14.3] -and as RDFa in html output +Phase 2 will extend the Pandoc filter +to support extraction of annotations, +storing them as document-wide metadata in the Markdown YAML section. + +Phase 3 will extend the Pandoc filter further +to support translating annotations +when rendering as HTML or PDF. + +The annotation syntax for the current phase 1 of these project +was chosen in anticipation of phases 2 and 3, +as it aligns with established annotation formats +supported by the PDF and HTML document formats: +PDF documents support metadata and text-specific annotations stored as XMP +[@PDFAssociation2020 chapter 14.3, @Adobe2012, p. 9]; +HTML documents support text-specific annotations stored as RDFa [@Herman2015]. +Both XMP and RDFa are concrete formulations (serializations) +of Resource Description Framework (RDF), +an abstract language for expressing semantics. -RDF is an abstract data model for knowledge graphs, -usable for domain-specific annotations: -Terminology for a domain is established by referencing a shared ontology, -and terms are composed as sets of subject-predicate-object triples. -RDF includes one language, Turtle, strives to be human readable, -and languages for embedding triples into other data structures, -notably XMP for PDF files and RDFa for HTML. +Both phases 2 and 3 will involve a more intimate parsing of annotations, +to resolve their RDF statements +in the form of so-called subject-predicate-object triplets, +in order to rephrase (serialize) them +to better fit embedding in YAML, HTML and PDF, respectively. -RDF is an abstract data model for knowledge graphs. -Multiple RDF languages exist, -each covering all or subsets of the RDF model, -including human readability optimized Turtle, -RDFa for HTML embedding -and XMP for PDF embedding. -Each RDF language have different constraints, -e.g. the XMP language for storing RDF in media files -can express express one RDF graph in each XMP object -[@Adobe2012, p. 9]. +These extensions to the Pandoc-based workflow have uses in themselves, +and also enables further explorations into more complex workflows. ### Integration with Hypothesis -* filter extension to extend Pandoc/Quarto citations to cover [CiTO] +*TODO: filter extension to extend Pandoc/Quarto citations to cover [CiTO]* [CiTO]: <http://purl.org/spar/cito/2018-02-12> "CiTO, the Citation Typing Ontology" |