Editor for teaching TEI - features
Revision as of 00:51, 9 July 2016 by Piotr Banski (talk | contribs) (jotting down the content of the TEI-L discussion with small additions)
This is an attempt at listing the minimal set of features that a TEI editor used for teaching purposes should have.
Contents
Basic required features
- multiplatform
- validation with Relax NG
- contextual suggestions (following the schema)
- XSLT 2 transformation
- easy to use
- free
- syntax highlighting (?)
Good-to-have but not mandatory
- xPath query
- Inline documentation (i.e. the little pop-ups with the definition of the element)
- pre-set templates (example?)
Features we can live without in a "teaching editor"
- No XSLT 3 (as a consequence of the fact that no commercial tool such as Saxon PE/EE could be used in such an editor)
- No need for XSLT or XQuery debuggers
- no need for database connectivity
- no need for a built-in SVN (etc.) client
- no need for a Tree Editor such as the one offered by oXygen
- no need for Compare Files/Directories tools
- no need for big-file editor or big-file support in general
- no need for syntax highlighting and editing support for some file types which are not XML-based (JavaScript, CSS, JSON, etc.).
Notes
The impetus for establishing the above came from a sub-thread on the TEI-L list bulleted by the following messages: [1], [2], [3]. The idea is to see whether the community can agree on a single feature set that a dumbed-down commercial editor can implement is a "student version" with an appropriate license. Or, as Martin Holmes puts it, we want to "arrive at something which would be utterly useless for the likes of me, and quite frustrating for serious users, but perfectly functional for teaching introductory XML encoding classes over a few months."