Editor for teaching TEI - features - Revision history

Piotr Banski: frankly, this seems to me the only point that might require a reaction after the most recent message

2016-07-12T22:27:36Z

frankly, this seems to me the only point that might require a reaction after the most recent message

← Older revision		Revision as of 22:27, 12 July 2016
Line 9:		Line 9:
	<br>1.4. contextual suggestions (following the schema)		<br>1.4. contextual suggestions (following the schema)
	<br>1.5. XSLT 2 transformation (Saxon HE? that would offer XQuery as well)		<br>1.5. XSLT 2 transformation (Saxon HE? that would offer XQuery as well)
	<br>1.6. easy to use		<br>1.6. easy to use (think as opposed to Emacs, and think DH students)
	<br>1.7. free for students (as in beer)		<br>1.7. free for students (as in beer)
	<br>1.8. syntax highlighting for XML (that naturally includes XSLT)		<br>1.8. syntax highlighting for XML (that naturally includes XSLT)

Piotr Banski: + question

2016-07-12T08:53:48Z

+ question

← Older revision		Revision as of 08:53, 12 July 2016
Line 25:		Line 25:
	* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?		* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?
	* I've added Oxygen project files, or an equivalent system in a competing editor (Martin Holmes).		* I've added Oxygen project files, or an equivalent system in a competing editor (Martin Holmes).
			** Could we just say "project files", which in the context of oXygen will be interpreted as "oXygen project files", and elsewhere as an equivalent system? [[User:Piotr Banski\|Piotr]]
	* Another essential feature for me would be the ability to script a sequence of transformations etc. in the way that oXygen currently does when generating RNG and XHTML from an ODD file. It's currently done with an Ant script, but any scripting language will do. I routinely do an exercise which involves editing an ODD, generating a schema, using it to create a new file, et da capo. This is easy and seamless in oXyGen: doing it via the oXGarage web interface would be cumbersome and confusing. (Lou)		* Another essential feature for me would be the ability to script a sequence of transformations etc. in the way that oXygen currently does when generating RNG and XHTML from an ODD file. It's currently done with an Ant script, but any scripting language will do. I routinely do an exercise which involves editing an ODD, generating a schema, using it to create a new file, et da capo. This is easy and seamless in oXyGen: doing it via the oXGarage web interface would be cumbersome and confusing. (Lou)

Piotr Banski: minor housekeeping notes

2016-07-12T08:49:12Z

minor housekeeping notes

← Older revision		Revision as of 08:49, 12 July 2016
Line 22:		Line 22:
	** very true Piotr! Whatever the interface, I agree with Lou that it's an important feature.		** very true Piotr! Whatever the interface, I agree with Lou that it's an important feature.
	* 2.5: "From a sustainability perspective, I would add "open-source" to the feature set, maybe in the "2. Ideally..." section. This may not be much pertinent from the short term opportunistic point of view of a student (or a teacher), but may help consolidate tools appropriateness to TEI for the long term, which is what TEI is all about." (Serge Heiden)		* 2.5: "From a sustainability perspective, I would add "open-source" to the feature set, maybe in the "2. Ideally..." section. This may not be much pertinent from the short term opportunistic point of view of a student (or a teacher), but may help consolidate tools appropriateness to TEI for the long term, which is what TEI is all about." (Serge Heiden)
	* I have moved XPath queries from "Ideally" to "Basic features". In my experience, that's an essential point for students (and people in general). (Marjorie) I've constrained this to XPath 2.0; I think this would be sufficient. (Martin Holmes)		* [http://wiki.tei-c.org/index.php?title=Editor_for_teaching_TEI_-_features&action=historysubmit&diff=15031&oldid=15026 I have moved XPath queries] from "Ideally" to "Basic features". In my experience, that's an essential point for students (and people in general). (Marjorie) I've constrained this to XPath 2.0; I think this would be sufficient. (Martin Holmes)
	* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?		* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?
	* I've added Oxygen project files, or an equivalent system in a competing editor (Martin Holmes).		* I've added Oxygen project files, or an equivalent system in a competing editor (Martin Holmes).

Lou: /* Comments, justification, discussion */

2016-07-11T14:02:40Z

Comments, justification, discussion

← Older revision		Revision as of 14:02, 11 July 2016
Line 25:		Line 25:
	* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?		* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?
	* I've added Oxygen project files, or an equivalent system in a competing editor (Martin Holmes).		* I've added Oxygen project files, or an equivalent system in a competing editor (Martin Holmes).
			* Another essential feature for me would be the ability to script a sequence of transformations etc. in the way that oXygen currently does when generating RNG and XHTML from an ODD file. It's currently done with an Ant script, but any scripting language will do. I routinely do an exercise which involves editing an ODD, generating a schema, using it to create a new file, et da capo. This is easy and seamless in oXyGen: doing it via the oXGarage web interface would be cumbersome and confusing. (Lou)

	=== 2. Ideally... ===		=== 2. Ideally... ===

Mholmes: /* 1. Basic required features */

2016-07-11T12:33:37Z

1. Basic required features

← Older revision		Revision as of 12:33, 11 July 2016
Line 13:		Line 13:
	<br>1.8. syntax highlighting for XML (that naturally includes XSLT)		<br>1.8. syntax highlighting for XML (that naturally includes XSLT)
	<br>1.9. XPath queries (2.0 only would be fine)		<br>1.9. XPath queries (2.0 only would be fine)
	<br>1.10 Support for Oxygen project files enabling configuration of validation, transformation and templating.		<br>1.10 Support for Oxygen project files enabling configuration of validation, transformation and templating; or an equivalent system for another editor.

	=== Comments, justification, discussion ===		=== Comments, justification, discussion ===

Mholmes: /* Comments, justification, discussion */

2016-07-11T12:33:10Z

Comments, justification, discussion

← Older revision		Revision as of 12:33, 11 July 2016
Line 22:		Line 22:
	** very true Piotr! Whatever the interface, I agree with Lou that it's an important feature.		** very true Piotr! Whatever the interface, I agree with Lou that it's an important feature.
	* 2.5: "From a sustainability perspective, I would add "open-source" to the feature set, maybe in the "2. Ideally..." section. This may not be much pertinent from the short term opportunistic point of view of a student (or a teacher), but may help consolidate tools appropriateness to TEI for the long term, which is what TEI is all about." (Serge Heiden)		* 2.5: "From a sustainability perspective, I would add "open-source" to the feature set, maybe in the "2. Ideally..." section. This may not be much pertinent from the short term opportunistic point of view of a student (or a teacher), but may help consolidate tools appropriateness to TEI for the long term, which is what TEI is all about." (Serge Heiden)
	* I have moved XPath queries from "Ideally" to "Basic features". In my experience, that's an essential point for students (and people in general). (Marjorie) I've constrained this to XPath 2.0; I think this would be sufficient. (Martin)		* I have moved XPath queries from "Ideally" to "Basic features". In my experience, that's an essential point for students (and people in general). (Marjorie) I've constrained this to XPath 2.0; I think this would be sufficient. (Martin Holmes)
	* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?		* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?
			* I've added Oxygen project files, or an equivalent system in a competing editor (Martin Holmes).

	=== 2. Ideally... ===		=== 2. Ideally... ===

Mholmes: /* Comments, justification, discussion */

2016-07-11T12:31:53Z

Comments, justification, discussion

← Older revision		Revision as of 12:31, 11 July 2016
Line 22:		Line 22:
	** very true Piotr! Whatever the interface, I agree with Lou that it's an important feature.		** very true Piotr! Whatever the interface, I agree with Lou that it's an important feature.
	* 2.5: "From a sustainability perspective, I would add "open-source" to the feature set, maybe in the "2. Ideally..." section. This may not be much pertinent from the short term opportunistic point of view of a student (or a teacher), but may help consolidate tools appropriateness to TEI for the long term, which is what TEI is all about." (Serge Heiden)		* 2.5: "From a sustainability perspective, I would add "open-source" to the feature set, maybe in the "2. Ideally..." section. This may not be much pertinent from the short term opportunistic point of view of a student (or a teacher), but may help consolidate tools appropriateness to TEI for the long term, which is what TEI is all about." (Serge Heiden)
	* I have moved XPath queries from "Ideally" to "Basic features". In my experience, that's an essential point for students (and people in general). (Marjorie)		* I have moved XPath queries from "Ideally" to "Basic features". In my experience, that's an essential point for students (and people in general). (Marjorie) I've constrained this to XPath 2.0; I think this would be sufficient. (Martin)
	* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?		* Could we preserve the possibility to use a third-party commercial tool, like Saxon PE, if the users need them and want to acquire them?

Mholmes: /* 1. Basic required features */

2016-07-11T12:30:54Z

1. Basic required features

← Older revision		Revision as of 12:30, 11 July 2016
Line 12:		Line 12:
	<br>1.7. free for students (as in beer)		<br>1.7. free for students (as in beer)
	<br>1.8. syntax highlighting for XML (that naturally includes XSLT)		<br>1.8. syntax highlighting for XML (that naturally includes XSLT)
	<br>1.9. XPath queries		<br>1.9. XPath queries (2.0 only would be fine)
	<br>1.10 Support for Oxygen project files enabling configuration of validation, transformation and templating.		<br>1.10 Support for Oxygen project files enabling configuration of validation, transformation and templating.

Mholmes at 12:30, 11 July 2016

2016-07-11T12:30:19Z

← Older revision		Revision as of 12:30, 11 July 2016
Line 13:		Line 13:
	<br>1.8. syntax highlighting for XML (that naturally includes XSLT)		<br>1.8. syntax highlighting for XML (that naturally includes XSLT)
	<br>1.9. XPath queries		<br>1.9. XPath queries
			<br>1.10 Support for Oxygen project files enabling configuration of validation, transformation and templating.

	=== Comments, justification, discussion ===		=== Comments, justification, discussion ===

Mburghart: /* 2. Ideally... */

2016-07-11T11:34:23Z

2. Ideally...

← Older revision		Revision as of 11:34, 11 July 2016
Line 31:		Line 31:
	<br>2.5. open source		<br>2.5. open source
	<br>2.6. validation with Relax NG '''based on the xml-model PI in the document'''		<br>2.6. validation with Relax NG '''based on the xml-model PI in the document'''
			<br>2.7. possibility to auto-update the TEI schema at each new release

	=== 3. Features that can be eliminated from a "teaching editor" in order to decrease its cost ===		=== 3. Features that can be eliminated from a "teaching editor" in order to decrease its cost ===