BPG Feedback on Complete Draft - Revision history

Kshawkin: /* General Level 3 Recommendations */ description of encoding of index is good enough

2009-04-19T23:11:06Z

‎General Level 3 Recommendations: description of encoding of index is good enough

Kshawkin: /* General Level 3 Recommendations */ fixed wiki markup

2009-04-19T23:08:19Z

‎General Level 3 Recommendations: fixed wiki markup

Kshawkin: /* General Level 3 Recommendations */ end-of-division notes resolved for now

2009-04-19T23:06:58Z

‎General Level 3 Recommendations: end-of-division notes resolved for now

Kshawkin: /* LEVEL 4: Basic Content Analysis */ Kevin incorporated instructions for indexes into Level 4

2009-04-17T13:22:04Z

‎LEVEL 4: Basic Content Analysis: Kevin incorporated instructions for indexes into Level 4

Mdalmau: /* Introduction */

2009-04-16T23:29:55Z

‎Introduction

Kshawkin: /* LEVEL 2: Minimal Encoding */ not all examples use @facs any more

2009-04-16T13:15:25Z

‎LEVEL 2: Minimal Encoding: not all examples use @facs any more

Mdalmau: /* LEVEL 4: Basic Content Analysis */

2009-04-15T22:35:26Z

‎LEVEL 4: Basic Content Analysis

Mdalmau: /* LEVEL 4: Basic Content Analysis */

2009-04-15T22:35:12Z

‎LEVEL 4: Basic Content Analysis

Mdalmau: /* Linking between encoded text and images of source documents */

2009-04-15T22:32:05Z

‎Linking between encoded text and images of source documents

Mdalmau: /* Structure of a TEI Document */

2009-04-15T15:13:46Z

‎Structure of a TEI Document

@@ Line 71: / Line 71: @@
 * <strike>Use of the "n" attribute for <l> should be optional.  Remove from example? Or add optional "n" usage to the table? [[User:Mdalmau|Mdalmau]] (reported by Rich)</strike> We decided to remove n= from l element in Level 3.
-* Check: "Add the "target" attribute (@target) to reference the <pb> identifier to generate links from the index into the text proper." And in general the consistency with how we list attributes, i.e. "target" attribute or target= attribute; or @target, etc. [[User:Natasha|Natasha]]
+* <strike>Check: "Add the "target" attribute (@target) to reference the <pb> identifier to generate links from the index into the text proper." And in general the consistency with how we list attributes, i.e. "target" attribute or target= attribute; or @target, etc. [[User:Natasha|Natasha]]</strike>
+** <strike>I revised this to make it somewhat clearer, but I think it should be rewritten and an example (even a fake one) included.  It would be good to give guidance on what to do with things like page ranges in an index and errors in the index. ([[User:Kshawkin|Kshawkin]])</strike> No full example yet provided, but ext revised to make it clearer. People can decide on their own what to do about page ranges and errors.
 === Level 3 Examples ===

@@ Line 68: / Line 68: @@
 ** <strike>Do we handle with: &lt;ref target="#note01">1</ref> that points to end of division [1] <note xml:id="note01">blah</note>?</strike>
 ** <strike>Do we need to support bi-directional linking: &lt;ref target="#note01" xml:id="ref01">1</ref> and <note xml:id="note01">&lt;ref target="#ref01">[1]</ref>blah</note>? [[User:Mdalmau|Mdalmau]]</strike>
-*** <strike>See email from Kevin sent on 2009-04-14.</strike> Since no feedback from Syd, we went with option b from Kevin's email even though this doesn't agree with the TOC markup, based on P5, which uses <ptr> instead of <ref> when it might be expected.
+*** <strike>See email from Kevin sent on 2009-04-14.</strike> Since no feedback from Syd, we went with option b from Kevin's email even though this doesn't agree with the TOC markup, based on P5, which uses <tt>ptr</tt> instead of <tt>ref</tt> when it might be expected.
 * <strike>Use of the "n" attribute for <l> should be optional.  Remove from example? Or add optional "n" usage to the table? [[User:Mdalmau|Mdalmau]] (reported by Rich)</strike> We decided to remove n= from l element in Level 3.

@@ Line 65: / Line 65: @@
 * <strike>sorry, but what does "Forme Works" mean? [[User:Natasha|Natasha]]</strike> clarified this TEI term
-* 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.
+* <strike>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.</strike>
-** Do we handle with: &lt;ref target="#note01">1</ref> that points to end of division [1] <note xml:id="note01">blah</note>?
+** <strike>Do we handle with: &lt;ref target="#note01">1</ref> that points to end of division [1] <note xml:id="note01">blah</note>?</strike>
-** Do we need to support bi-directional linking: &lt;ref target="#note01" xml:id="ref01">1</ref> and <note xml:id="note01">&lt;ref target="#ref01">[1]</ref>blah</note>? [[User:Mdalmau|Mdalmau]]
+** <strike>Do we need to support bi-directional linking: &lt;ref target="#note01" xml:id="ref01">1</ref> and <note xml:id="note01">&lt;ref target="#ref01">[1]</ref>blah</note>? [[User:Mdalmau|Mdalmau]]</strike>
-*** See email from Kevin sent on 2009-04-14.
+*** <strike>See email from Kevin sent on 2009-04-14.</strike> Since no feedback from Syd, we went with option b from Kevin's email even though this doesn't agree with the TOC markup, based on P5, which uses <ptr> instead of <ref> when it might be expected.
 * <strike>Use of the "n" attribute for <l> should be optional.  Remove from example? Or add optional "n" usage to the table? [[User:Mdalmau|Mdalmau]] (reported by Rich)</strike> We decided to remove n= from l element in Level 3.

@@ Line 84: / Line 84: @@
 * Moved Name Tagging recommendations from bullet point under General Recommendations to its own section.  The explanation and examples are too dense for a bullet point.  We may need to find a better place for this. [[User:Mdalmau|Mdalmau]]
 ** Not contested.
-* Natasha to incorporate index "tip" originally in level 3 in level 4:
+* <strike>Natasha to incorporate index "tip" originally in level 3 in level 4:
 <p>'''Back Matter'''</p>
-      <p>'''&lt;div type="index"&gt;''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt>&lt;ref&gt;</tt> element used to mark up page numbers given in the index entry.  Add the "target" attribute (@target) to reference the n= attribute of the <tt>&lt;pb&gt;</tt> of the referenced page.</p>
+      <p>'''&lt;div type="index"&gt;''': Use [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CONOIX lists] to mark up index entries, with the <tt>&lt;ref&gt;</tt> element used to mark up page numbers given in the index entry.  Add the "target" attribute (@target) to reference the n= attribute of the <tt>&lt;pb&gt;</tt> of the referenced page.</p></strike> Kevin just did this.

@@ Line 8: / Line 8: @@
 ==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]]
+* <strike>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 ..."</strike> [[User:Mdalmau|Mdalmau]]
 ==General Recommendations==

@@ Line 49: / Line 49: @@
 Consider revision? "Level 2 texts do not require any special knowledge or manual intervention below the section level." [[User:Natasha|Natasha]]
-In "Linking between encoded text and images of source documents", we say that "The examples below use the former method", i.e. "Use the @facs attribute on each <pb> element to point to the corresponding page image using a URI." Indeed that's what we use in the Level 1 example:
+<strike>In "Linking between encoded text and images of source documents", we say that "The examples below use the former method", i.e. "Use the @facs attribute on each <pb> element to point to the corresponding page image using a URI." Indeed that's what we use in the Level 1 example:
 <pb n="114" facs="00000002.tif"/>
@@ Line 56: / Line 56: @@
 [[User:Natasha|Natasha]]
-maybe to keep one - Alger Hiss document - example?[[User:Natasha|Natasha]]
+maybe to keep one - Alger Hiss document - example?[[User:Natasha|Natasha]]</strike> No longer says "The examples below use the former method".
 ==LEVEL 3: Simple Analysis==

@@ Line 83: / Line 83: @@
 * <strike>Matt has provided an @key example; some possible debate about where the explanation appears in the Header</strike> [[User:Mdalmau|Mdalmau]]
 * Moved Name Tagging recommendations from bullet point under General Recommendations to its own section.  The explanation and examples are too dense for a bullet point.  We may need to find a better place for this. [[User:Mdalmau|Mdalmau]]
 === Level 4 Letters ===

@@ Line 28: / Line 28: @@
 ==Linking between encoded text and images of source documents==
 * <strike>Consider moving this text up under the General Rec. section. [[User:Mdalmau|Mdalmau]]</strike> done
-* 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. [[User:Mdalmau|Mdalmau]]
+* <strike>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.</strike> [[User:Mdalmau|Mdalmau]]
-** Kevin suggested that we need more info for how to use xml:id with METS.  I am not quite sure how to do this at-a-glance and any attempt at detail will lead us into a significant discussion about METS.  Here are some things we can say, but may not all of them (and hopefully Chris P. can provide some guidance):
+** <strike>Kevin suggested that we need more info for how to use xml:id with METS.  I am not quite sure how to do this at-a-glance and any attempt at detail will lead us into a significant discussion about METS.  Here are some things we can say, but may not all of them (and hopefully Chris P. can provide some guidance):</strike>
-*** Use xml:id used as a "conceptual" identifier for content but not explicit representation of content (it doesn't "point to" content)
+*** <strike>Use xml:id used as a "conceptual" identifier for content but not explicit representation of content (it doesn't "point to" content)</strike>
-*** fileSec used to explicitly list all the images (master, jpg, pdf)
+*** <strike>fileSec used to explicitly list all the images (master, jpg, pdf)</strike>
-*** structMap orders the pages by page break and references each image defined in fileSec [[User:Mdalmau|Mdalmau]]
+*** <strike>structMap orders the pages by page break and references each image defined in fileSec</strike> [[User:Mdalmau|Mdalmau]]
 ==LEVEL 1: Fully Automated Conversion and Encoding==

← Older revision		Revision as of 15:13, 15 April 2009
Line 16:		Line 16:

	* Do we need to reference <tt><facsimile></tt>? [[User:Mdalmau\|Mdalmau]]		* Do we need to reference <tt><facsimile></tt>? [[User:Mdalmau\|Mdalmau]]
		+	** We don't. We assume Libraries will use METS for that functionality.

	==The TEI Header==		==The TEI Header==