[tei-council] Proposal for choice, model.pPartEdit, and model.choicePart

Daniel O'Donnell daniel.odonnell at uleth.ca
Sun Jul 22 20:46:29 EDT 2007


Hi all,

Here is the first of two proposals relating to my concerns around choice
and app/rdg:
http://people.uleth.ca/~daniel.odonnell/Research/a-proposal-for-revisions-to-choice-app-and-modelppartedit

I'm still working on the app/rdg one but hope to have it up soon.

In summary, the proposal linked to above suggests:

     1. removing restore from model.pPartTranscriptional and placing it
        in the parent model.pPartEdit
     2. creating a new class model.restorePart to contain the relatively
        limited number of elements from macro.paraContent that restore
        can logically affect
     3. removing app from model.pPartTranscriptional and placing it in
        model.listLike
     4. removing choice from model.pPartEditorial and placing it in the
        parent model.pPartEdit
     5. getting rid of model.pPartEditorial and
        model.pPartTranscriptional (all of the contents of which after
        the revisions 1-4 are now also found in model.choicePart
     6. redefining the membership of model.pPartEdit to contain: choice,
        restore, and model.choicePart

The reasoning and advantages of these changes are discussed in the
document. There are also some other suggestions for changes in language,
etc.

I had almost proposed removing seg from model.choicePart and replacing
it with a new phrase level element named something like option or
alternative as the generic case (this is because a series of segs are
not obviously alternatives normally), but decided against it for the
time being because this may be of broader application.

-dan

-- 
Daniel Paul O'Donnell, PhD
Director, Digital Medievalist Project http://www.digitalmedievalist.org/
Associate Professor and Chair, Department of English
University of Lethbridge
Lethbridge AB T1K 3M4
Canada
Vox: +1 403 329-2378
Fax: +1 403 382-7191




More information about the tei-council mailing list