[tei-council] class struggle procedure suggestion

[Lou's Laptop]

Syd Bauman wrote:

>A1. ED W 84 needs to be updated to reflect the current P5 
>
>  
>
This I just did. (the script that generates it is in 
p5/Utilities/listcontentmodels.xsl in CVS)


>2. ED W 84 needs to be updated so that each record is easily uniquely
>   identified [1]
>
>  
>

I'm leaving that for Sebastian, if there's a general wish to see it done

>3. For each set of modules listed below, the Class Crew holds a
>   conference call going through the module as we did for header,
>   core, etc. in Oxford. We should set aside 2 hrs for each call,
>   hoping to be done in half that.
>
>  
>
I think the calls might be more productive if they were primed with a 
set of proposed changes. Or at least some suggested ones.

>4. Notes from conference call should be posted very rapidly, ideally
>   less than 24 hrs later.
>
>5. Brief discussion period among Class Crew to affirm notes and hammer
>   out any details (by default 1 week)
>
>6. Editors implement agreed changes, post about any problems
>   encountered (approximately 1 week)
>
>7. ED W 84 is updated to reflect this set of changes
>
>I don't see any reason not to start before the next Council call.
>(Have we decided on the date for that call? Fri 24 Feb was
>suggested.) I am going to suggest Thu 26 Jan at 14:00Z for the first
>Class Crew conference call (C4 for short, although we hope not to be
>as explosive :-).
>
>
>Module Sets
>  
>
Any particular motivation for these groupings or this ordering? Just 
curious.

>------ ----
>* gaiji, nets, figures
>* transcr, textcrit, namesdate
>  
>
>* analysis, corpus, spoken (and personography, if it exists by then)
>  
>
inasmuchas it exists, it is currently in the corpus module

* iso-fs, declarefs

>* drama, tagdocs, linking
>  
>
these really look like obf to me!

>* msdescription (perhaps MD & DB should be included in con call)
>* dictionaries
>  
>

and terminology?

>There is almost nothing to be done for the following modules, so they
>have not been included in the above sets:
>* verse (only element empty)
>* certainty (all elements empty, already a member of a model class)
>* concurrent-decl (scheduled for execution by firing squad)
>
>Notes
>-----
>[1] My personal suggestion would be to add an incrementing record
>    number to each cell in the "module" column, but the details don't
>    really matter. The point is to make it so that in a web browser,
>    which typically has very limited searching capabilities, every
>    participant can find the record in question ASAP -- if someone
>    says "look at person", the others need to search through at least
>    every occurrence of "person" in content models, etc., if not every
>    occurrence of "personPart", "personGrp", etc.; if someone says
>    "look at record 0283", everyone else can be on the same record v.
>    fast.
>
>_______________________________________________
>tei-council mailing list
>tei-council at lists.village.Virginia.EDU
>http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
>
>  
>