search

DigitalMitford / DM_poetry

a repository for developing files in the poetry module of the Digital Mitford project.
https://digitalmitford.github.io/DM_poetry/
GNU Affero General Public License v3.0
0 stars 0 forks source link

Revised Watlington Hill code #1

Open ebeshero opened 5 years ago

ebeshero commented 5 years ago

@KellieDC @jamesrovira @lmwilson I've (at last) revised the encoding of Watlington Hill as we discussed this summer. I'll save the new copy in Box, but it's also here in this DM_poetry repository (a new GitHub repository in our DigitalMitford organization), and the filename is the same as it's always been: WatlingtonHill.xml. It's here: https://github.com/DigitalMitford/DM_poetry/blob/master/WatlingtonHill.xml

The new file changes a few of the elements around (I replaced <div type="section"> with <lg type="section"> for example, and <head> elements inside those old div elements are now <label> elements. This permits us to nest sections of the poem inside a single <app>, which we needed for that added section in the middle of the 1827 poem. The <app> elements are streamlined/simplified across the file now...I've removed the unnecessary <app> elements that indicated where the two witnesses agreed since we only need them to indicate moments of divergence.

The new file is the first in our project to officially be schema-checked by our new ODD-generated schema! (This is a customization of the TEI that I finally made for our project in August, and I've been testing it.) It seems to be working as expected--and it should be a little more easy to work with adding @ref and @corresp attributes that point at site index or proposed site index entries. As you're in progress with those, you get gentle warnings in yellow rather than red angry oXygen error indicators, and the only red error messages are now signaled on outright serious errors. (I'm hoping our project error messages are a little clearer now, too.) And best of all, as you go to fill in values for @ref and @corresp, you'll get a drop-down menu in oXygen to choose which value is most appropriate. You'll probably still want to doublecheck against the real site index at http://digitalmitford.org/si.xml , but in most cases you're likely to find values for things like Scott's Marmion right away b/c of our super-clear human-readable xml:ids! :-) Like our old project schema line, this is pointing to an online file on GitHub, so just leave the purple lines at the top of the file alone and as long as you're connected to the internet you'll be schema-checked.

@jamesrovira This is now ready, I think, for you and @KellieDC to keep on going. Take a look through it and let me know if you have any questions about the new encoding.

ebeshero commented 5 years ago

PS: The spiffy new file is even sporting new curly quotes and curly apostrophes in the element contents. (We have to use straight quotes in attribute values, but we want to be using curlies where we can for the body of Mitford's text.) We're not doing that everywhere yet, but this is a start!

ebeshero commented 5 years ago

What remains to be done? I think there's more contextual annotation (the stuff we were discussing with our serendipitous correspondent from Watlington Hill for example). Also, (as I wrote over on Box), among other things, the existing app elements will need to be modified like we discussed to pinpoint the moments of divergence more precisely (around specific words rather than whole lines following TEI P5's parallel segmentation model in the TEI Guidelines).

Check the <pb> elements: I removed those from <app> elements since they don't contain poem content, but I added a convenient @edRef attribute so the <pb> indicates what edition it's part of. I think we only have page numbering in place for one edition. We should add it for the other edition, just as it's done here (no <app> elements needed for those). Everything will need to be carefully proofed against sources/photo facsimiles. Inside the lines of poetry, it will be best to reset the <app> elements to wrap around ONLY the divergent portions (words or characters) rather than encapsulating the entire line.

jamesrovira commented 5 years ago

Thanks much for this work, Elisa. I think I should be able to get back to this around mid October.

Jim

On Tue, Sep 25, 2018 at 9:24 PM Elisa Beshero-Bondar < notifications@github.com> wrote:

@KellieDC https://github.com/KellieDC @jamesrovira https://github.com/jamesrovira @lmwilson https://github.com/lmwilson I've (at last) revised the encoding of Watlington Hill as we discussed this summer. I'll save the new copy in Box, but it's also here in this DM_poetry repository (a new GitHub repository in our DigitalMitford organization), and the filename is the same as it's always been: WatlingtonHill.xml.

The new file changes a few of the elements around (I replaced <div type="section"> with for example, and elements inside those old div elements are now

elements that indicated where the two witnesses agreed since we only need them to indicate moments of divergence. The new file is the first in our project to officially be schema-checked by our new ODD-generated schema! (This is a customization of the TEI that I finally made for our project in August, and I've been testing it.) It seems to be working as expected--and it should be a little more easy to work with adding @ref and @corresp attributes that point at site index or proposed site index entries. As you're in progress with those, you get gentle warnings in yellow rather than red angry oXygen error indicators, and the only red error messages are now signaled on outright serious errors. (I'm hoping our project error messages are a little clearer now, too.) And best of all, as you go to fill in values for @ref and @corresp, you'll get a drop-down menu in oXygen to choose which value is most appropriate. You'll probably still want to doublecheck against the real site index at http://digitalmitford.org/si.xml , but in most cases you're likely to find values for things like Scott's Marmion right away b/c of our super-clear human-readable xml:ids! :-) Like our old project schema line, this is pointing to an online file on GitHub, so just leave the purple lines at the top of the file alone and as long as you're connected to the internet you'll be schema-checked. @jamesrovira This is now ready, I think, for you and @KellieDC to keep on going. Take a look through it and let me know if you have any questions about the new encoding. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread .

-- Dr. James Rovira http://www.jamesrovira.com/

Active CFPs