{"title":"The Dream of a CMS","authors":"A. Nordström","doi":"10.4242/balisagevol28.nordstrom01","DOIUrl":"https://doi.org/10.4242/balisagevol28.nordstrom01","url":null,"abstract":"An XML-first content management system — XML technologies handling XML content in an XML database — has been the author's dream for the last decade and a half, ever since he first found a way to break free from the shackles of non-XML technologies limiting what he could do. A portal for an automotive client provided both an interesting, and XML-centric, case study using quite a few “X” technologies, but just as importantly a way forward to finally implementing that system.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"18 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70947264","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Project Mirabel: XQuery-Based Documentation Reporting and Exploration System","authors":"E. Kimber","doi":"10.4242/balisagevol27.kimber01","DOIUrl":"https://doi.org/10.4242/balisagevol27.kimber01","url":null,"abstract":"Project Mirabel is a multi-function XQuery-based system for capturing and reporting on the results of applying Schematron validation to DITA documents. Mirabel has experienced a very 'organic' development, growing (all within the span of three weeks!) from a simple reporting utility into a multi-function platform for general reporting and exploration over large and complex sets of DITA content that represent non-trivial hyperdocuments. Whew!","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70946055","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Customisation of Akoma Ntoso using Schematron","authors":"G. Bormans","doi":"10.4242/balisagevol27.bormans01","DOIUrl":"https://doi.org/10.4242/balisagevol27.bormans01","url":null,"abstract":"Akoma Ntoso, an Oasis Open standard for legal documents, is gaining popularity. Since the standard aims to cover a wide variety of legislative and parliamentary traditions, it is fairly broad and generic. Projects usualy start by customisation of the standard to a local tradition. Such a customisation is usualy achieved by generating a so called subschema through publicaly available tooling. This presentation shows an alternative approach for some common use cases using Schematron instead.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70945795","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Keyboarding Frege's concept writing","authors":"C. M. Sperberg-McQueen","doi":"10.4242/balisagevol28.sperberg-mcqueen01","DOIUrl":"https://doi.org/10.4242/balisagevol28.sperberg-mcqueen01","url":null,"abstract":"Gottlob Frege’s 1879 book Begriffsschrift (Concept Writing) poses a number of problems for the would-be digitizer, most notably its extensive use of a two-dimensional notation not easily reduced to a linear sequence of characters. With careful study, however, the notation can be seen to possess a clear internal logic, and an easily keyboardable serialized form for data capture can be designed, which makes it easy to transcribe even complex formulas. Invisible XML supports the key step of parsing that data capture format and turning it into usefully structured XML, from which routine stylesheets can generate SVG images of the two-dimensional formulae and other useful outputs.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70947549","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Biblical Scholarship in the GitHub Jungle","authors":"J. Robie","doi":"10.4242/balisagevol27.robie01","DOIUrl":"https://doi.org/10.4242/balisagevol27.robie01","url":null,"abstract":"Clear Bible's MACULA project is a major data integration challenge. Clear creates freely licensed linguistic datasets for the entire Bible in the original Hebrew, Aramaic, and Greek languages. We integrate these datasets with high quality datasets created by others and align them with translations in many languages. Language is complex and individuals have different ways of organizing and understanding texts, so integrating these diverse datasets is not straightforward. Few texts have been analyzed as thoroughly as the Bible, from many different perspectives. A great deal of Biblical analysis is available on GitHub under open licenses, including well-established reference systems for the verses in a Bible and the words used in the original languages. But data integration is still problematic since there are different traditions, with different sets of books and different ways of dividing up individual books. For instance, Psalm 23 in a Protestant Bible is called Psalm 22 in a traditional Catholic Bible. Even a concept as simple as \"what is a word\" becomes complicated, since there is no clear universal distinction between a word and a morpheme — linguists employ a range of different criteria, which are not uniformly applicable across contexts and languages. In this article, we would like to illustrate some of the challenges we have encountered in the first year of our work on MACULA. We will also discuss the approach we have taken in response to each of these challenges.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70946447","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Paula Prescod, Ben Feuer, Andrii Hladkyi, Sean Paulk, Arjun Prasad
{"title":"Auto-Markup BenchMark: Towards an Industry-standard Benchmark for Evaluating Automatic Document Markup","authors":"Paula Prescod, Ben Feuer, Andrii Hladkyi, Sean Paulk, Arjun Prasad","doi":"10.4242/balisagevol28.prescod01","DOIUrl":"https://doi.org/10.4242/balisagevol28.prescod01","url":null,"abstract":"Recent large language models (LLMs) such as GPT, Bard and Claude have achieved impressive progress in comprehending and generating human language. We explore the potential for LLMs to automate markup of semi-structured texts into HTML, DITA, and other related languages. Automated markup could make it possible to move documents into XML at much lower cost. Currently, there is no standard benchmark for evaluating automatic markup systems. Establishing a benchmark for the understanding and generation of structured documents and markup languages can drive innovation, standardize evaluations, identify algorithm strengths and weaknesses, clarify the State of the Art and foster interdisciplinary collaborations. This paper introduces an early version of a benchmark for this purpose.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70947420","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"BITS for Government Information?","authors":"Ravit H. David","doi":"10.4242/balisagevol27.david01","DOIUrl":"https://doi.org/10.4242/balisagevol27.david01","url":null,"abstract":"Scholars Portal, a service of the Ontario Council of University Libraries, provides multiple levels of access and preservation to scholarly packages of Ebooks. We have created an in-house custom modification of the Book Interchange Tag Suite (BITS, a sister vocabulary to the Journal Article Tag Suite, JATS) to describe EBooks. A recent strategic decision to host government information has posed several challenges with our BITS modification and required a new in-house schema to accommodate specific metadata requirements posed by the somehow different nature of govinfo content. We’ll look at some of these challenges, then examine ways BITS can accommodate metadata that isn’t necessarily standard Ebook metadata.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70945808","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Pulling All Production Processes Together with an XML-First System","authors":"M. Gross, C. O'Connor","doi":"10.4242/balisagevol28.gross01","DOIUrl":"https://doi.org/10.4242/balisagevol28.gross01","url":null,"abstract":"Creating a seamless centralized workflow that starts with XMLhas long been the siren song of scholarly journal production workflows. Yet the definition of “start” is the critical piece in this publishing puzzle. For Aries Systems Corporation, innovating article production truly means starting with XML as soon as a manuscript is accepted after peer review. But how do you create a system for auto XML text conversion for Word files when you cannot control the creation of the Word file, nor force authors to follow any predefined template or complex instructions? Given all the ways that authors can use (and abuse!) the wide range of MS Word features, no automated system can produce good XML from 100% of author-supplied files. But Aries could not expect the users of Editorial Manager and ProduXion Manager to be detectives or tinkerers, figuring out what in a problem Word file needs to be fixed to get a good result, rerunning the file, QC’ing the result, maybe having to go back in and fix something else, rerunning the file, QC’ing the result. Editors and authors need to have confidence that when they submit a Word file for processing they will get a good XML file out every time.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70946952","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The SGML/XML Approach to Document Processing: [an incomplete] History of Criticisms and Challenges","authors":"Allen H. Renear","doi":"10.4242/balisagevol28.renear01","DOIUrl":"https://doi.org/10.4242/balisagevol28.renear01","url":null,"abstract":"Like all SGML/XML enthusiasts I have spent considerable energy responding to objections to the SGML/XML approach to document processing. In this talk I list some objections to that approach that have been posed by authors, scholars, designers, philosophers, clients, programmers, web designers, and computer scientists, and indicate how I (and others) have responded — that includes responses that in the interest of sustaining friendships or job security were never quite articulated. I look forward to your additions in the discussion.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70947479","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Ambiguity in iXML","authors":"Norm Tovey-Walsh","doi":"10.4242/balisagevol28.tovey-walsh01","DOIUrl":"https://doi.org/10.4242/balisagevol28.tovey-walsh01","url":null,"abstract":"Humans are really good at resolving ambiguities. Our senses are trained for it: is that pattern of shadows in the forest dappled sunlight, or a tiger waiting to pounce? Our minds quickly and almost effortlessly adjust interpretations based on contextual clues that change over time. Parsers? Not so much. Our everyday languages and formats: XML, JSON, JavaScript, Java, etc. are rigorously defined to avoid ambiguity: you must put a quote here, a semicolon there. (Most) parsers reject anything that cannot be unambiguously identified within a small textual window. Invisible XML is an uncommon format in that it doesn’t reject grammars or parses that are ambiguous. That doesn’t mean ambiguity is a good thing, and it doesn’t mean authors wouldn’t like to control it.","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"1 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70947622","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}