|
200 | 200 | projects, though the TEI Consortium website has for many years offered a platform
|
201 | 201 | for one: <title level="a">Projects Using the TEI,</title> accessed May 17, 2021,
|
202 | 202 | <ptr target="https://tei-c.org/activities/projects/"/>. More recently, the
|
203 |
| - TEIhub project lists more than 12,500 <ptr type="software" xml:id="GitHub" |
204 |
| - target="#GitHub"/><rs type="soft.name" ref="#GitHub">GitHub</rs>-hosted TEI |
205 |
| - projects (last updated May 11, 2021, <ptr target="https://teihub.netlify.app/"/>); |
206 |
| - an associated bot called TEI Pelican provides a daily twitter feed of new <ptr |
207 |
| - type="software" xml:id="GitHub" target="#GitHub"/><rs type="soft.name" |
208 |
| - ref="#GitHub">GitHub</rs> repositories containing a TEI header. We are unaware |
209 |
| - of any systematic analysis of the application types indicated by these data |
210 |
| - sources, but a glance gives the impression that traditional editorial and |
211 |
| - resource-building projects predominate.</note> |
| 203 | + TEIhub project lists more than 12,500 <ptr type="software" xml:id="R1" |
| 204 | + target="#GitHub"/><rs type="soft.name" ref="#R1">GitHub</rs>-hosted TEI |
| 205 | + projects (last updated May 11, 2021, <ptr type="software" xml:id="R7" |
| 206 | + target="#teipelican"/><rs type="soft.url" ref="#R7"><ptr |
| 207 | + target="https://teihub.netlify.app/"/></rs>); an associated bot called <rs |
| 208 | + type="soft.url" ref="#R7">TEI Pelican</rs> provides a daily twitter feed of new |
| 209 | + <ptr type="software" xml:id="R2" target="#GitHub"/><rs type="soft.name" |
| 210 | + ref="#R2">GitHub</rs> repositories containing a TEI header. We are unaware of |
| 211 | + any systematic analysis of the application types indicated by these data sources, |
| 212 | + but a glance gives the impression that traditional editorial and resource-building |
| 213 | + projects predominate.</note> |
212 | 214 | </p>
|
213 | 215 | <p>The work of the Action<note>Further information about the Action is available from
|
214 | 216 | its website at <ptr target="https://www.distant-reading.net/"/>. For information
|
|
228 | 230 | issues of sampling and balance were prepared for discussion and approval by the
|
229 | 231 | members of WG1, and remain available from the Working Group’s website. <note>These
|
230 | 232 | and other documents are available from the Action’s <ptr type="software"
|
231 |
| - xml:id="GitHub" target="#GitHub"/><rs type="soft.name" ref="#GitHub" |
232 |
| - >GitHub</rs> page, accessed May 17, 2021, <ptr |
233 |
| - target="https://distantreading.github.io/"/>.</note> |
| 233 | + xml:id="R3" target="#GitHub"/><rs type="soft.name" ref="#R3">GitHub</rs> page, |
| 234 | + accessed May 17, 2021, <ptr target="https://distantreading.github.io/"/>.</note> |
234 | 235 | </p>
|
235 | 236 | </div>
|
236 | 237 | <div xml:id="eltec">
|
|
653 | 654 | <p>In the ELTeC project, we begin by defining an ODD which selects from TEI all the
|
654 | 655 | components used by any ELTeC schema at any level. This ODD also contains
|
655 | 656 | documentation and specifies usage constraints applicable across every schema. This
|
656 |
| - base ODD is then processed using the TEI standard odd2odd stylesheet to produce a |
| 657 | + base ODD is then processed using the <ptr type="software" xml:id="R8" |
| 658 | + target="#odd2odd"/><rs type="soft.name" ref="#R8">TEI standard odd2odd stylesheet</rs> to produce a |
657 | 659 | stand-alone set of TEI specifications which we call eltec-library. Three different
|
658 | 660 | ODDs, eltec-0, eltec-1, and eltec-2, then derive specific schemas and documentation
|
659 | 661 | for each of the three ELTeC levels, using this library of specifications as a base
|
|
662 | 664 | resulting encoding standard. As with other ODDs, we are then able to produce
|
663 | 665 | documentation and formal schemas which reflect exactly the scope of each encoding
|
664 | 666 | level.</p>
|
665 |
| - <p>The ODD sources and their outputs are maintained on <ptr type="software" |
666 |
| - xml:id="GitHub" target="#GitHub"/><rs type="soft.name" ref="#GitHub">GitHub</rs> |
667 |
| - and are also <ptr target="http://doi.org/10.5281/zenodo.3546326"/>published on Zenodo |
668 |
| - (<ref type="bibl" target="#odebrecht2019">Odebrecht et al. 2019</ref>) along with |
669 |
| - the ELTeC corpora.<note>The <ptr type="software" xml:id="GitHub" target="#GitHub" |
670 |
| - /><rs type="soft.name" ref="#GitHub">GitHub</rs> repository for the ELTeC |
671 |
| - collection (last updated May 17, 2021) is found at <ptr |
| 667 | + <p>The ODD sources and their outputs are maintained on <ptr type="software" xml:id="R4" |
| 668 | + target="#GitHub"/><rs type="soft.name" ref="#R4">GitHub</rs> and are also <ptr |
| 669 | + target="http://doi.org/10.5281/zenodo.3546326"/>published on <ptr type="software" xml:id="R9" |
| 670 | + target="#zenodo"/><rs type="soft.name" ref="#R9">Zenodo</rs> (<ref |
| 671 | + type="bibl" target="#odebrecht2019">Odebrecht et al. 2019</ref>) along with the |
| 672 | + ELTeC corpora.<note>The <ptr type="software" xml:id="R5" target="#GitHub"/><rs |
| 673 | + type="soft.name" ref="#R5">GitHub</rs> repository for the ELTeC collection |
| 674 | + (last updated May 17, 2021) is found at <ptr |
672 | 675 | target="https://github.com/COST-ELTeC/"/>; the Zenodo community within which it
|
673 | 676 | is being published (last updated April 11, 2021) lives at <ptr
|
674 | 677 | target="https://zenodo.org/communities/eltec/"/>.</note>
|
|
689 | 692 | development and are expected to become available during the coming year. As noted
|
690 | 693 | above, up-to-date information about the current state of all corpora is publicly
|
691 | 694 | visible at <ptr target="http://distantreading.github.io/ELTeC/"/>, which includes
|
692 |
| - links to the individual <ptr type="software" xml:id="GitHub" target="#GitHub"/><rs |
693 |
| - type="soft.name" ref="#GitHub">GitHub</rs> repositories for each corpus.</p> |
| 695 | + links to the individual <ptr type="software" xml:id="R6" target="#GitHub"/><rs |
| 696 | + type="soft.name" ref="#R6">GitHub</rs> repositories for each corpus.</p> |
694 | 697 | <p>As well as continuing to expand the collection, and continuing to fine-tune its
|
695 | 698 | composition, we hope to improve the consistency and reliability of the metadata
|
696 | 699 | associated with each text, as far as possible automatically. For example, we have
|
|
0 commit comments