There’s still time to submit a long paper to ACM #DocEng25: share your document-related research and submit a paper by April 29!

Short papers and demos are due June 17.

(For all categories, abstracts are due a week before).

#DocEng2025 #DocEng #DocumentEngineering
https://mastodon.acm.org/@mxp/114182356855235680

The irony is that they conclude that 200 dpi are enough, and 300 dpi give you a good safety margin. They stress that higher resolutions waste storage space, communication network bandwidth for file transmission, and processing power.

But this didn't stop them from including a 3272 × 5500 pixel color PNG as what amounts to a thumbnail.

#DocumentEngineering

I’m looking at a paper that discusses the most suitable resolution for scanning documents. The 10-page PDF is almost 90 MB in size. Why? Because the authors did experiments with different resolutions… and the table that lists the characteristics at the various resolutions includes the *actual* scanned page at that resolution (shown at about 2 cm × 3 cm). ⇢

#DocumentEngineering

What’s especially interesting is that Don Chamberlin isn’t just some random IBMer (https://en.wikipedia.org/wiki/Donald_D._Chamberlin). And he wasn’t only involved with Quill SGML editor, but also with the Quilt XML query language, which heavily influenced XQuery (he was one of the editors of the W3C XQuery 1.0 recommendation).

#XMLPrague #REXX #SGML #HistoryOfComputing #DocumentEngineering

In my talk for the 2019 #XMLPrague paper “History and the Future of Markup” http://archive.xmlprague.cz/2019/files/xmlprague-2019-proceedings.pdf#page=335 I speculated about the use of #REXX as a language for #SGML tree manipulation.

Last night I “discovered” that REXX had indeed been used for this at IBM, and Goldfarb knew about it: namely in the experimental Quill editor running on an experimental windowing system on an experimental operating system on the IBM RT PC… (see, e.g., https://doi.org/10.1145/62506.62524)

#HistoryOfComputing #DocumentEngineering

Without even blinking, Greg Brockman during his GPT-4 demo, redefines the "document" as "arbitrarily interspersed images and text."

Byebye #DocumentEngineering

The call for papers for @ACM #DocEng23 (August 22–25 in Limerick, Ireland) is out:

http://doceng.org/doceng2023/cfp

❝The 23rd ACM Symposium on Document Engineering (DocEng’23) seeks original research papers that focus on the design, implementation, development, management, use and evaluation of advanced systems where document and document collections play a key role. DocEng emphasizes innovative approaches to document engineering technology, use of documents and document collections in real world applications, novel principles, tools and processes that improve our ability to create, manage, maintain, share, and productively use these. In particular, DocEng 2023 seeks contributions in the area of collaborative work with documents. Attendees at this international forum have interests that span all aspects of document engineering and applications.❞

#DocEng #DocumentEngineering

@mpe Awesome! Mandatory reading also for everyone in #documentEngineering!

It’s finally out now: @CerstinMahlow and my #DocEng2022 position paper on “Academic writing and publishing beyond documents.”

https://doi.org/10.1145/3558100.3563840

#DocumentEngineering #scholarlyPublishing

and of course there is an “r” missing in #DocumentEngineering

#Introduction

Golden Geek + interoperability maven. First line of code compiled then crashed the computer: May 1958

#CollaborativeSystems
#democracy
#DocumentEngineering
#GoldenGeek
#interoperability
#MathematicalLogic
#MiserProject
#nfoTools
#PersonalComputing
#photography
#SoftwareEngineering