You hit the nail right on the head. We do indeed need
"a simple interface in which the casual reader spots a mis-transcription
of mis-classification and is willing to fix it."
That's the best one line description of this goal that I've ever read. How
do we get from that "here" to the "there" of defining what it would take
to build it and where to find the resources for doing it?
Professor emeritus of English and Classics
On 2/22/15 12:55 PM, "Sebastian Rahtz" <[log in to unmask]> wrote:
>Ah, maybe you are not over-problematizing, but prematurely-optimizing.
>rightly, a simple interface in which the casual reader spots a
>mis-classification and is willing to fix it. But youıre then jumping to
>saying we need
>a specific re-phrasing of the XML source, and quoting markup, and getting
>You can describe what the system does and what the user-interface is
>worry at this point about how the software works, and what it does under
>Thatıs a technical discussion later which neither you nor I really need
>Chief Data Architect
>University of Oxford IT Services
>13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431