BPG Feedback on Complete Draft

Back to GBP

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

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

 * Do we need to reference &lt;facsimile>? Mdalmau

The TEI Header

 * I changed 'the Open Access Initiative (OAI)" to "the Open Archives Initiative (OAI)". Unless there is another initiative that I do not know about.Natasha


 * encodingDesc: Even though Melanie and I wrote most of the header, I don't remember any more why some information about sourceDesc is in encodingDesc/p and other info is in encodingDesc/editorialDecl/p . Seems like this info should be in one place or the other.  Suggestions?  Note that the P5 schema allows both p and non-p children of encodingDesc, but the prose implies that this isn't allowed.  I've reported to SourceForge ( https://sourceforge.net/tracker/?func=detail&atid=644062&aid=2761884&group_id=106328 ), but maybe we should do it one way or the other.  All the more reason to fix this.

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
 * 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):
 * Use xml:id to locate content but not explicit representation of content
 * fileSec used to explicitly list all the images (master, jpg, pdf)
 * structMap orders the pages by page break and references each image defined in fileSec Mdalmau

LEVEL 2: Minimal Encoding
Second paragraph of rationale: why "earlier than 1900"? Restate to explain what it is about certain older source documents that makes it difficult to use automated methods on them.

I think the last paragraph of "Rationale" in essence repeats what has been stated in the first para. Suggestions - combine them and edit to avoid repetition. Natasha

Consider revision? "Level 2 texts do not require any special knowledge or manual intervention below the section level." 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  element to point to the corresponding page image using a URI." Indeed that's what we use in the Level 1 example: 

However, here is the level 2 example:  Natasha

maybe to keep one - Alger Hiss document - example?Natasha

General Level 3 Recommendations

 * need to check for consistency: sometimes it's pb, sometimes it's &lt;pb&gt; Natasha


 * sorry, but what does "Forme Works" mean? Natasha


 * 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.
 * Do we handle with: &lt;ref target="#note01">1 that points to end of division [1] blah ?
 * Do we need to support bi-directional linking: &lt;ref target="#note01" xml:id="ref01">1 and &lt;ref target="#ref01">[1] blah ? Mdalmau
 * Use of the "n" attribute for  should be optional. Remove from example? Or add optional "n" usage to the table? Mdalmau (reported by Rich)


 * Check: "Add the "target" attribute (@target) to reference the  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. Natasha

Basic Structure: Verse
I am afraid that our examples for level 3 and level 4 verse are not that different. Level 3 verse has n= attribute for  element, while level 4 verse does not. Thoughts? Natasha

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
 * 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. Mdalmau

Level 4 Letters
I see your point, Kevin. I will try to find a more clear-cut example, but, honestly, I would stay with the one we have :-) Natasha
 * This text conflates personal letters (epistles) with situations where one text is embedded within another. These topics should be dealt with separately since there are encoding projects that encode personal correspondence only (where letters are not embedded within other texts), and there are cases of non-epistles included within frame texts. (Kshawkin)

LEVEL 5: Scholarly Encoding Projects
Syd, what do you think about my comments re your WWP example? It can be considered level 5. Natasha
 * Need examples. Syd was going to make scholarly the level 4 examples.  Any updates? Mdalmau

Appendix A: History of this Document

 * Why aren't we using the new rendition feature in P5? Mdalmau