-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Danish Letter 19310818 #20
Comments
One thing Tina and I noticed about the schema validation process is that not only did it fire up, but it fired up on the element because where it was, it wasn't well formatted. We talked about it, and because this is sort of a new thing for all of us, we think that this particular error existed because it was an issue with the document not being "well formed". We don't know a ton about encoding, but we thought that would exist because formatting has been the most foundational part of our understanding when it's come to encoding. That's been one of the key lessons so far, so it makes sense that we'd come back to an idea that we know and challenge us to master it. |
My Two Reports:
|
List of unique people:
List of unique places:
|
My Two Reports:
|
Elizabeth accurately highlighted our concerns when implementing the MIW schema into our Danish Letter. To elaborate, the specific error we encountered was present in both the English and German versions, so 2 errors in total. The error was the uncertainty with this element: persName key="kreutz?">Herr Oberartz</persName where the attribute value has a question mark. The error in English was the same: persName key="kruetz?">the head doctor</persName. Regardless, the schema was associated into XML successfully. |
@ekupchella and @tinatiehen well done completing most of the TEI XML Exercise! 🎉 The only minor issue with your submission was although you were clearly able to associate the schema in order to determine the validation errors neither of you re-uploaded the correctly associated XML to your team's folder. I went ahead and added the XML with the correct schema line to your folder just to prevent any continued confusion for the next people to work with these files. For the next assignment, your team will need to reference the latest file added to the Danish Letter 19310818 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 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 |
Elizabeth and I discussed in class that we will equally divide our TEI header tasks within our XML file, I created lines 1-43 in the TEI header, and Elizabeth took 44-96. I sent my lines to Elizabeth and she will be uploading the xml tei header file to our issue. |
A TEI element I noticed that is not utilized in our TEI header is |
@tinatiehen @ekupchella I love the idea of dividing the file up based on lines. What a nice use of the line numbering available in oXygen as well as here on GitHub. Great use of the interfaces we are using! @tinatiehen 🎉 fantastic statement regarding the element |
Really great points, Tina! I wanted to focus on how we didn't have to do |
Elizabeth, great points❗️I agree that referencing a specific schema could not only become repetitive, but the project is constantly improving and changing based on incoming information. That being said, the schema would need to reflect the progress being made and thus, could be modified and become inconsistent for any given xml. However, I find it beneficial to recognize that the |
🎉 This is a fantastic interaction @tinatiehen and @ekupchella! 🎉 |
@tinatiehen @ekupchella please be sure to upload your file containing the completed TEI Header before class. I do not see it in your team's folder. |
Source Materials:
19310818 Folder
MIWschema.rng
The text was updated successfully, but these errors were encountered: