TEI Cheatsheets - Revision history

Kshawkin: Reverted edits by Kshawkin (talk) to last revision by Stuartyeates

2013-11-27T17:25:21Z

Reverted edits by Kshawkin (talk) to last revision by Stuartyeates

Kshawkin: added Category:Cheatsheets

2013-11-27T17:23:35Z

added Category:Cheatsheets

Kshawkin: /* Which TEI cheatsheets? */ added Encoding journals and other serial publications

2013-11-17T06:15:13Z

‎Which TEI cheatsheets?: added Encoding journals and other serial publications

Kshawkin: /* Facilitating the work of tool developpers */ typos

2013-11-13T14:42:09Z

‎Facilitating the work of tool developpers: typos

Stuartyeates: http://viaf.org/

2013-04-21T21:44:20Z

http://viaf.org/

Stuartyeates: http://viaf.org/

2013-04-21T21:39:43Z

http://viaf.org/

Mburghart: /* Which TEI cheatsheets? */

2013-04-19T20:15:00Z

‎Which TEI cheatsheets?

Martin de la Iglesia: /* Which TEI cheatsheets? */

2013-04-09T11:51:20Z

‎Which TEI cheatsheets?

Kshawkin: /* Which TEI cheatsheets? */ added Encoding Patent Bibliographic References

2013-04-09T02:25:58Z

‎Which TEI cheatsheets?: added Encoding Patent Bibliographic References

Mburghart: /* Why TEI cheatwsheets? */

2013-04-08T20:35:32Z

‎Why TEI cheatwsheets?

@@ Line 1: / Line 1: @@
 This page is listing the "cheatsheets" in preparation for various types of tasks or sub-communities of the TEI users community at large.
@@ Line 16: / Line 14: @@
 My feeling is that the Guidelines should be regarded as a reference book for more advanced users, not as the textbook for people starting to learn (or even people who do not really want to learn but just do). There are many different communities of Humanities scholars who use the TEI, and I am assuming that all (most?) of them know what they want to do with their texts, and have their own ways of working with them. My hope is that the cheatsheets, targetting specific Humanities communities or needs, will be a way of making the learning curve less steep for newbies. I hope that this would let people with no experience of XML feel immediately familiar with what the encoding is doing, at no great learning cost. It should get them started quickly, then it'll be up to them to see if they need (or care) to learn more and delve into the Guidelines.
-==Facilitating the work of tool developers==
+==Facilitating the work of tool developpers==
-A notable side-effect of the existence of such cheatsheets or "best practice in a nutshell" would be to greatly facilitate the work of tool developers considering to support TEI as a format in their application. It is currently most difficult for tools developpers to figure how to support TEI, because of the many possible ways of encoding the same phenomenon. Having a clearly defined list of "best practice" guides would make it easier to conform to those practices, and would hopefully boost the number of TEI-aware tools available.
+A notable side-effect of the existence of such cheatsheets or "best practice in a nutshell" would be to greatly facilitate the work of tool developpers considering to support TEI as a format in their application. It is currently most difficult for tools developpers to figure how to support TEI, because of the many possible ways of encoding the same phenomenon. Having a clearly defined list of "best practice" guides would make it easier to conform to those practices, and would hopefully boost the number of TEI-aware tools available.
 =Which TEI cheatsheets?=
@@ Line 50: / Line 48: @@
 ** Hebrew names: cf. suggestion from Hayim Lapin on TEI-L
 ** Checking names of modern authors in non-Latin scripts: cf. http://viaf.org/

← Older revision		Revision as of 17:23, 27 November 2013
Line 1:		Line 1:
		+	[[Category:Cheatsheets]]
		+
	This page is listing the "cheatsheets" in preparation for various types of tasks or sub-communities of the TEI users community at large.		This page is listing the "cheatsheets" in preparation for various types of tasks or sub-communities of the TEI users community at large.

← Older revision		Revision as of 06:15, 17 November 2013
Line 48:		Line 48:
	** Hebrew names: cf. suggestion from Hayim Lapin on TEI-L		** Hebrew names: cf. suggestion from Hayim Lapin on TEI-L
	** Checking names of modern authors in non-Latin scripts: cf. http://viaf.org/		** Checking names of modern authors in non-Latin scripts: cf. http://viaf.org/
		+
		+	*[[Encoding journals and other serial publications]]

@@ Line 14: / Line 14: @@
 My feeling is that the Guidelines should be regarded as a reference book for more advanced users, not as the textbook for people starting to learn (or even people who do not really want to learn but just do). There are many different communities of Humanities scholars who use the TEI, and I am assuming that all (most?) of them know what they want to do with their texts, and have their own ways of working with them. My hope is that the cheatsheets, targetting specific Humanities communities or needs, will be a way of making the learning curve less steep for newbies. I hope that this would let people with no experience of XML feel immediately familiar with what the encoding is doing, at no great learning cost. It should get them started quickly, then it'll be up to them to see if they need (or care) to learn more and delve into the Guidelines.
-==Facilitating the work of tool developpers==
+==Facilitating the work of tool developers==
-A notable side-effect of the existence of such cheatsheets or "best practice in a nutshell" would be to greatly facilitate the work of tool developpers considering to support TEI as a format in their application. It is currently most difficult for tools developpers to figure how to support TEI, because of the many possible ways of encoding the same phenomenon. Having a clearly defined list of "best practice" guides would make it easier to conform to those practices, and would hopefully boost the number of TEI-aware tools available.
+A notable side-effect of the existence of such cheatsheets or "best practice in a nutshell" would be to greatly facilitate the work of tool developers considering to support TEI as a format in their application. It is currently most difficult for tools developpers to figure how to support TEI, because of the many possible ways of encoding the same phenomenon. Having a clearly defined list of "best practice" guides would make it easier to conform to those practices, and would hopefully boost the number of TEI-aware tools available.
 =Which TEI cheatsheets?=

@@ Line 47: / Line 47: @@
 ** Arabic names: cf. http://jtei.revues.org/398#tocto3n3
 ** Hebrew names: cf. suggestion from Hayim Lapin on TEI-L
-** Names of modern authors: cf. http://viaf.org/
+** Checking names of modern authors in non-Latin scripts: cf. http://viaf.org/

← Older revision		Revision as of 20:15, 19 April 2013
Line 43:		Line 43:
	*[[Images Cheatsheet]]		*[[Images Cheatsheet]]
	''You have a facsimile with both textual and non-textual information, how do you encode the non-textual information and connect it with the transcription? I started compiling a similar resource, "[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI\|A Guide to Images in TEI]]", but it might be useful if we could distil that into a Cheatsheet written from an art historian's perspective. --[[User:Martin de la Iglesia\|Martin de la Iglesia]] 07:51, 9 April 2013 (EDT)''		''You have a facsimile with both textual and non-textual information, how do you encode the non-textual information and connect it with the transcription? I started compiling a similar resource, "[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI\|A Guide to Images in TEI]]", but it might be useful if we could distil that into a Cheatsheet written from an art historian's perspective. --[[User:Martin de la Iglesia\|Martin de la Iglesia]] 07:51, 9 April 2013 (EDT)''
		+
		+	*[[Encoding non-European names]]
		+	** Arabic names: cf. http://jtei.revues.org/398#tocto3n3
		+	** Hebrew names: cf. suggestion from Hayim Lapin on TEI-L

← Older revision		Revision as of 11:51, 9 April 2013
Line 40:		Line 40:

	*[[Encoding Patent Bibliographic References]]		*[[Encoding Patent Bibliographic References]]
		+
		+	*[[Images Cheatsheet]]
		+	''You have a facsimile with both textual and non-textual information, how do you encode the non-textual information and connect it with the transcription? I started compiling a similar resource, "[[User_talk:Martin_de_la_Iglesia/A_Guide_to_Images_in_TEI\|A Guide to Images in TEI]]", but it might be useful if we could distil that into a Cheatsheet written from an art historian's perspective. --[[User:Martin de la Iglesia\|Martin de la Iglesia]] 07:51, 9 April 2013 (EDT)''

← Older revision		Revision as of 02:25, 9 April 2013
Line 38:		Line 38:
	This is not something I am in any way experienced with but I suspect there is some need for cheatsheets in this department.		This is not something I am in any way experienced with but I suspect there is some need for cheatsheets in this department.
	Please use the [[Linguistic Encoding Cheatsheet]] to submit tasks and the best way do perform them.		Please use the [[Linguistic Encoding Cheatsheet]] to submit tasks and the best way do perform them.
		+
		+	*[[Encoding Patent Bibliographic References]]

@@ Line 9: / Line 9: @@
-=Why TEI cheatwsheets?=
+=Why TEI cheatsheets?=
 ==Easing the learning curve==
@@ Line 15: / Line 15: @@
 ==Facilitating the work of tool developpers==
 A notable side-effect of the existence of such cheatsheets or "best practice in a nutshell" would be to greatly facilitate the work of tool developpers considering to support TEI as a format in their application. It is currently most difficult for tools developpers to figure how to support TEI, because of the many possible ways of encoding the same phenomenon. Having a clearly defined list of "best practice" guides would make it easier to conform to those practices, and would hopefully boost the number of TEI-aware tools available.
 =Which TEI cheatsheets?=