Markup UK 2025 Proceedings

Content
Search Results
Loading, please wait ...

Loading

  • Modular ixml
    • Contents
    • Introduction
    • Requirements
    • Naming and renaming
    • The Structure of a Module
    • Semantics
    • Processing
    • Example
    • Example
    • Example
    • A Larger Example
    • Other Possible Approaches
    • Conclusion
    • References
  • From iXML to XSpec
    • Introduction
      • What is iXML?
      • Why iXML?
    • Learning iXML
    • Testing an iXML grammar
      • Eyeballing the output
      • Schema validation
      • Diff
      • XSpec
        • Using XSpec to test XSLT
        • Using XSpec to test iXML
      • What testing revealed
    • Automation
    • Conclusion
    • Bibliography
  • XForms Extended
    • Introduction
    • The problem
      • Issue #1: Cumbersome layouts
      • Issue #2: Complex logic
      • Issue #3: The need for advanced JavaScript code
    • The proposed solution:
      • XForms code
      • JavaScript and CSS code
      • Extended XForms Components
    • Weaknesses and Limitations
    • What's next
    • Bibliography
  • Processing JSON with Template Rules
    • Introduction
    • Selecting the case study
    • Converting the input XML to JSON
    • Serializing the parse tree
    • Generating the digest file
    • Refining the digest
    • Conclusions
    • Bibliography
  • Schema Test Suite
    • Introduction
      • Structural Validation vs. Schematron
      • Schema Languages
    • Schema Test Suite
      • Unit Testing Methodology
      • Test Cases
        • Folder Directory Hierarchy
        • Templates
        • Passing XML
        • Failing XML
      • Implementation and Execution
        • Tools and Libraries
        • Execution Logic
        • Reporting
    • Conclusion
      • Continuous Development
      • Integration
      • Accessibility
    • Bibliography
  • Design and Performance of a Corpus Scanner
    • Introduction
    • Tool Requirements and Features
      • Easy to configure and run
      • Convenient to provide inputs
      • Produce multiple forms of report
      • Combine multiple runs into a single report
      • Robust against parse errors
      • Extensible and Maintainable
    • Implementation
    • Memory Usage and Speed
    • Parsing Errors
    • Extensibility
    • Future Work
    • Conclusion
  • Surfing the web with XProc
    • Introduction
    • Enter Selenium
    • Enter Invisible XML
    • cx:selenium
    • Security implications
    • Next steps
  • PrintCSS Meets LaTeX
    • Introduction
    • The Status Quo: Configuring Layouts in xerif
    • PrintCSS and TeX
    • Building a PrintCSS renderer
      • Preliminary Considerations
      • Parsing PrintCSS
      • Generating an xml2tex Configuration
    • Summary, Discussion and Future Work
    • Appendix I: Supported PrintCSS Features
    • Appendix II: Supported Standard CSS Features
  • Adding new Cars to a Running Train
    • What is JATS?
    • Requirements and Constraints
      • How Multi-language Documents are Presented and Stored
      • Requirements and Non-Requirements
        • Backwards Compatibility
        • The Needs of the Few Must Not Burden the Many
        • JATS Should Stay In It's Lane
    • I Don't Use JATS; Why Should I Care?
    • JATS Multi-language Mechanism (@lang-group)
      • Influence of SGML's “Architectural Forms”: Giving Credit where Credit is Due
    • A Few Examples
      • Simple Example of a Language Group
      • Did a Person or an Algorithm Translate This?
      • Not Everything Should be Translated
    • Doesn't This Mechanism Entail a Lot of Overhead?
    • Documentation for All This
    • Acknowledgements
    • Bibliography

Copyright © 2025 Norm Tovey-Walsh