Talk:Best Practices for TEI in Libraries

The following are revisions to make to the BP before making an official "release". There is a separate list of Future changes to Best Practices for TEI in Libraries.

= Test ODDs and schemas derived from them =

Test Syd's ODDs and schemas derived from them: http://bauman.zapto.org/~syd/temp/BestPractices/. Just go to that URL, download the .rng files, and create a new XML document based on the schema. See if it allows you to insert all the elements you expect to be able to insert and whether it rebels against inserting elements that are not included in the Best Practics. Syd has been asked to make the following changes but might not have done so yet:


 * in header ODD, allow only a structured &lt;publicationStmt&gt;
 * lib1.rng: &lt;oXygen/&gt; says "Errors encountered: Probably no start pattern found".
 * The only allowed child of front, body, or back *at any level* should be a div.
 * note should not be allowed at in Level 1 or Level 2
 * ab should be the only child allowed of any div (in both Level 1 and Level 2). This element seems to be missing from the schema.
 * floatingText is missing in Level 3 or Level 4 schemas.

Possible additional tweaks to the ODDs based on email threads (need to determine whether to move to Future changes to Best Practices for TEI in Libraries):


 * Use of attribute(s) on sourceDesc/biblStruct/monogr/imprint/date is now required, and with attribute values mapping to the Dates fixed fields (per email sent by Kevin on 1/16/2010)
 * normalizing AACR2 dates for machine processing, to be shared with Thutmose project (per email sent by Kevin on 1/16/2010)

= Pending Review: Use of any P5 attributes =

On the June 2 conference call, the group agreed to create a list of all attributes to include for Level 1-4.


 * Prose changed now reflects that there are recommended/required attributes in the body of a text
 * This text will need to be revised again after the attribute list has been generated
 * We will probably add an appendix of all attributes identified
 * With the goal of creating an "include" list of attributes, Lisa compiled a list of attributes mentioned in the BP, followed by a list of all the additional attributes include in P5, see List of attributes suggested to include in BPG, and those excluded
 * The group will need to review the list for completeness
 * Syd will constrain the ODDs accordingly
 * Group will then need to test against real-life files

= Pending Review: Add history of version 3 to Appendix A =


 * Text is now in the main prose
 * Could benefit from group review
 * I reviewed and think it is good -- I was more out of the loop in 2009, so I am not the best of reviewers. But let this count as my approval! --Emcaulay 13:29, 20 June 2010 (EDT)

= Pending Review: Add Tite as Level 3.5 =


 * Dependent on ongoing Tite revisions; need confirmation from Dan O'Donnell/Perry Trolard
 * Adding level 3.5 on hold
 * Updated clarification between Tite and the BP added to the main prose

This was strongly recommended by Daniel Pitti in Ann Arbor because he felt certain that administrators and funders would be confused about the difference between TEI Tite and the Best Practices ("don't the libraries already have a TEI customization?"); in fact, Kevin has known this same confusion to arise among TEI Council members. While we have a section of the BP discussion its relationship to Tite, by having a Level 3.5, we can be more explicit about mapping between the two.

Mapping clarification from Kevin: Instead of actually mapping elements, Daniel wanted us to simply proclaim use of Tite as one of a number of appropriate encoding levels for libraries.

Naturally we will not be able to describe Tite the way we do other levels -- by simply saying "all the elements in the previous levels, plus the following". Tite uses different element names of all sorts. There's no point in having Syd make an ODD for Tite since one already exists. So what Kevin envisions here is a sort of "sidebar" about Tite, inserted between Levels 3 and 4 that discusses Tite in a bit more detail than we currently have in the beginning of the BP, with particular discussion of mapping between the two.

We recently had some discussion about the merits of this, so maybe we won't do it in the end. But if we do, we'll need a draft of this new sidebar. Two paragraphs are already written for you (the brief discussion of the relationship between Tite and the BP), and you can pull more information from Tite's discussion of an earlier version of the Best Practices.

Would someone be willing to write a first draft of all of this? Two paragraphs are already written for you, and you can pull more information from Tite's discussion of an earlier version of the Best Practices.


 * Can we just use what's written here (rather than link to it) and modify accordingly fpr our level 3.5: http://www.tei-c.org/release/doc/tei-p5-exemplars/html/tei_tite.doc.html#tei-in-lib-bpg. Didn't Kevin write this anyway?  If not, whose permission do we need?
 * I'm pretty sure Perry Trolard wrote this section. Shouldn't be a problem to use it.  However, we should carefully check all the assertions since things have likely changed since Tite was last revised.  Another round of Tite revisions is supposed to be forthcoming, so perhaps wait on this.
 * Add Perry trolard to acks? --Emcaulay 13:32, 20 June 2010 (EDT)
 * I just re-read the section on Tite and I think it sounds good. Maybe we can revisit this as the last step before finalizing these Best Practices ; if we have more information from the current version of Tite, great. If not, no big deal.

= Pending Review: Revise section on hyphenation =


 * ediotorialDecl description in Header pending; Kevin will confirm with Perry W.

= Acknowledgments = = Minor Stuff = Lisa: 3rd paragraph of introduction (after the table that lists out the levels) seems misplaced and I don't understand it. It's too vague to be useful, from my perspective.
 * May need to revise DLF thank you to something more onging if they continue ot provide support (under discussion)