German Letter 3

[RJP43]

Source Materials:

German_letter3 Folder MIWschema.rng

[anais-turiello]

@jsteele1 I will do part five of the exercise since you are doing part four.

[jsteele1]

@anais-turiello below is the list I created of people and places in our document, part four of the exercise:

Tatjana Willims-Jones, ref="twj", mentioned: 1 Sabine Meyers, ref="sm", mentioned: 1 Zanabe Othman, ref="zo", mentioned: 1 Lili Elbe, key="lili", mentioned: 8 Einar Wegnar, key="wegenerE", mentioned: 16 Hotel Brutze, key="NO ID", mentioned: 2 Kopenhagen, key="copenhagen", mentioned: 2 (line 108 and 123) Copenhagen, key="copenhagen", mentioned: 2 Grete, key="wegenerG", mentioned:1 Grete's, NO KEY OR ID (line 115)

[jsteele1]

Part five: Two elements used in our XML file were:

1. <gap extent="6"> this is used to indicate the gap in between pieces of writing. This follows TEI guidelines because for every different gap in this letter its attribute is a number that corresponds with which gap it is referring to and this labeling method makes it easy to understand by you the coder.

2. <div type="letterTranslate"> this is used to indicate the separation of the original letter and the translated letter. This specific key follows TEI guidelines advice to pick attributes which helps indicate what the division is and are easy to understand by you the coder.

please note I, @RJP43, had to correct your markdown by adding tic marks around your elements

[anais-turiello]

Part 5:

1. The element <respStmt> was used to indicate the statement of responsibility regarding the intellectual content of the piece. This follows the TEI guidelines because the names of the translators for the letter follow, therefore crediting the individuals who contributed.
2. the element <p> is used to mark paragraphs in prose. This follows TEI guidelines because it is an element capable of holding several other elements as well as divides the text accordingly.

please note I, @RJP43, had to correct your markdown by adding tic marks around your elements

[jsteele1]

@anais-turiello the elements I chose didn't show up in my last comment. I used < gap extend="5"> and < div type="letterTranslate">

[RJP43]

Hi @anais-turiello and @jsteele1! 👋

Well done completing the TEI XML Exercise! :tada:
The minor issues with your submission were:

1. the placement of your schema line
2. due to the failed schema association were unable to identify actual schema validation errors

I have corrected these issues to avoid confusion and messaged you both on the upload commit history so we have a record of your original upload/submission.

For the next assignment, your team will need to reference the latest file added to the German Letter 3 Archival Materials Folder 📂 -- a screenshot of the TEI header information provided by the project manager, Emily Datskou. As a team, you will work together to create a <teiHeader> element for German Letter 3 using the information provided by Emily, the existing XML encoding, photograph(s) of the letter (a.k.a the facsimile images), and the translation/transcription documents.
(⬆️ all available in your text's folder linked above ⬆️)

Be sure to reference the TEI Header Exercise in order to let each other, @ProfPLC, and I know what tasks you each are comfortable with completing by Tuesday (2/26) 📆. Please remember the main goals in all of our assignments are team communication 💬 and collaboration 👐.

_Note: the TEI header template is available in Thursday's lesson on Capturing Metadata and as a download-able XML file containing the template <teiHeader>._ Happy coding! 💻 😃

[jsteele1]

In the first picture: Gletter3_IMG_9032.jpg. I observed that there is seems to be three different types of handwritings: 1. dark handwriting, 2. lighter handwriting, 3. red handwriting. The lighter handwriting seems to be the body of the letter. The darker handwriting seems to be headers/roman numerals. The red handwriting is written horizontally on top of the body of the letter. The letter is written on a white sheet of paper that has been folded in half, there is a small tear/fold over on the left side of the paper. The right bottom corner of the paper is folded over.

In the second picture: Gletter3_IMG_9033.jpg. I observed that this letter seems to be written in two different types of handwritings: 1. dark handwriting and 2. lighter handwriting. The lighter handwriting seems to be the body of the letter. Some things written in the lighter handwriting is crossed out. The darker seems to be headers/roman numerals. The letter is written on a white sheet of paper that has been folded in half, there is a small tear/fold over on the right side of the paper. The left bottom corner is folded over.

[anais-turiello]

I uploaded the TEI header document with all of the information as well as Jade's commentary. However, I couldn't find the information regarding the date of the XML into HTML transformation as well as the date for the completion of the HTML proofing. Let me know if there's a way to fix this.

[jsteele1]

An element not used in our project is revisionDesc, this element is used for revision history. It allows for the encoder to provide a history of changes made during the development of the electronic text. I believe we use comments for this in our project.

[jsteele1]

The last step of the assignment due tomorrow is to each post an element not used in our project (2-3 sentences) and respond to each others @anais-turiello mine is posted above so you just need to respond then post your own and I'll reply to that

[RJP43]

@jsteele1 fantastic source description of the two images, and the revisionDesc element is certainly an interesting one. I am looking forward to @anais-turiello's response and chosen element.

As for the information in the header you could not find it is because that information is yet to be supplied. As mentioned in class, anything about HTML should just be copied directly from the template and unchanged because we have not yet transformed the XML to HTML. Great work.

[anais-turiello]

Another element that was not used in our project was <encodingDesc> which is an element that documents the relationship between the electronic text and the source from which it came from. We could use this in our project to signify the relationship between Lili's handwritten letter and the typed up version of it.

[anais-turiello]

An element not used in our project is revisionDesc, this element is used for revision history. It allows for the encoder to provide a history of changes made during the development of the electronic text. I believe we use comments for this in our project.

@jsteele1 I think it would be important for us to use this element in our project because it would make it easier for us to keep track of the revisions made to the document along the way. I think it could be a way to make things more organized for us.

[jsteele1]

@anais-turiello The element you chose didn't post, but using the description you said about it I think this could be a helpful element to use in our project because we have photos and letters that we are using. That element seems like it is similar to the element I chose and it would help just keep track of things.

[RJP43]

@jsteele1 I added the tic marks around @anais-turiello's element so you can see it now.