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.