Comments (3)
Also we had briefly talked about whether we want to do versioning to make when there is a variation in the "appearance" of text. So for example in the original articles there may be a comma somewhere that doesn't appear in the Barkley text or in the original articles frequently when the title of the newspaper is referenced it is in all caps whereas in the Barkley text just Times is italicized. I imagine markup for these two situations would look like this:
Example 1: <app><rdg wit="#CT021">,</rdg><rdg wit="#WSGC23"></rdg></app>
Example 2: <app><rdg wit="#CT021"><name rend="case(allcaps)" ref="#CT">THE TIMES</name></rdg><rdg wit="#WSGC23">the <name rendition="italic" ref="#CT">Times</name></rdg></app>
However, we (@spadafour and I) couldn't really see the purpose behind doing this. It is more obvious why these types of things should be kept for poetry, but we couldn't come up with any strong reasoning to keep it for newspaper articles. I think we are going to just make whatever the representation in the original articles be what is kept, but I wanted to see if anyone had a reason we should consider for marking those type of differences between versions. If we would decide to do the markup for this kind of versioning I would argue that the <name>
elements that identify when the newspaper is being referenced would have to sit inside of the <app><rdg>
setup because of the varying @rend
attributes that determine how the text is rendered.
@ebeshero @ghbondar @nlottig94 @brookestewart @djbpitt
from cityslavegirls.
@RJP43 These are good questions. You want to establish a clear methodology for what you are going to mark and what you are going to ignore silently as not relevant. You can create an editorial statement that will sit in your TEI header, in the <encodingDesc>
that will explain openly what you are ignoring and why you and your team are ignoring it. You can say that the use of blockcaps doesn't matter semantically and that these are not marked in your comparison of versions. Here's Chapter 2 of the TEI Guidelines on the TEI header, which you'll want to be thinking about developing more.
I think it's fine to wrap the <app>
elements in your persName, placeName, orgName (etc.) elements. Keep the coding as simple as you can, and keep in view the purpose of your versioning.
from cityslavegirls.
We have decided on the markup for version control. Please refer to our codebook and/or our first version controlled article 8-19
from cityslavegirls.
Related Issues (20)
- Where are we going? HOT 5
- The tagging saga continues.... Dashes and Quotation Marks HOT 2
- The tagging saga continues ... Grammatical Markup HOT 5
- XSLT Batch Transformation
- Schematron Issue HOT 3
- Network Analysis Discussion: Bimodal and Directed HOT 27
- What is done: HOT 6
- Using PHP to transform XML to HTML with XSLT HOT 9
- Data for *Possible* Mapping HOT 9
- Preparing Historic Maps for the Web HOT 2
- What needs to be done:
- Help with XSLT -- Suggestions Please!! HOT 3
- Checkbox Javascript??? HOT 1
- Official Submission Spring 2016 HOT 3
- Notes for Revision on Nell Nelson Website HOT 1
- Summer Transcription and Coding Work HOT 10
- ILiADS Ideas and Job Opportunities HOT 40
- Archetype Network Graphs HOT 9
- Mapping/Image Mapping Stuff HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cityslavegirls.