Difference between revisions of "BPG Feedback on Complete Draft"
Jump to navigation
Jump to search
m |
m |
||
| Line 3: | Line 3: | ||
The main sections of the BPG are outlined below to facilitate orderly feedback :-). '''Please provide feedback by Friday, April 10th''' so Kevin and I have enough time to compile any of the more significant issues for discussion during our upcoming meeting on April 14th. | The main sections of the BPG are outlined below to facilitate orderly feedback :-). '''Please provide feedback by Friday, April 10th''' so Kevin and I have enough time to compile any of the more significant issues for discussion during our upcoming meeting on April 14th. | ||
| − | Add each new comment as bullet and be sure to attribute comments so we know how to follow-up if there's some debate. For example: | + | Add each new comment as a bullet point and be sure to attribute comments so we know how to follow-up if there's some debate. For example: |
* feedback blah blah, [[User:Mdalmau|Mdalmau]] | * feedback blah blah, [[User:Mdalmau|Mdalmau]] | ||
| − | |||
==Introduction== | ==Introduction== | ||
| + | * Task Force w/c though historically correct may lose context in this new revision. Consider something more generic like "Working Group" or past tense: "the Task Force attempted to make these ..." [[User:Mdalmau|Mdalmau]] | ||
==General Recommendations== | ==General Recommendations== | ||
Revision as of 22:30, 7 April 2009
The main sections of the BPG are outlined below to facilitate orderly feedback :-). Please provide feedback by Friday, April 10th so Kevin and I have enough time to compile any of the more significant issues for discussion during our upcoming meeting on April 14th.
Add each new comment as a bullet point and be sure to attribute comments so we know how to follow-up if there's some debate. For example:
- feedback blah blah, Mdalmau
Contents
- 1 Introduction
- 2 General Recommendations
- 3 Structure of a TEI Document
- 4 The TEI Header
- 5 Linking between encoded text and images of source documents
- 6 LEVEL 1: Fully Automated Conversion and Encoding
- 7 LEVEL 2: Minimal Encoding
- 8 LEVEL 3: Simple Analysis
- 9 LEVEL 4: Basic Content Analysis
- 10 LEVEL 5: Scholarly Encoding Projects
- 11 General Guidelines for Attribute Usage
- 12 Acknowledgements
- 13 Appendix A: History of this Document
Introduction
- Task Force w/c though historically correct may lose context in this new revision. Consider something more generic like "Working Group" or past tense: "the Task Force attempted to make these ..." Mdalmau
