AnnArbor2012-Actions

A list of actions, those responsible, and what has been done about them from Ann Arbor 2012 face to face meeting of TEI Technical Council

Who	What	Result
KH, LB, PS, and JC	Get more examples from Ranjith of the current state of the output so that we can calculate some statistics on accuracy, and encourage Google towards making this output format public.
SR	will convert the EEBO-TCP <byline> to <signed> , which solves the issue of the EEBO-TCP import; the broader issue of <figure> will be addressed in the discussion of <floatingDiv> later.	done
SR	Add <trailer> to att.typed	done
RW, JC	http://purl.org/tei/bug/3480609 RW will check TEI documents and outputs to confirm everything licensed CC+BY and BSD2Clause (not CC+BY+SA or otherwise), and will report back about any inconsistencies. JC will close the bug, and a new one will be opened for any issues which emerge.
MH	http://purl.org/tei/bug/3472477 MH to implement change of IDs in output of guidelines
MH	http://purl.org/tei/bug/3471119 MH will implement the consensus (no spaces around em dashes used parenthetically). RW will create the styleguide document with help from KH who knows the CMS system already. The text style guide will be deleted.
JC, KH	http://purl.org/tei/bug/3395448 JC will try to discover whether Virginia is technically still a partner or not. When it’s resolved, KH will implement any changes to the website.
JC, MH	http://purl.org/tei/fr/3511134 JC and MH will conspire to implement an html:@id for attributes in HTML Guidelines output in the stylesheets.
KH	http://purl.org/tei/fr/3437509 KH will review the whole thread and make a recommendation about the form of @ref, and make the soft deprecation changes to the Guidelines; these will be reviewed by LB.
SR, PB	http://purl.org/tei/fr/3432520 Finish implementing standard attributes referring to ISOCAT
PB	http://purl.org/tei/fr/3046288 PB will contact LR and ask him to provide further examples.
KH	http://purl.org/tei/fr/3041605 KH to close ticket
JC	http://purl.org/tei/bug/3497369 (JC) Strike the sentence that’s under discussion, because then the paragraph is less confusing. We should also add a new section (12.2.4), which explains that you don’t have to use ids in @from and @to; you can also use any URIs and XPointers with TEI XPointer schemes.
MH	http://purl.org/tei/bug/3497356 MH will ask the submitter (and the TEI-L, pointing to the ticket) for any examples of the use of <div> which suggest that <listApp> might be useful (for instance, organization of <apps> into multiple <div> s with @type).
LB	http://purl.org/tei/bug/3496998 LB will add an additional example of how to combine <lacunaEnd> inside a <rdg> . Ticket will be closed.
KH	http://purl.org/tei/bug/3475748 KH to implement
SR to coordinate, KH and GB to assist	http://purl.org/tei/bug/3440771 document how to point from a <geo> to the <geoDecl> in order to indicate which coordinate system is being used. Remove from the Guidelines the statement that “All uses of geo within a document are required to use the same coordinate system.” edit the definition of <location> to say something like “defines the location of a place as *one or more* sets of geographical coordinates...” to indicate that more than one system may be used at once clarify relationship between <location> and <geo> in the prose of the Guidelines
LB	http://purl.org/tei/bug/3458222 LB will add <pc> to pPart.edit and revise the prose accordingly
LB, KH, PS	http://purl.org/tei/bug/3439980 LB to chair an ad hoc council working group to report back on this before next face2face, KH, LB, and PS to be members, others as necessary.
MH	http://purl.org/tei/bug/3500088 MH to re-visit to determine what's unclear and correct Guidelines.
SR	http://purl.org/tei/fr/3423686 Sebastian to nag Ontology SIG
PB	http://purl.org/tei/fr/3288293 PB will add a new attribute to att.pointing, called @targetLang.
JC	http://purl.org/tei/fr/2724997 and http://purl.org/tei/fr/2507305 linking audio/video; JC will write to TEI-L asking for people who are interested in this area to get in touch. He will run the message by Council first. These people will join a Council working group to come back with a consistent proposal to be discussed later at this meeting.
MH, SR, LB	MH will write a new section for “How to edit the Guidelines” which explains TEI testing framework in more detail; this will then be checked by SR and LB.
LB, MH	LB and MH to make sure a new-style inclusion TEI Lite ODD is up to date, regenerate schemas and update prose to match. The result should be packaged and archived as a stable and unchanging resource.
KH, LB, MH	KH will collaborate with LB and MH to carry out the same process of freezing with Tite.
KH	KH will make the customization available through the TEI website (we will not incorporate it into our build process because it’s too restrictive); the document itself will be mined for good ideas, and turned into a set of recommendations for changes to the Guidelines. KH to submit tickets for items to be added to the main Guidelines, since most of the items are likely to be independent and can be assessed separately.
MH	http://purl.org/tei/bug/3496958 (MH) We leave the content model alone (it’s horrible), but we use this as an example for Council to collaborate on the creation of one or more Schematron constraints which will enforce the presence of at least one <rdg> , to everyone’s edification.
JC	http://purl.org/tei/bug/3496954 No action required; JC to close ticket.	done
LB	http://purl.org/tei/bug/3496951 LB to create att.witnessed for @wit on <rdg> and <lem> and remove @wit from <rdgGrp>
GB	http://purl.org/tei/bug/3496949 GB will review the particular example mentioned on the ticket, and revise and expand it: firstly, use a straightforward witness; secondly add an example for the "unattested" case.
JC	http://purl.org/tei/fr/3490054 JC will close ticket with won't fix suggesting it for P6	done
JC	Start wiki page on P6 development ideas http://wiki.tei-c.org/index.php/P6-dev	done
SY	SY will send an email to tei-l to encourage people to add their docs to the samples page to keep open the statistical approach in the long term.
MH	MH look at existing pages for attribute classes and see if there are any examples, try adding an example to att.ascribed class spec to see if it works
SR	SR Sebastian will "show all examples" so that at the top it lists examples from the appropriate chapter, and links to that chapter.
MH	MH to create a wiki page to coordinate adding examples to attribute classes. Since most attribute classes do not have examples, all of us should generate examples to be added to attribute class pages.
SR	change build process so that you can't build without examples on attribute classes (this would have to be implemented later)
MH	http://purl.org/tei/fr/3434990 MH will write a Schematron rule requiring that <lg> contains <l> , <lg> , or <gap>
SR	http://purl.org/tei/fr/3305016 SR will implement the content model proposed by KH on SF
GB	http://purl.org/tei/fr/3416130 GB will survey the guidelines to see what kind of changes <certainty> within milestone elements would involve. He will report back via email, unless there is great disagreement the FR should be approved and implement. If there is disagreement, address at our next teleconference
JC	http://purl.org/tei/fr/3416130 JC will update the ticket in sourceforge to assign to GB and add a note about our decided action	done
JC	macro.paraContent out of place in <gram> etc [cf discussion] link to ticket is broken, so group E did not discuss; Action: JC to find out what happened to this ticket.
KH	http://purl.org/tei/fr/3500566 Implement proposal 'a' on SF ticket
GB	http://purl.org/tei/fr/3497079 GB to write a comment on the ticket giving examples of citations that would be problematic or confusing according to this proposal. Paul can also provide example citations from his U-M CV project. Kevin will discuss with Gabby and incorporate marked-up examples into proposal and revise proposal if appropriate. Leave ticket open for now