Difference between revisions of "BPG Feedback on Complete Draft"
Jump to navigation
Jump to search
(→LEVEL 4: Basic Content Analysis) |
(→LEVEL 3: Simple Analysis) |
||
| Line 29: | Line 29: | ||
=== General Level 3 Recommendations === | === General Level 3 Recommendations === | ||
| − | Need to explain more about how to encode end-of-division notes. They need an n= attribute, but they also need a <tt>ptr</tt> in the text. | + | * Need to explain more about how to encode end-of-division notes. They need an n= attribute, but they also need a <tt>ptr</tt> in the text. |
| + | * Use of the "n" attribute for <l> should be optional. Remove from example? Or add optional information to the table? [[User:Mdalmau|Mdalmau]] | ||
==LEVEL 4: Basic Content Analysis== | ==LEVEL 4: Basic Content Analysis== | ||
Revision as of 22:47, 8 April 2009
The main sections of the BPG are outlined below to facilitate orderly feedback :-). Please provide feedback by Saturday, April 11th 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
General Recommendations
- Conisder moving facsimile page image info here as the final bullet point. Mdalmau
Structure of a TEI Document
The TEI Header
Linking between encoded text and images of source documents
- Consider moving this text up under the General Rec. section. Mdalmau
- Do we need to say this: "The examples below use the former method." And do we want all examples to use @facs? I think we should mix it up since we are recommending both options. Mdalmau
LEVEL 1: Fully Automated Conversion and Encoding
LEVEL 2: Minimal Encoding
LEVEL 3: Simple Analysis
General Level 3 Recommendations
- Need to explain more about how to encode end-of-division notes. They need an n= attribute, but they also need a ptr in the text.
- Use of the "n" attribute for <l> should be optional. Remove from example? Or add optional information to the table? Mdalmau
LEVEL 4: Basic Content Analysis
- For name tagging, recommend the use of @ref when the target is web accessible and @key when not. Mdalmau
- Matt has provided an @key example; some possible debate about where the explanation appears in the Header Mdalmau
