Balisage series on markup technologies最新文献

{"title":"The Impossible Task of Comparing CALS Tables","authors":"R.F. La Fontaine, J. Francis","doi":"10.4242/balisagevol27.lafontaine01","DOIUrl":"https://doi.org/10.4242/balisagevol27.lafontaine01","url":null,"abstract":"Finding out what has changed in a CALS table is remarkably complicated. Some variant of the CALS standard is often used to represent tabular data in XML, but it permits considerable flexibility in the form of headers, footers, and spans. Additional complexity arises when authors use empty columns for layout or use column or row spans specified in unusual ways, or when applications simply do not follow the standard. In practice, comparing CALS tables directly is impossible. But maybe that is OK if all we need is a clear representation of the changes. And if we can represent them in a CALS table!","PeriodicalId":89326,"journal":{"name":"Balisage series on markup technologies","volume":"59 1","pages":""},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"70946098","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":"Unveiling Linguistic Harmony: Asserting Interlingual Synchronicity in Documents","authors":"G. Bormans, Srikanth Venkata Subramanian","doi":"10.4242/balisagevol28.bormans01","DOIUrl":"https://doi.org/10.4242/balisagevol28.bormans01","url":null,"abstract":"Publishing texts in multiple languages always involves issues of coordination of both content and structure. The Swiss Chancellery must deal with documents in four official languages, and they face special problems in the production of compilations that merge amendments into existing legislation. Although the source documents are prepared in MS Word, they are issued in derivative products such as PDF, HTML, and Akoma Ntoso. To aid coordination between versions, the authors are developing a reporting system that does rule-driven sanity checks on parallel documents, starting with the XML of Akoma Ntoso. Each rule is represented by XSLT processes, and the selection of rules to be applied is controlled by XProc, with the results displayed as messages interpolated into an HTML rendition of the source document.","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":"70947106","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":"Serializing the Locator Format of the United States Government Publishing Office as XML","authors":"Joel Kalvesmaki","doi":"10.4242/balisagevol28.kalvesmaki01","DOIUrl":"https://doi.org/10.4242/balisagevol28.kalvesmaki01","url":null,"abstract":"The Government Publishing Office makes significant use of so-called locators, a specialized file format for commercial typography. In this article, I explain the origins of the locator format, discuss its architecture, and single out some of the challenges inherent in understanding and converting the format. I present Slax, Serializing Locators as XML, an expression of the locator format in XML and an application that makes the conversion. In telling the story of the locator format, which is poorly documented, I argue that it developed slowly over time as user expectations changed, and in tandem with its primary processor, MicroComp. Slax also provides an excellent example of where XSLT is an ideal technology for document conversion, and where it is not, and provides a model for the symbiotic use of declarative and imperative programming models.","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":"70947454","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":"Adventures in Correcting XML Collation Problems with Python and XSLT","authors":"E. Beshero-Bondar","doi":"10.4242/balisagevol27.beshero-bondar01","DOIUrl":"https://doi.org/10.4242/balisagevol27.beshero-bondar01","url":null,"abstract":"The process of instructing a computer to compare texts, known as computer-aided collation, might resemble trying to fix a power loom when the threads it is supposed to weave together become tangled. The power of the automated weaving continues, with the threads improperly aligned and the pattern broken in a way that can make it difficult to isolate the cause of the problem. Automating a tedious process magnifies the complexity of error-correction, sometimes calling for new tooling to help us perfect the weaving or collating process. The authors are attempting to refine a collation algorithm to improve its alignment of variant passages in the Frankenstein Variorum project. We have begun with a Python script that tokenizes and normalizes the texts of the editions and delivers them to collateX for processing the collation and delivering TEI-conformant output for our project. In post-processing stages after running the collation, we apply a series of XSLT transformations to the collation output. This post-collation XSLT pipeline publishes the digital variorum edition, which prepares each output witness in TEI XML to store information about its own variance from the other editions. We have discussed that pipeline elsewhere, but our interest in this paper is in efforts to repair and correct and improve the collation process. We have applied Schematron and XSLT in post-processing to correct patterns of erroneous alignments, but eventually realized that the problems we were trying to solve required repairing the collation algorithm. We are now experimenting with revising the collation algorithm in two ways: 1) by fine-tuning the text preparation algorithms we apply in our Python file that delivers text to the collateX software, and 2) by attempting to introduce those same text preparation algorithms entirely with XSLT using the Text Alignment Network's XSLT application of tan:diff() and tan:collate(), introduced by Joel Kalvesmaki at the 2021 Balisage conference. In this paper we discuss the challenges of figuring out where and how to intervene in the collation process, and what we are learning about how far we can take XSLT and Schematron in helping to automate the preparation, collation, and correction process.","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":"70946173","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":"Constructive Inconsistency","authors":"C. M. Sperberg-McQueen","doi":"10.4242/balisagevol27.sperberg-mcqueen02","DOIUrl":"https://doi.org/10.4242/balisagevol27.sperberg-mcqueen02","url":null,"abstract":"A foolish consistency, said Emerson, is the hobgoblin of little minds. But how can we know when consistency is foolish and when it is wise?","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":"70946503","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":"Serverless Searching with XSLT and JavaScript","authors":"Joseph Takeda, Martin Holmes","doi":"10.4242/balisagevol27.takeda01","DOIUrl":"https://doi.org/10.4242/balisagevol27.takeda01","url":null,"abstract":"Increasing awareness of the burdens of technical debt and the risks and costs associated with complex server infrastructures have prompted digital humanists to consider moving to purely static HTML/CSS/JS websites for projects such as online digital editions. Building static sites is not difficult, but digital editions also require sophisticated search capabilities, incorporating text search with stemming and wildcards as well as a rich array of filters tuned to the contents of the edition itself. Responding to this need, we created staticSearch, a system which builds search indexes offline with XSLT and queries them statically using JavaScript, providing a straightforward approach to search for purely static websites. This presentation will describe how staticSearch works, and discuss some of the interesting and challenging problems that such a system has to overcome.","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":"70946633","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":"Processing Lax XML Element Trees","authors":"Phil Fearon, Gursheen Kaur","doi":"10.4242/balisagevol28.fearon01","DOIUrl":"https://doi.org/10.4242/balisagevol28.fearon01","url":null,"abstract":"When processing HTML tables within XML documents, we generally find the lax element schema for the HTML table specification increases the complexity of the processing system. By first transforming HTML tables to a normalized representation we avoid the need for different logic paths deep inside our code. Ensuring there is a single normalized element hierarchy for any given table also simplifies the task of comparing different versions of each table. This paper describes the design and implementation of XSLT that transforms lax HTML table element structures within an XML document to conform to a strict content model.","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":"70946797","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":"Invisible XML coming into focus","authors":"Tom Hillman, J. Lumley, S. Pemberton, C. M. Sperberg-McQueen, Bethan Tovey-Walsh, Norm Tovey-Walsh","doi":"10.4242/balisagevol27.eccl01","DOIUrl":"https://doi.org/10.4242/balisagevol27.eccl01","url":null,"abstract":"Invisible XML has had a long incubation process, but in the last year things have heated up. A W3C Community Group has been formed, the spec has been improved, and implementations have been released or are in various stages of development. This paper gives an overview of iXML in its stable version 1.0 form, with discussion of some of the design decisions that have shaped it, and accounts from implementors of their practical experiences with iXML.","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":"70945841","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":"Getting Useful XML out of Microsoft Excel","authors":"Gayanthika Udeshani","doi":"10.4242/balisagevol27.udeshani01","DOIUrl":"https://doi.org/10.4242/balisagevol27.udeshani01","url":null,"abstract":"This paper presents a solution that transforms a Microsoft Excel Open XML Spreadsheet (XLSX) file into a shallow-structured XML file used at Typefi, called Content XML (CXML), using XSLT and XProc. This solution has three main research areas: The XProc pipeline to read the Excel file content. Transform Excel tables to a CALS table using XSLT functions. Transform Excel charts and embedded images. Significant information is read from the chart.xml and converted to a Scalable Vector Graphics (SVG) file, and then referenced as an image in the output XML. The XLSX file can contain various elements such as tables, charts, and graphics. This solution does not yet use all the features available within the Excel XML but is a work in progress and future improvements will be guided by customer requests.","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":"70946320","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":"Accumulators in XSLT and XSpec","authors":"A. Galtman","doi":"10.4242/balisagevol28.galtman01","DOIUrl":"https://doi.org/10.4242/balisagevol28.galtman01","url":null,"abstract":"Accumulators in XSLT 3, while not necessarily an everyday staple of XSLT code bases, can provide elegant solutions to certain challenges in both streaming and non-streaming XSLT applications. The debugging and testing techniques you might use for accumulators are a little different from techniques you use for templates and functions. After briefly reviewing what makes accumulators special and powerful, this paper describes and compares several debugging and testing techniques for accumulators. Whether you need a near-term bug diagnosis or an automated XSpec test for long-term code health, you'll learn ways to access, understand, and maintain your accumulator's behavior.","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":"70946848","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}