ReasonsToUseTEI - Revision history

Stuartyeates at 19:10, 29 March 2009

2009-03-29T19:10:49Z

Stuartyeates: three more reasons

2009-03-22T19:58:23Z

three more reasons

Piotr Banski: + category "?"

2009-03-20T13:43:18Z

+ category "?"

Stuartyeates: New page: This is a quick summary of reasons to use TEI * '''No 'Tag Soup.' ''' Many generators of HTML generate an apparently random collection of tags to get a fragment of content to look as expe...

2009-03-17T22:03:03Z

New page: This is a quick summary of reasons to use TEI * '''No 'Tag Soup.' ''' Many generators of HTML generate an apparently random collection of tags to get a fragment of content to look as expe...

New page

This is a quick summary of reasons to use TEI

* '''No 'Tag Soup.' ''' Many generators of HTML generate an apparently random collection of tags to get a fragment of content to look as expected in a particular context, but when taken out of this context the tags are essentially useless. TEI prevents this from happening by defining legal occurrence scenarios of all tags, and providing rigorous tools check that the XML is valid. Presentation is handled by tools such as CSS, which was designed to handle presentation

* '''Defined Semantics.''' Whereas HTML defines hold text should ''look'' with tags such as <b/> and <u/>, TEI defines what the content of the tag ''is'', or what it ''means'' with tags such as <author/> and <opener/>.

@@ Line 8: / Line 8: @@
 * '''Community of Practice''' The TEI community practice builds on best-practice in the field of humanities computing to enable members to be at the forefront of the digital humanities
-* '''Representation of non-Unicode characters''' While many text-oriented systems struggle with the full range of Unicode characters and features, TEI goes beyond Unicode to support arbitrary characters using the glyph tag
+* '''Representation of non-Unicode characters''' While many text-oriented systems struggle with the full range of Unicode characters and features, TEI goes beyond Unicode to support arbitrary characters using the <glyph> tag
 * '''Rending the HTML or PDF''' easy rendering to PDF or HTML allows easy user access without the need for plugins, adaptors or fuss.

← Older revision		Revision as of 19:58, 22 March 2009
Line 5:		Line 5:

	* '''Defined Semantics.''' Whereas HTML defines hold text should ''look'' with tags such as <b/> and <u/>, TEI defines what the content of the tag ''is'', or what it ''means'' with tags such as <author/> and <opener/>.		* '''Defined Semantics.''' Whereas HTML defines hold text should ''look'' with tags such as <b/> and <u/>, TEI defines what the content of the tag ''is'', or what it ''means'' with tags such as <author/> and <opener/>.
		+
		+	* '''Community of Practice''' The TEI community practice builds on best-practice in the field of humanities computing to enable members to be at the forefront of the digital humanities
		+
		+	* '''Representation of non-Unicode characters''' While many text-oriented systems struggle with the full range of Unicode characters and features, TEI goes beyond Unicode to support arbitrary characters using the glyph tag
		+
		+	* '''Rending the HTML or PDF''' easy rendering to PDF or HTML allows easy user access without the need for plugins, adaptors or fuss.

← Older revision		Revision as of 13:43, 20 March 2009
Line 1:		Line 1:
		+	[[category:?]]
	This is a quick summary of reasons to use TEI		This is a quick summary of reasons to use TEI