DIGIT 110: Text Encoding

• Watch Elena Pierazzo's short video "Why do we encode? Advantages of encoding texts with XML".
• Complete XML Exercise 1 (Historic Letter) and submit to Canvas.

• First, revise the code in your XML Exercise 1: Try adding tags and attributes to help track more specific pieces of information than you marked at first. Try marking people and places, for example.
• Look for pseudomarkup to convert into markup
• Choose another letter in the collection from XML Exercise 1 and try to encode it the same way.
• Optional: Try making a personography or a placeography list (even a partial one) of distinct people or places mentioned in the two letters. This can be a third file, or embedded as a section in each letter. Code the entries in this list to hold distinct names and any other information you wish, and give each entry an @xml:id attribute to hold a short distinct identifier you can use in your code. Then, apply pointer attributes (maybe @who, or @where or @ptr or @ref) in the markup of people or places in the body of the letters to point to entries to the personography or placeography using hashtags so you do not duplicate the xml:id. Where the xml:id would be coded only once on a page or in a project like so: identifier, the values of pointers can be used as many times as you like, and are just preceded with a hashmark like this: #identifier.
• Submit your revised letter XML and new letter XML (and optional personography/placeography) on Canvas for XML Exercise 2.

• (To help with Git Ex 2): Watch my short (15 minute) video showing how to git pull in changes, and the three-step of git add, git commit, and git push.
• (To help with Git Ex 2): Work with our short list of Git Commands to pull, commit, and push changes to your personal GitHub repo and/or to the digitProjectDesign-Hub.
• Complete Git Exercise 2. Send a link to your personal GitHub repo to me on Canvas (Assignments)
• (Optional: good to try:): Watch / work with Set up a Git Bash Profile (short video how-to): (this is convenient for you, and more command line knowledge).

• Git Shell Practice (starting today for seven days): Make sure your personal repo and the class repo are properly set up and cloned to your computer. Using your Bash shell, practice some basic git commands to build a habit. On alternating days, push to the other repo (if you pushed to your personal repo today, tomorrow you will pull and push a file to our class repo). Remember: ALWAYS PULL BEFORE YOU PUSH!
• Start exploring/responding to the Comparison of Emily Dickinson Projects on the textEncoding-Hub.

• Make a folder to hold this homework, since it will contain two files. Save the folder using our homework filenaming conventions.
• Open this goodMorning.xml file (open the link, and right-click to save on your computer with your homework, then open in oXygen).
• Open a new Relax-NG Compact syntax file in oXygen, and set your editor in tile view so you can see the goodMorning.xml file next to your schema file. Delete the code in the Relax NG file so you have a blank slate to start with.
• Write a Relax NG Schema in Compact Syntax that models the content of this XML file as you study it. (Save the schema in the same directory with your XML file so you can easily find it.)
• Associate the schema with the XML file (in oXygen go to Document > Schema > Associate Schema, and browse to locate the schema. Click OK and note the new schema line at the top of your XML file.
• Zip (compress) the file directory holding your XML file and the Relax NG schema file, and submit this on Canvas at the upload point for this assignment.

• Repair any broken Relax NG syntax and/or XML validation issues on previous homework submissions.
• Get started on the Crowdsourcing Transcription exercise: Choose a resource from one of the options on the assignment and begin transcribing.

• Read about the TEI in About These Guidelines and look for uses of the word interchange. Come to class with some ideas about interchange and the TEI: What do you think interchange means and why might it be important?
• Complete the Crowdsourcing Transcription exercise if you did not do so last time.
• Repair any broken Relax NG syntax and/or XML validation issues on previous homework submissions.

• TEI Exercise 3: Continue coding the AJC survey in TEI. Suggestions/options:
  • Revise your code from TEI Exercise 2 to make it valid if you need to
  • Try changing your approach, or adding some new elements from the TEI that you did not introduce before
  • Look into how to develop the msDesc in the teiHeader
  • Try coding a little more of the survey and responses
• Complete Take-home Test 2: Relax NG (by 11:59pm)

• Read Intro to Regular Expressions
• Watch ~20+ min. video: Introducing Regular Expressions in the oXygen XML Editor

• Watch followup ~20 min. video: How to do your Regex Homework in oXygen and keep a record of your Regex expressions
• Regex Exercise 1

• Finish up the Dracula Regex and post (or re-post) to Regex Ex 2 on Canvas
• Read introduction to HTML and review GitHub and git at command line
• Carefully review the Semester Project Assignment and sign up for a project option.

• Complete HTML Exercise 1 for GitHub Pages in your GitHub repo
• Read introduction to CSS (and begin editing the CSS file for your GitHub website if you feel ready.)
• Project cluster document data modeling: identify a research question or questions of interest

• Read our Introduction to XPath.
• Start working on XPath exercise 1
• Finish up the HTML exercises from last week if you need to do that and continue tinkering with HTML and CSS on your GitHub Pages site.

• Re-read and consult our Introduction to XPath, and recorded class video from Monday as you complete XPath Exercise 1.
• Complete XPath exercise 1

• Complete XPath Exercise 2 (complex predicates and functions)
• Work on markup and a schema for your semester project, and push updated files to your repo.

• Refine semester project schema and XML
• work on XPath Exercise 3 (String functions), due by Friday.

• Finish XPath Exercise 3.
• Read Introduction to XSLT, and watch one (or both) of the following orientation videos on how to set up oXygen to write XSLT:
  • orientation video (version for Mac)
  • orientation video (version for Windows)

• XSLT Exercise 1: an identity transformation
• Review Introduction to XSLT, and (re)watch one (or both) of the following orientation videos on how to set up oXygen to write XSLT:
  • orientation video (version for Mac)
  • orientation video (version for Windows)

Read Introducing Schematron

Semester Project Milestone 3: Each member of a project team work on code to help contribute to the project. Your code should be pushed to the team GitHub repo, and you should identify it by directly linking to your git commit. Each individual member of the team should work on one or more of the following:

• Continue with XML markup and refining the schema. Indicate in a Canvas message if the transcription/markup is complete or how much remains.
• Write XSLT over your project code to produce a reading view of some or all of your XML in HTML.
• Write CSS to style the output HTML. Use CSS to highlight and format anything of interest.
• Develop more content for the project website: introductions of participants, etc.
• Select a Creative Commons license for your work, and embed the code on your site.

Semester Project Milestone 4: Team members collaborate together to develop the project:

• Look for interesting data from your markup that you can pull with XPath and XSLT to view in HTML sorted lists and/or tables.
• Refine and update the project Relax NG schema to share as documentation of your code. Add comments to explain the team's thinking for schema rules worth noting.
• Prepare a Schematron file to check for issues in the project XML.
• Ensure the XML is valid against your Relax NG and Schematron schemas. Check that schema lines are properly associated and work with them to produce valid team markup.
• Revise and update XSLT processing as needed with any new and improved XML markup.
• Coordinate with the team to finalize the XML markup, making sure you are applying the appropriate/up-to-date schemas.

Your code should be pushed to the team GitHub repo, and you should identify it by directly linking to your git commit. Prepare the website, update and refine the styling, make sure Dr. B has a link to the project website to post for the presentations.