Open fharrington1 opened 2 years ago
Good progress!
Instead of separate tone and tone2 attributes, would it be better to have one tone attribute and allow it to take multiple values? If possible values of tone are different from possible values of tone2, your version with different attributes is better, although you might want to pick more self-documenting names. If you're creating a second attribute because you may want to specify more that one value from the same set of possibilities, it's better to have a single attribute and allow it to contain more than one value. We can show you how to model that in Relax NG if it looks like a good way to proceed, so please keep us informed?
I think your guys' balance of emotions and tones using the elements and attributes is a really smart way of showcasing the different aspects/depths of the emotional language. I'm interested in what Dr. Birnbaum recommended, as I feel like this type of markup could be useful in our XML if specific element tags have attributes with varying values (i.e. the marked text is both "female" and "male"). I would be interested to see the Relax NG model of this variety and determine if it is something our team could consider utilizing to tweak our markup. (The whole gendered actions thing was a bit difficult when one line of text signified an action being done by 2 or more characters or varying genders). I'm also impressed at the fact that your schema was able to be valid against all of your team's markup! Are there any particular tips your team could give in juggling multiple XML documents marked up by different team members and writing a schema for them all (if this is how your markup was done)?
I'm excited to see the further progress of this project! I have a question, couldn't you just keep only one tone attribute, but have many attribute characteristics.
For example,
We got a lot done at our meeting this week! We discussed adding more emotion and tone markers, and decided to add a "tone2" attribute if the situation required a second tone. We also discussed the mark-up of our XML documents as well as pushing, and although there were some merge conflicts, they were resolved before the end of the meeting. Feral had pushed the schema and tested it against the XML and it worked! We briefly touched on thinking about ideas for the website and the reading view of our texts, and we will be talking about that at our next meeting.
For our midterm assignment Caelin will be writing the fleshed out methodology and Frances will be writing the mark-up guidelines. We will also have all of our texts fully marked-up by Tuesday so that we can each have some time to go over each others' mark-up before our next meeting and before the midterm assignment is due. For the last part of our midterm assignment, Emily asked us all to upload some sketched out ideas for what our site could potentially look like before the next meeting.