Difference between revisions of "PoetryVisualizationTool"

From TEIWiki
Jump to navigation Jump to search
Line 1: Line 1:
 +
All the documents described in this essay are available here: http://www.4shared.com/file/213276484/156f569f/sampleCoding.html
  
http://www.4shared.com/file/213276484/156f569f/sampleCoding.html
+
[[Category:Tools]]
 +
 
 +
[[Category:Analysis tools]]
 +
[[Category:Interfaces]]
 +
 
 +
 
 +
[[Category:Discovering]]
 +
[[Category:Annotating]]
 +
[[Category:Comparing]]
 +
[[Category:Illustrating]]
 +
[[Category:Representing]]
 +
 
 +
== Synopsis ==
 +
In collaboration with Digital Artist Ira Greenberg, I am building a Poetry Visualization Tool.  He is building the visualizations in the Processing language; I am encoding the poetry to be visualized in an xml code that is an extension of TEI, with "pa" ([Poetess Archive | http://unixgen.muohio.edu/~poetess]) elements added into it.  What I offer here is not the processing code but the extended TEI and its schema that can be used to code the meter, sound, tropology, and syntax of poetry.
 +
 
 +
== Features ==
 +
This is simply an extended tagset for analyzing poetry, at the moment, though the tag set can be used by a visualization tool in development at http://www.iragreenberg.com/ira_greenberg_data/code/poetess/index.html
 +
 
 +
== User commentary ==
 +
'''Please sign all comments.'''
 +
 
 +
== System requirements ==
 +
The Poetry Visualization tool can be run on Mac, Windows, or Linux.
 +
 
 +
== Source code and licensing ==
 +
 
 +
 
 +
== Support for TEI ==
 +
(Does it support TEI or TEI Lite "out of the box"?)
 +
(How easily can TEI be implemented?)
 +
(Are there customized versions of the tool created for the TEI community, perhaps even by those not affiliated with the tool's creators?)
 +
 
 +
== Language(s) ==
 +
(What computer language is the tool written in?)
 +
(What language(s) are used in the interface?)
 +
(What language(s) are used in the documentation?)
 +
 
 +
== Documentation ==
 +
(link to or information about documentation available)
 +
 
 +
== Tech support ==
 +
(What technical support is provided by the creators of the tool?)
 +
 
 +
== User community ==
 +
(Are there any communities of users?)
 +
 
 +
== Sample implementations ==
 +
(links to demo sites running the tool or successful implementations of it)
 +
 
 +
== Current version number and date of release ==
 +
(type in that information here)
 +
 
 +
== History of versions ==
 +
(type in that information here)
 +
 
 +
== How to download or buy ==
 +
(type in that information here)
 +
 
 +
== Additional notes ==
 +
(type in that information here)

Revision as of 00:44, 2 February 2010

All the documents described in this essay are available here: http://www.4shared.com/file/213276484/156f569f/sampleCoding.html

Synopsis

In collaboration with Digital Artist Ira Greenberg, I am building a Poetry Visualization Tool. He is building the visualizations in the Processing language; I am encoding the poetry to be visualized in an xml code that is an extension of TEI, with "pa" ([Poetess Archive | http://unixgen.muohio.edu/~poetess]) elements added into it. What I offer here is not the processing code but the extended TEI and its schema that can be used to code the meter, sound, tropology, and syntax of poetry.

Features

This is simply an extended tagset for analyzing poetry, at the moment, though the tag set can be used by a visualization tool in development at http://www.iragreenberg.com/ira_greenberg_data/code/poetess/index.html

User commentary

Please sign all comments.

System requirements

The Poetry Visualization tool can be run on Mac, Windows, or Linux.

Source code and licensing

Support for TEI

(Does it support TEI or TEI Lite "out of the box"?) (How easily can TEI be implemented?) (Are there customized versions of the tool created for the TEI community, perhaps even by those not affiliated with the tool's creators?)

Language(s)

(What computer language is the tool written in?) (What language(s) are used in the interface?) (What language(s) are used in the documentation?)

Documentation

(link to or information about documentation available)

Tech support

(What technical support is provided by the creators of the tool?)

User community

(Are there any communities of users?)

Sample implementations

(links to demo sites running the tool or successful implementations of it)

Current version number and date of release

(type in that information here)

History of versions

(type in that information here)

How to download or buy

(type in that information here)

Additional notes

(type in that information here)