Purpose
Registration description: Creating a ProofReading Markup Language, since I haven't found anything quite suited to the purpose out there on the 'Net, using XML DTDs and/or schema, and/or XHTML 1.1 modules, and at least a Perl/GTK reference implementation, with hopefully a PHP/SQL interface to follow. This Markup Language would strive to accurately convey any possible imperfections in a printed work (possibly expanded later to include online HTML and such, if there's a demand for it) in a way that makes it clear to printsetters exactly what needs to be fixed, and why.
The initial reference implementation, tentatively named "Proximal" at this point (since changed to "Perameles"), will be a Perl/GTK program, able to run on typical Linux/*BSD (perhaps Mac OSX?) machines without needing extra libraries or packages. (That's changed since Fedora, at least, no longer includes Gtk-Perl by default.) It should be able to read a local *.prml file, a http://example.com/sample.prml file over a network, or use a MySQL database which stores author, volume, division, page, and line info. It should then display either the version as seen on the printed page, the corrected version of that same region, or both side by side (or, the original version with a semblance of traditional proofreaders' marks (ISO 5776:1983) superimposed). It should allow the file to be edited to add or remove markup, indicating errors found or already corrected, and save the information back to a local file or the MySQL database.
At a later stage, I would like to develop a PHP interface which would work with a MySQL database compatible with the "Proximal" SQL, allowing either a read-only view of the errors and correction, or updating the database information, and saving the information as a *.prml file on the client machine, depending on user permissions. An even further-off goal might be a front end to the database and/or local files based on Mozilla's Gecko Rendering engine, but that's still so vague I can't do much to describe it yet. Ideally, though, this would allow Windows users to have a native interface directly to the information, without going through a PHP middle-end and a web browser.
The intended audience would be developers for the XML DTD/XSD, and end users in the publishing business when a satisfactory interface takes shape.
Project Gutenberg's Distributed Proofreaders project doesn't seem to have what I'm looking for, since it's oriented more towards correcting optical scanning mistakes, and less towards fixing errors in the original.
