April 9, 2015
DissCo
DissCo will be April 21st at 12pm in the DSC; Moya Bailey will be talking about establishing a professional presence online.
Encoding Meeting
We rescheduled the April 23rd encoding meeting to April 22 at 1pm. Thanks to everyone for your flexibility!
Party!
We’ll be having a party to celebrate the end of the year on May 8th in the DSC. I set up a card in the Trello ideas board to track movie nominations and suggestions for how we can celebrate a great year!
Article on WWO
Here’s the link to the article on WWO and feminist markup that I mentioned during the meeting: http://digitalcommons.unl.edu/libphilprac/1228/
Encoding Discussion:
<orgName>
Ceillie brought in a question about whether a seminary in her text should be encoded with <orgName>; we confirmed that it should and we will be expanding the examples of encoding with <orgName> in the internal documentation to clarify our use of this element.
<pause> in Pix
Sarah Stanley brought in an example from Pix’s False Friend where white spaces between words are used to indicate pauses in speech from characters who are dying. Julia suggested we look into the <pause> element for cases like this one where we don’t have any way of indicating that speakers are pausing (in contrast to places where ellipses or em dashes are used, which can be indicated typographically). We’re going to look for other places in the textbase where <pause> might be needed and confirm whether we want to add it to the schema.
Braced lists and enigmas in Ladies Diary
Nicole brought in an example from the Ladies Diary in which a list of readings is braced to point back to a source text; she’ll be circulating an example of how this encoding works and we’ll add it to the internal documentation. Nicole also asked about a genre that the Ladies Diary identifies as the “enigma,” some of which are treated as a separate section of the text, while others are interspersed with other sections of the text. In talking about the enigmas we brought up the possibility of recording @localtype values for cases like this one, where texts use specific labels that aren’t in our @type values. We’ll continue to explore this possible change in our encoding; in the mean time, if you do find any cases where recording a local type for one of your texts would be useful, please bring them to a meeting.