TEIWiki - User contributions [en]

EpiDoc

2013-08-05T15:59:01Z

GabrielBodard: updated urls

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the [http://www.eagle-eagle.it/ EAGLE] and [http://www.rzuser.uni-heidelberg.de/~gv0/ HGV] databases.

=== Tools ===

The EpiDoc community also produce several Open Source tools for use by editors of epigraphic (and related) XML editions. Among which:

* EpiDoc Example Stylesheets (XSLT for rendering HTML, TXT or ODF representations recogisable by traditional editors [https://sourceforge.net/p/epidoc/wiki/Stylesheets/])
* Transcoder (Java tool for translating between Beta Code, Unicode NF C, NF D, and other encodings [http://epidoc.sourceforge.net/resources.shtml#transcoder])
* CHETC (python tool for converting conventional Leiden to EpiDoc XML)
* Crosswalker (abstractable, customizable tool for defining relationships between XML schemas) (defunct)

== Agenda ==

Concerete plan to move into conformant TEI P5 in Fall 2008 (some modifications to P5 already proposed).

== Links ==

*[http://www.stoa.org/epidoc/gl/latest/ EpiDoc Guidelines] at Stoa
*[http://epidoc.sourceforge.net/ SourceForge project page]
*Latest EpiDoc [http://www.stoa.org/epidoc/schema/latest/tei-epidoc.xml ODD] and [http://www.stoa.org/epidoc/schema/latest/tei-epidoc.rng RNG schema]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]
[[Category:Customization]]

Current events

2013-07-08T18:00:46Z

GabrielBodard: fixed date

Current events

2013-07-07T11:54:39Z

GabrielBodard: added Sofia EpiDoc training

Council actions 2013-04

2013-06-20T11:40:05Z

GabrielBodard: fixed url

A list of actions, those responsible, and what has been done about them
from Providence, Rhode Island, 2013-04-11 to 2013-04-13 face to face
meeting of TEI Technical Council
{|class="wikitable sortable"
|'''Who'''
|'''What'''
|'''Suggested Deadline'''
|'''Result (What Was Done)'''
|-
|All of Council
|read and comment on the document (even if it's "this bit doesn't make sense to me"). http://goo.gl/AwPs6
|2013-05-17
|
|-
|EM
|to clarify the description on elementSpec on biblScope, citedRange and locus to clarify the use of @from and @to. https://sourceforge.net/p/tei/feature-requests/389/
|2013-06-07
|
|-
|EM and SB
|to take over from KH and get something from the phys bibl group, and/or encourage the generation of cheatsheets for encoding physical bibliography to go on the wiki. [— addendum, 2013-04-14 by Syd: I believe this action was on EM and SB (or perhaps EM, LB, SB); in any case, I have already spoken to Richard Noble who is not only on board but eager. —]
|2013-05-31
|
|-
|GB
|to add examples of schematron constrains on contents of <app> as the (Green) ticket says.
|2013-05-31
|
|-
|GB
|to re-read the section and rephrase/rewrite if necessary. https://sourceforge.net/p/tei/bugs/552/
|2013-05-31
|
|-
|GB
|to close the ticket with explanation, and possibly revise the text to clarify. https://sourceforge.net/p/tei/bugs/553/
|2013-04-30
| DONE
|-
|GB
|Close https://sourceforge.net/p/tei/bugs/405/ if fully incorporated into HC's proposal
|2013-04-30
| Assigned to HC
|-
|GB
|look at other suggested standards recording s<nowiki/>ex, gender, and gender identity for inclusion in the notes. https://sourceforge.net/p/tei/feature-requests/425/
|2013-04-30
| DONE
|-
|GB
|Implement https://sourceforge.net/p/tei/feature-requests/425/ changing data.s<nowiki/>ex to be datatype data.word, providing changed Guidelines prose and notes to other standards.
|2013-04-30
| DONE
|-
|GB
|to propose a more effective wording incorporating all the nuances. https://sourceforge.net/p/tei/bugs/543/
|2013-05-31
|
|-
|HC
|to change values in @unit to singular, spelled-out forms, add column, and update Guidelines examples and text for consistency with the new values. Leave @type alone because it's deprecated. https://sourceforge.net/p/tei/feature-requests/429/
|2013-05-17
|
|-
|HC
|Nudge NH, SB, and PB for input.
|2013-05-31
|
|-
|HC and SB
|specification and estimated cost for Xpointer resolver
|2013-05-31
|
|-
|HC and SR
|to test the use of @xml:space to solve this specific problem, and to see whether that's the correct solution in the long term. DONE; https://sourceforge.net/p/tei/bugs/544/
|2013-04-30
|DONE
|-
|JC
|to implement https://sourceforge.net/p/tei/feature-requests/449/ add <am> to att.typed.
|2013-04-30
|DONE at revision 12263
|-
|JC
|to close ticket https://sourceforge.net/p/tei/feature-requests/438/ as won't-fix.
|2013-04-30
|DONE
|-
|JC
|to put a copy of the SF XML dump in the Vault.
|2013-04-30
|PENDING
|-
|JC
|to talk to DavidS and ShayneB to find out if we'd be allowed to dump the wiki db, make changes, and re-upload. For the OpenCMS we could do it manually.
|2013-04-30
|DONE (investigating)
|-
|JC
|to email sourceforge and find out if we can turn this off or modify markdown setup and investigate the implications/options.
|2013-04-30
|Investigating options.
|-
|JC
|https://sourceforge.net/p/tei/bugs/504/ implement (already done.) Close Ticket.
|2013-04-30
|DONE (Then revised slightly subsequently)
|-
|JC
|to investigate the Allura system if possible to make the meanings of the (priority) numbers explicit.
|2013-04-30
|DONE
|-
|JC
|to fix this (change "seven" to "four"). https://sourceforge.net/p/tei/bugs/555/
|2013-04-30
|LB Fixed before I had a chance to.
|-
|JC
|get back in touch with SIG conveners to encourage them to become active.
|2013-05-31
|DONE
|-
|JC
|Inform CMC SIG of their acceptance.
|2013-04-30
|DONE
|-
|JC
|Decide on deadlines for actions, but add them to the wiki not official minutes.
|2013-04-22
|DONE!
|-
|JC
|Schedule next teleconference.
|2013-05-17
|PENDING
|-
|JC
|to prod PB on all tickets assigned to him.
|2013-05-31
|PENDING
|-
|JC
|Ensure minutes are tidied up, posted online, summarised and that summary posted to TEI-L.
|2013-04-30
|DONE
|-
|JC and LB
|specification and estimated cost for new web Roma, etc.
|2013-05-31
|PENDING
|-
|JC and SB
|to encourage Piotr to get some people into a room in Rome to discuss this(?). SB will attend to push the more generic viewpoint.
|2013-05-31
|PENDING
|-
|KH
|to email Council to solicit volunteers for TEI Google work, and provide a link to the samples again.
|2013-04-30
|DONE
|-
|KH
|to go through recent soft and hard deprecations and decide whether they're correct (hard) or not, to remove @status and add @validUntil attribute.
|2013-05-31
|[[Practices_no_longer_recommended_or_now_deprecated|Plan of action with questions for others]]
|-
|KH
|to address the original issue at his leisure. https://sourceforge.net/p/tei/bugs/496/
|2013-05-31
|
|-
|KH
|to close ticket wontfix. https://sourceforge.net/p/tei/bugs/493/
|2013-04-30
|DONE
|-
|KH
|to implement the wording changes. https://sourceforge.net/p/tei/bugs/541/
|2013-05-31
|
|-
|KH
|change <idno> to <ref> or <pointer> as appropriate. The criterion to apply is whether the URL in question is an identifier or a link.
|2013-05-31
|
|-
|KH
|to add text to tcw24. Will look at how things are written in the introductory section about terminology. See if it needs adjustment. https://sourceforge.net/p/tei/bugs/548/
|2013-05-31
|
|-
|KH
|look for <note> near <egXML>, see which are just URL, change them to citations. KH will update tcw20. https://sourceforge.net/p/tei/bugs/527/
|2013-05-31
|
|-
|KH
| to complete the ticket and close. https://sourceforge.net/p/tei/bugs/288/
|2013-05-17
|
|-
|LB
|to liaise with Mr Schmidt re audio and video ODD.
|2013-05-31
|Discussion has been active and work is progressing on the google doc : some FRs will be appearing shortly
|-
|LB
|to implement ticket fr 437 https://sourceforge.net/p/tei/feature-requests/437/
|2013-05-31
|done
|-
|LB
|specification and estimated cost for OmegaT
|2013-05-31
|"quick hack" has been done (by Frederic Glorieux) to enable testing but it's not clear how much extra work would be needed to make this usable
|-
|LB
|will request examples of use of @corresp on TEI-L to investigate looser uses
|2013-05-31
|done 2013-06-17
|-
|LB
|look into this and will clarify the note in element spec for publicationStmt to no longer imply that order of publisher, place of publication, etc. is mandatory if you use <p> inside of <publicationStmt>.
|2013-05-31
|Done
|-
|LB
|Draft a message to TEI-L asking people to encode just a few samples by emailing back to TEI-L as a interim measure.
|2013-05-31
|Dunno what this is about. divliminal maybe?
|-
|LB and MH
|Suggest idea of breaking up the chapters, <divs> into files with FlorenceC, report back on desirability or lack thereof. MH: suggests that there would be Canadian contributors to a French translation if that gets off the ground. MH to liaise or introduce them to FlorenceC
|2013-04-30
|FC has no opinion on the subject of breaking chapters but work is in hand; meanwhile I have received rough Fr translations of 4 or 5 other chapters from Henri Hudrisier. Not sure where to go with these.
|-
|LB/PS/KH/MH (Div.liminal working group)
|to build the survey application for community markup method.
|2013-08-31
|
|-
|MH
|to implement https://sourceforge.net/p/tei/feature-requests/446/
|2013-05-31
|Done by rev 11882.
|-
|MH
|to contact JM and resolve the ticket https://sourceforge.net/p/tei/feature-requests/402/ one way or the other.
|2013-05-17
|Done in rev 12023.
|-
|MH
|to implement a draft of a new combined TOC and allow Council to comment https://sourceforge.net/p/tei/feature-requests/421/
|2013-05-31
|In progress. Pilot page created, waiting for feedback from Council.
|-
|MH
|to come up with a very concrete set of use cases for groups of elements and make very specific arguments for their needing @resp. https://sourceforge.net/p/tei/feature-requests/443/
|2013-05-17
|
|-
|MH
|to carry the remaining issues forward with Lou and Laurent to help as needed. https://sourceforge.net/p/tei/bugs/515/
|2013-05-31
|
|-
|MH
|to remove @scheme from <rendition> and replace it with the class; also it will then pick up the new @schemeVersion. https://sourceforge.net/p/tei/bugs/539/
|2013-05-31
|Done by rev 11880.
|-
|MH
|investigate where we say these kinds of things and find a way to implement in XSLT, insert it into the make file so that it generates a <div> in a file, and XInclude that file into the first Guidelines chapter. https://sourceforge.net/p/tei/bugs/512/
|2013-07-31
|Done in various revs by 2013-04-26, and documented in http://www.tei-c.org/Activities/Council/Working/tcw20.xml#body.1_div.3. Ticket closed 2013-05-15.
|-
|MH
|Change our practice in the use of list/@type to @rend in the Guidelines (for values of "simple", "ordered" and "bulleted"). https://sourceforge.net/p/tei/bugs/460/
|2013-04-30
|Done in various revs, including work by SB on Stylesheets.
|-
|MH
|Create a proposal for new recommendations regarding the use of list/@type and list/@rend. https://sourceforge.net/p/tei/bugs/460/
|2013-04-30
|Done 2013-04-23 (on the ticket)
|-
|MH
|Summarize to tei-council mailing list the text-directionality proposals and share the slides.
|2013-04-30
|Done 2013-04-25
|-
|PS
|make new example for the <listOrg> section ND.html#NDORG. Add another example to the element spec for <listOrg> that refers to more typical listorgs. https://sourceforge.net/p/tei/bugs/558/
|2013-05-17
|
|-
|PS
|Select ~6-10 samples for div.liminal which evince the confusions we want help with.
|2013-05-17
|
|-
|RW
|to add proposed wording on <substJoin> to guidelines (and look for photograph of MS). https://sourceforge.net/p/tei/feature-requests/448/ (update to text is already done; remains to be seen whether the image can be found)
|2013-05-17
|DONE
|-
|RW
|Fix https://sourceforge.net/p/tei/bugs/557/
|2013-04-30
|DONE at revision 11890
|-
|RW and BB
|to categorize the table of attributes without examples by adding a column with priorities of high, medium and low.
|2013-05-31
|
|-
|SB
|send KH details about TEI-PB list [done 2013-04-21]
|2013-04-30
|DONE
|-
|SB
|to improve the elementSpec desc and add one or more examples. https://sourceforge.net/p/tei/feature-requests/443/
|2013-05-31
|done, @ rev 12280
|-
|SB
|create @validUntil as a class and write Schematron checks for deprecations.
|2013-05-17
|Mostly done — see post to Council list “new validUntil=” of 2013-05-16 15:27
|-
|SB
|to rename the Specs-Unused directory to Defunct, and move the SH file into it.
|2013-05-17
|done
|-
|SB
|to implement the current wording suggested above (See Minutes), as an interim measure. https://sourceforge.net/p/tei/bugs/543/
|2013-05-31
|done, @ rev 12283
|-
|SB
|make <ptr>, <ref> consistent in component parts of <biblStruct>
|2013-05-31
|LB and SB completed this at the face-to-face meeting on 04-12
|-
|SB
|remove our own dis-recommended use of <idno> in the bibliography
|2013-05-31
|
|-
|SB
|to implement https://sourceforge.net/p/tei/bugs/527/
|2013-05-31
|
|-
|SB
|add new tickets for the data.enumerated and valItem/@ident needing to be data.word not rng:text and xs:NCname, respectively.
|2013-05-31
|
|-
|SB
|post @rend, @rendition, @style class FR
|2013-04-30
|
|-
|SB and EM
|specification and estimated cost for oxygen front end for ODD.
|2013-05-31
|
|-
|SR
|to continue work on separating the Stylesheets from the guidelines into separate projects and solve problems with the Guidelines build process as a consumer of these. Any separation should be concentrating on making the latter more amenable to community development, reporting on back to Council.
|2013-05-17
|
|-
|SR
|to move the prose re <equiv/> from the core chapter into the tagdocs chapter, and tidy up. https://sourceforge.net/p/tei/bugs/516/
|2013-05-31
|DONE
|-
|SR
|to rewrite the paragraph again, to address other comments on the ticket. https://sourceforge.net/p/tei/bugs/549/
|2013-05-31
|DONE
|-
|SR
|rewrite the paragraph https://sourceforge.net/p/tei/bugs/550/
|2013-05-31
|DONE
|-
|SR
|when he gets the answer, he'll fix it, and definitive response will be sent to Jens. https://sourceforge.net/p/tei/bugs/560/
|2013-04-30
|DONE
|-
|SR
|Circulate ODD-related development papers to Council for comment
|2013-05-31
|DONE
|-
|SR and JC
|to investigate dates for next Council meeting, and set up a Doodle Poll.
|2013-05-31
|
|}
[[Category:Council]]

Council actions 2013-04

2013-06-20T11:25:22Z

GabrielBodard: several GB tasks "done"

A list of actions, those responsible, and what has been done about them
from Providence, Rhode Island, 2013-04-11 to 2013-04-13 face to face
meeting of TEI Technical Council
{|class="wikitable sortable"
|'''Who'''
|'''What'''
|'''Suggested Deadline'''
|'''Result (What Was Done)'''
|-
|All of Council
|read and comment on the document (even if it's "this bit doesn't make sense to me"). http://goo.gl/AwPs6
|2013-05-17
|
|-
|EM
|to clarify the description on elementSpec on biblScope, citedRange and locus to clarify the use of @from and @to. https://sourceforge.net/p/tei/feature-requests/389/
|2013-06-07
|
|-
|EM and SB
|to take over from KH and get something from the phys bibl group, and/or encourage the generation of cheatsheets for encoding physical bibliography to go on the wiki. [— addendum, 2013-04-14 by Syd: I believe this action was on EM and SB (or perhaps EM, LB, SB); in any case, I have already spoken to Richard Noble who is not only on board but eager. —]
|2013-05-31
|
|-
|GB
|to add examples of schematron constrains on contents of <app> as the (Green) ticket says.
|2013-05-31
|
|-
|GB
|to re-read the section and rephrase/rewrite if necessary. https://sourceforge.net/p/tei/bugs/552/
|2013-05-31
|
|-
|GB
|to close the ticket with explanation, and possibly revise the text to clarify. https://sourceforge.net/p/tei/bugs/553/
|2013-04-30
| DONE
|-
|GB
|Close https://sourceforge.net/p/tei/bugs/405/ if fully incorporated into HC's proposal
|2013-04-30
| Assigned to HC
|-
|GB
|look at other suggested standards recording s<nowiki/>ex, gender, and gender identity for inclusion in the notes. https://sourceforge.net/p/tei/feature-requests/425/
|2013-04-30
| DONE
|-
|GB
|Implement https://sourceforge.net/p/tei/feature-requests/425/ changing data.s<nowiki/>ex to be datatype data.word, providing changed Guidelines prose and notes to other standards.
|2013-04-30
| DONE
|-
|GB
|to propose a more effective wording incorporating all the nuances. https//sourceforge.net/p/tei/bugs/543/
|2013-05-31
|
|-
|HC
|to change values in @unit to singular, spelled-out forms, add column, and update Guidelines examples and text for consistency with the new values. Leave @type alone because it's deprecated. https://sourceforge.net/p/tei/feature-requests/429/
|2013-05-17
|
|-
|HC
|Nudge NH, SB, and PB for input.
|2013-05-31
|
|-
|HC and SB
|specification and estimated cost for Xpointer resolver
|2013-05-31
|
|-
|HC and SR
|to test the use of @xml:space to solve this specific problem, and to see whether that's the correct solution in the long term. DONE; https://sourceforge.net/p/tei/bugs/544/
|2013-04-30
|DONE
|-
|JC
|to implement https://sourceforge.net/p/tei/feature-requests/449/ add <am> to att.typed.
|2013-04-30
|DONE at revision 12263
|-
|JC
|to close ticket https://sourceforge.net/p/tei/feature-requests/438/ as won't-fix.
|2013-04-30
|DONE
|-
|JC
|to put a copy of the SF XML dump in the Vault.
|2013-04-30
|PENDING
|-
|JC
|to talk to DavidS and ShayneB to find out if we'd be allowed to dump the wiki db, make changes, and re-upload. For the OpenCMS we could do it manually.
|2013-04-30
|DONE (investigating)
|-
|JC
|to email sourceforge and find out if we can turn this off or modify markdown setup and investigate the implications/options.
|2013-04-30
|Investigating options.
|-
|JC
|https://sourceforge.net/p/tei/bugs/504/ implement (already done.) Close Ticket.
|2013-04-30
|DONE (Then revised slightly subsequently)
|-
|JC
|to investigate the Allura system if possible to make the meanings of the (priority) numbers explicit.
|2013-04-30
|DONE
|-
|JC
|to fix this (change "seven" to "four"). https://sourceforge.net/p/tei/bugs/555/
|2013-04-30
|LB Fixed before I had a chance to.
|-
|JC
|get back in touch with SIG conveners to encourage them to become active.
|2013-05-31
|DONE
|-
|JC
|Inform CMC SIG of their acceptance.
|2013-04-30
|DONE
|-
|JC
|Decide on deadlines for actions, but add them to the wiki not official minutes.
|2013-04-22
|DONE!
|-
|JC
|Schedule next teleconference.
|2013-05-17
|PENDING
|-
|JC
|to prod PB on all tickets assigned to him.
|2013-05-31
|PENDING
|-
|JC
|Ensure minutes are tidied up, posted online, summarised and that summary posted to TEI-L.
|2013-04-30
|DONE
|-
|JC and LB
|specification and estimated cost for new web Roma, etc.
|2013-05-31
|PENDING
|-
|JC and SB
|to encourage Piotr to get some people into a room in Rome to discuss this(?). SB will attend to push the more generic viewpoint.
|2013-05-31
|PENDING
|-
|KH
|to email Council to solicit volunteers for TEI Google work, and provide a link to the samples again.
|2013-04-30
|DONE
|-
|KH
|to go through recent soft and hard deprecations and decide whether they're correct (hard) or not, to remove @status and add @validUntil attribute.
|2013-05-31
|[[Practices_no_longer_recommended_or_now_deprecated|Plan of action with questions for others]]
|-
|KH
|to address the original issue at his leisure. https://sourceforge.net/p/tei/bugs/496/
|2013-05-31
|
|-
|KH
|to close ticket wontfix. https://sourceforge.net/p/tei/bugs/493/
|2013-04-30
|DONE
|-
|KH
|to implement the wording changes. https://sourceforge.net/p/tei/bugs/541/
|2013-05-31
|
|-
|KH
|change <idno> to <ref> or <pointer> as appropriate. The criterion to apply is whether the URL in question is an identifier or a link.
|2013-05-31
|
|-
|KH
|to add text to tcw24. Will look at how things are written in the introductory section about terminology. See if it needs adjustment. https://sourceforge.net/p/tei/bugs/548/
|2013-05-31
|
|-
|KH
|look for <note> near <egXML>, see which are just URL, change them to citations. KH will update tcw20. https://sourceforge.net/p/tei/bugs/527/
|2013-05-31
|
|-
|KH
| to complete the ticket and close. https://sourceforge.net/p/tei/bugs/288/
|2013-05-17
|
|-
|LB
|to liaise with Mr Schmidt re audio and video ODD.
|2013-05-31
|Discussion has been active and work is progressing on the google doc : some FRs will be appearing shortly
|-
|LB
|to implement ticket fr 437 https://sourceforge.net/p/tei/feature-requests/437/
|2013-05-31
|done
|-
|LB
|specification and estimated cost for OmegaT
|2013-05-31
|"quick hack" has been done (by Frederic Glorieux) to enable testing but it's not clear how much extra work would be needed to make this usable
|-
|LB
|will request examples of use of @corresp on TEI-L to investigate looser uses
|2013-05-31
|done 2013-06-17
|-
|LB
|look into this and will clarify the note in element spec for publicationStmt to no longer imply that order of publisher, place of publication, etc. is mandatory if you use <p> inside of <publicationStmt>.
|2013-05-31
|Done
|-
|LB
|Draft a message to TEI-L asking people to encode just a few samples by emailing back to TEI-L as a interim measure.
|2013-05-31
|Dunno what this is about. divliminal maybe?
|-
|LB and MH
|Suggest idea of breaking up the chapters, <divs> into files with FlorenceC, report back on desirability or lack thereof. MH: suggests that there would be Canadian contributors to a French translation if that gets off the ground. MH to liaise or introduce them to FlorenceC
|2013-04-30
|FC has no opinion on the subject of breaking chapters but work is in hand; meanwhile I have received rough Fr translations of 4 or 5 other chapters from Henri Hudrisier. Not sure where to go with these.
|-
|LB/PS/KH/MH (Div.liminal working group)
|to build the survey application for community markup method.
|2013-08-31
|
|-
|MH
|to implement https://sourceforge.net/p/tei/feature-requests/446/
|2013-05-31
|Done by rev 11882.
|-
|MH
|to contact JM and resolve the ticket https://sourceforge.net/p/tei/feature-requests/402/ one way or the other.
|2013-05-17
|Done in rev 12023.
|-
|MH
|to implement a draft of a new combined TOC and allow Council to comment https://sourceforge.net/p/tei/feature-requests/421/
|2013-05-31
|In progress. Pilot page created, waiting for feedback from Council.
|-
|MH
|to come up with a very concrete set of use cases for groups of elements and make very specific arguments for their needing @resp. https://sourceforge.net/p/tei/feature-requests/443/
|2013-05-17
|
|-
|MH
|to carry the remaining issues forward with Lou and Laurent to help as needed. https://sourceforge.net/p/tei/bugs/515/
|2013-05-31
|
|-
|MH
|to remove @scheme from <rendition> and replace it with the class; also it will then pick up the new @schemeVersion. https://sourceforge.net/p/tei/bugs/539/
|2013-05-31
|Done by rev 11880.
|-
|MH
|investigate where we say these kinds of things and find a way to implement in XSLT, insert it into the make file so that it generates a <div> in a file, and XInclude that file into the first Guidelines chapter. https://sourceforge.net/p/tei/bugs/512/
|2013-07-31
|Done in various revs by 2013-04-26, and documented in http://www.tei-c.org/Activities/Council/Working/tcw20.xml#body.1_div.3. Ticket closed 2013-05-15.
|-
|MH
|Change our practice in the use of list/@type to @rend in the Guidelines (for values of "simple", "ordered" and "bulleted"). https://sourceforge.net/p/tei/bugs/460/
|2013-04-30
|Done in various revs, including work by SB on Stylesheets.
|-
|MH
|Create a proposal for new recommendations regarding the use of list/@type and list/@rend. https://sourceforge.net/p/tei/bugs/460/
|2013-04-30
|Done 2013-04-23 (on the ticket)
|-
|MH
|Summarize to tei-council mailing list the text-directionality proposals and share the slides.
|2013-04-30
|Done 2013-04-25
|-
|PS
|make new example for the <listOrg> section ND.html#NDORG. Add another example to the element spec for <listOrg> that refers to more typical listorgs. https://sourceforge.net/p/tei/bugs/558/
|2013-05-17
|
|-
|PS
|Select ~6-10 samples for div.liminal which evince the confusions we want help with.
|2013-05-17
|
|-
|RW
|to add proposed wording on <substJoin> to guidelines (and look for photograph of MS). https://sourceforge.net/p/tei/feature-requests/448/ (update to text is already done; remains to be seen whether the image can be found)
|2013-05-17
|DONE
|-
|RW
|Fix https://sourceforge.net/p/tei/bugs/557/
|2013-04-30
|DONE at revision 11890
|-
|RW and BB
|to categorize the table of attributes without examples by adding a column with priorities of high, medium and low.
|2013-05-31
|
|-
|SB
|send KH details about TEI-PB list [done 2013-04-21]
|2013-04-30
|DONE
|-
|SB
|to improve the elementSpec desc and add one or more examples. https://sourceforge.net/p/tei/feature-requests/443/
|2013-05-31
|done, @ rev 12280
|-
|SB
|create @validUntil as a class and write Schematron checks for deprecations.
|2013-05-17
|Mostly done — see post to Council list “new validUntil=” of 2013-05-16 15:27
|-
|SB
|to rename the Specs-Unused directory to Defunct, and move the SH file into it.
|2013-05-17
|done
|-
|SB
|to implement the current wording suggested above (See Minutes), as an interim measure. https://sourceforge.net/p/tei/bugs/543/
|2013-05-31
|done, @ rev 12283
|-
|SB
|make <ptr>, <ref> consistent in component parts of <biblStruct>
|2013-05-31
|LB and SB completed this at the face-to-face meeting on 04-12
|-
|SB
|remove our own dis-recommended use of <idno> in the bibliography
|2013-05-31
|
|-
|SB
|to implement https://sourceforge.net/p/tei/bugs/527/
|2013-05-31
|
|-
|SB
|add new tickets for the data.enumerated and valItem/@ident needing to be data.word not rng:text and xs:NCname, respectively.
|2013-05-31
|
|-
|SB
|post @rend, @rendition, @style class FR
|2013-04-30
|
|-
|SB and EM
|specification and estimated cost for oxygen front end for ODD.
|2013-05-31
|
|-
|SR
|to continue work on separating the Stylesheets from the guidelines into separate projects and solve problems with the Guidelines build process as a consumer of these. Any separation should be concentrating on making the latter more amenable to community development, reporting on back to Council.
|2013-05-17
|
|-
|SR
|to move the prose re <equiv/> from the core chapter into the tagdocs chapter, and tidy up. https://sourceforge.net/p/tei/bugs/516/
|2013-05-31
|DONE
|-
|SR
|to rewrite the paragraph again, to address other comments on the ticket. https://sourceforge.net/p/tei/bugs/549/
|2013-05-31
|DONE
|-
|SR
|rewrite the paragraph https://sourceforge.net/p/tei/bugs/550/
|2013-05-31
|DONE
|-
|SR
|when he gets the answer, he'll fix it, and definitive response will be sent to Jens. https://sourceforge.net/p/tei/bugs/560/
|2013-04-30
|DONE
|-
|SR
|Circulate ODD-related development papers to Council for comment
|2013-05-31
|DONE
|-
|SR and JC
|to investigate dates for next Council meeting, and set up a Doodle Poll.
|2013-05-31
|
|}
[[Category:Council]]

I18n checklist

2013-05-13T10:57:12Z

GabrielBodard:

==Checklist of tasks for Internationalization==

===Types of i18n===

====Provision of examples in languages other than English====

...

====Guidelines prose translation====

...

====Guidelines specs/glosses translation====

...

====Element names translation/customization====

...

===Technical tasks===

...

[[category:Council]]
[[category:Community]]

I18n checklist

2013-05-13T10:44:33Z

GabrielBodard: stub

==Checklist of tasks for Internationalization==

===Types of i18n===

====Guidelines prose translation====

...

====Guidelines specs/glosses translation====

...

====Element names translation/customization====

...

===Technical tasks===

...

[[category:Council]]
[[category:Community]]

Practices no longer recommended or now deprecated

2013-04-19T11:01:38Z

GabrielBodard: /* "Deprecated" */ (glossing "no sooner than")

== Policy ==

At its April 2013 face-to-face meeting in Providence, the [[Council|Technical Council]] agreed to the following policy for handling practices that are "no longer recommended" or "deprecated".

=== "No longer recommended" ===

While the TEI Guidelines often offer more than one way of encoding a particular phenomenon, at times the Council agrees to identify a preferred method without making any definite plans to remove the non-preferred way from the Guidelines. In this case:

* The <remarks> element is used in the spec to indicate the preferred practice.
* The prose in one or more chapters is revised to indicate this preferred practice. Examples showing the non-preferred practice are maintained but preferably only in the section of the Guidelines where that element or attribute is discussed, not in passing elsewhere.

We will not add the "no longer recommended" practice to [[P6-dev]].

=== "Deprecated" ===

According to the [[TEI-Council-FAQ#What_is_the_.22Birnbaum_doctrine.22.3F|Birnbaum doctrine]], the Council has made the serious decision to break backwards compatibility by changing the content model of an element or class to remove an element or attribute, or to remove an element or attribute entirely from the Guidelines. In this case:

* The appropriate spec is modified to add @validUntil on the appropriate <elementSpec>, <classRef>, or <attDef> elements. The value of @validUntil shall be no sooner than two years from the date of the change (thus guaranteeing '''at least''' one year from the release in which the deprecation is announced to the change in which the feature disappears).
* A Schematron warning is added to the spec.
* Any examples of the deprecated practice are removed from the Guidelines, and any prose recommending them is reworded as appropriate.
* We will try to remember to include a mention of the deprecation in the release notes created for the following release.

After the date specified in @validUntil:

* The element or attribute is actually removed from the spec.

== To do ==

=== 1. Decide remaining questions ===

A. Since we are no longer using @status='deprecated', should we remove it as a legal value of this attribute in att.identified? It's odd to include it here if we won't be using it. Note that we only added this value recently, when implementing [http://purl.org/tei/fr/1933481 FR 1933481].

B. For deprecations (things we plan to remove), will we:
# list them on a wiki page (this one?)
# [http://purl.org/tei/bug/3435326 create a new tracker item for each]
# announce each on TEI-L
# include them in release notes

or a combination of these?

: I suggest we not create tracker items and therefore simply close [http://purl.org/tei/bug/3435326 bug 3435326]. If Council has already decided to deprecate, we don't need any feedback, and we can use @validUntil to track planned deprecations. ([[User:Kshawkin|Kshawkin]] 23:10, 18 April 2013 (EDT))

=== 2. Create a new tcw with the policy, plus answers to the remaining questions, for future reference ===

Once Council reviews that the intent from the Providence meeting has been correctly represented, KH will create this document (as originally requested in Oxford).

=== 3. Modify release building procedure ===

KH will add a step to tcw22 to say to grep the specs looking for @validUntil. For any values that are dates that have passed, you should go ahead and carry out the deprecation.

=== 4. Add handling of @validUntil to stylesheets for generating Guidelines ===

SR will:
* add code to stylesheets to display "Deprecated: valid until YYYY-MM-DD" in specs when @validUntil is present.
* add rendering of @validUntil in specLists. (Currently @status does not display in specLists!)

For now leave handling of @status in place in case a release is made before all specs are updated.

=== 5. Recent "deprecation" practices to be reviewed ===

For all of the following tickets ...

* [http://purl.org/tei/fr/3520653 deprecate <relationGrp>]
* [http://purl.org/tei/fr/3266021 dictionary entries with a single <sense>]
* [http://purl.org/tei/fr/3437509 Use @ref instead of @key]
* [http://purl.org/tei/fr/3286136 <altIdentifier> is deprecated within <msPart>]
* [http://purl.org/tei/fr/3565878 where to put <idno> within <biblStruct>]
* [http://purl.org/tei/bugs/3590818 Deprecation of "magic token" attributes]
* [http://purl.org/tei/bug/3376456 deprecate use of gram except as a child of gramGrp]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-join.html @targets deprecated on <join>] -- This was implemented at revisions [http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/join.xml?r1=8457&r2=8763 8763] and [http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/join.xml?r1=8763&r2=8808 8808] (but can't find a mention in any minutes, a ticket, or discussion of this on tei-council).
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quotation.html @form deprecated on <quotation>] (Note: deprecation will be noted in the Guidelines when [http://purl.org/TEI/FR/3556778 FR 3556778] is implemented.)
* [http://purl.org/TEI/FR/3570037 add @unit to <biblScope>, and soft-deprecate @type]

... we need to make sure they've been handled according to the above policy.

KH will do the following:

* If the spec has a @status, remove it. If appropriate according to the above policy, add a @validUntil with a value corresponding to two years after the date that the @status was added.
* If the spec has no @status but it should have a @validUntil according to the above policy, add @validUntil with a value that is two years from the current date.
* If it's a "no longer recommended" practice, make sure there's appropriate text in <remarks>.
* For deprecations, reopen the ticket if necessary and assign to SB with a note to add a Schematron warning.

SB will do the following:

* Add a Schematron warning for the "no longer recommended" practices.

=== 6. Remove @status='deprecated' in stylesheets ===

SR will change the stylesheets to remove display of "(deprecated)" for @status='deprecated' since this is no longer needed.

[[Category:Council]]

Practices no longer recommended or now deprecated

2013-04-19T11:00:11Z

GabrielBodard: /* "Deprecated" */

== Policy ==

At its April 2013 face-to-face meeting in Providence, the [[Council|Technical Council]] agreed to the following policy for handling practices that are "no longer recommended" or "deprecated".

=== "No longer recommended" ===

While the TEI Guidelines often offer more than one way of encoding a particular phenomenon, at times the Council agrees to identify a preferred method without making any definite plans to remove the non-preferred way from the Guidelines. In this case:

* The <remarks> element is used in the spec to indicate the preferred practice.
* The prose in one or more chapters is revised to indicate this preferred practice. Examples showing the non-preferred practice are maintained but preferably only in the section of the Guidelines where that element or attribute is discussed, not in passing elsewhere.

We will not add the "no longer recommended" practice to [[P6-dev]].

=== "Deprecated" ===

According to the [[TEI-Council-FAQ#What_is_the_.22Birnbaum_doctrine.22.3F|Birnbaum doctrine]], the Council has made the serious decision to break backwards compatibility by changing the content model of an element or class to remove an element or attribute, or to remove an element or attribute entirely from the Guidelines. In this case:

* The appropriate spec is modified to add @validUntil on the appropriate <elementSpec>, <classRef>, or <attDef> elements. The value of @validUntil shall be no sooner than two years from the date of the change.
* A Schematron warning is added to the spec.
* Any examples of the deprecated practice are removed from the Guidelines, and any prose recommending them is reworded as appropriate.
* We will try to remember to include a mention of the deprecation in the release notes created for the following release.

After the date specified in @validUntil:

* The element or attribute is actually removed from the spec.

== To do ==

=== 1. Decide remaining questions ===

A. Since we are no longer using @status='deprecated', should we remove it as a legal value of this attribute in att.identified? It's odd to include it here if we won't be using it. Note that we only added this value recently, when implementing [http://purl.org/tei/fr/1933481 FR 1933481].

B. For deprecations (things we plan to remove), will we:
# list them on a wiki page (this one?)
# [http://purl.org/tei/bug/3435326 create a new tracker item for each]
# announce each on TEI-L
# include them in release notes

or a combination of these?

: I suggest we not create tracker items and therefore simply close [http://purl.org/tei/bug/3435326 bug 3435326]. If Council has already decided to deprecate, we don't need any feedback, and we can use @validUntil to track planned deprecations. ([[User:Kshawkin|Kshawkin]] 23:10, 18 April 2013 (EDT))

=== 2. Create a new tcw with the policy, plus answers to the remaining questions, for future reference ===

Once Council reviews that the intent from the Providence meeting has been correctly represented, KH will create this document (as originally requested in Oxford).

=== 3. Modify release building procedure ===

KH will add a step to tcw22 to say to grep the specs looking for @validUntil. For any values that are dates that have passed, you should go ahead and carry out the deprecation.

=== 4. Add handling of @validUntil to stylesheets for generating Guidelines ===

SR will:
* add code to stylesheets to display "Deprecated: valid until YYYY-MM-DD" in specs when @validUntil is present.
* add rendering of @validUntil in specLists. (Currently @status does not display in specLists!)

For now leave handling of @status in place in case a release is made before all specs are updated.

=== 5. Recent "deprecation" practices to be reviewed ===

For all of the following tickets ...

* [http://purl.org/tei/fr/3520653 deprecate <relationGrp>]
* [http://purl.org/tei/fr/3266021 dictionary entries with a single <sense>]
* [http://purl.org/tei/fr/3437509 Use @ref instead of @key]
* [http://purl.org/tei/fr/3286136 <altIdentifier> is deprecated within <msPart>]
* [http://purl.org/tei/fr/3565878 where to put <idno> within <biblStruct>]
* [http://purl.org/tei/bugs/3590818 Deprecation of "magic token" attributes]
* [http://purl.org/tei/bug/3376456 deprecate use of gram except as a child of gramGrp]
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-join.html @targets deprecated on <join>] -- This was implemented at revisions [http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/join.xml?r1=8457&r2=8763 8763] and [http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/join.xml?r1=8763&r2=8808 8808] (but can't find a mention in any minutes, a ticket, or discussion of this on tei-council).
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-quotation.html @form deprecated on <quotation>] (Note: deprecation will be noted in the Guidelines when [http://purl.org/TEI/FR/3556778 FR 3556778] is implemented.)
* [http://purl.org/TEI/FR/3570037 add @unit to <biblScope>, and soft-deprecate @type]

... we need to make sure they've been handled according to the above policy.

KH will do the following:

* If the spec has a @status, remove it. If appropriate according to the above policy, add a @validUntil with a value corresponding to two years after the date that the @status was added.
* If the spec has no @status but it should have a @validUntil according to the above policy, add @validUntil with a value that is two years from the current date.
* If it's a "no longer recommended" practice, make sure there's appropriate text in <remarks>.
* For deprecations, reopen the ticket if necessary and assign to SB with a note to add a Schematron warning.

SB will do the following:

* Add a Schematron warning for the "no longer recommended" practices.

=== 6. Remove @status='deprecated' in stylesheets ===

SR will change the stylesheets to remove display of "(deprecated)" for @status='deprecated' since this is no longer needed.

[[Category:Council]]

Tutorials

2013-01-30T12:37:15Z

GabrielBodard: added EpiDoc cheatsheet

This page is intended to be a collection point for TEI, TEI-related tutorials, blog posts, or other teaching materials. There are also some on the TEI-C website at http://www.tei-c.org/Support/Learn/tutorials.xml and some of the material here is duplicated there.

* Kevin Hawkins, [http://www.ultraslavonic.info/intro-to-xml/ Introduction to XML for Text]: This is meant to be a starting point, to be read even before [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SG.html A Gentle Introduction to XML].
* [http://www.teibyexample.org/ TEI by Example]. A step-by-step tutorial guide to the use of TEI, sponsored by The Centre for Scholarly Editing and Document Studies (CTB) of the Royal Academy of Dutch Language and Literature, the Centre for Computing in the Humanities (CCH) of King's College London, and the Department of Information Studies of University College London.
* [http://digital.humanities.ox.ac.uk/dhoxss/2012/workshops.html#TEI An Introduction to XML and the Text Encoding Initiative] a 5-day course from the [http://digital.humanities.ox.ac.uk/dhoxss/ Digital.Humanities@Oxford Summer School 2012].
* [http://epidoc.svn.sourceforge.net/viewvc/epidoc/trunk/guidelines/msword/cheatsheet.doc EpiDoc cheatsheet] (doc) (part of [http://wiki.digitalclassicist.org/EpiDoc_Summer_School EpiDoc Summer School] teaching materials online)
* Please add more!

Oxford2012-Actions

2012-10-22T13:35:28Z

GabrielBodard:

A list of actions, those responsible, and what has been done about them from Oxford 2012 face to face meeting of TEI Technical Council

{|class="wikitable"
|Who
|What
|Result
|-
|ALL Council
|Discuss http://purl.org/TEI/FR/3416130 further.
|
|-
|ALL
|continue to complete assigned actions.
|
|-
|ALL
|identify anything we disagree with in their output.
|
|-
|All Council
|Council members (e.g. PB, LB and GB) will add comments directly to HC’s original proposal by the end of October, and then we will be happy to receive any further drafts of it.
|
|-
|All Council
|http://purl.org/TEI/BUGS/3520704:.
|
|-
|EP
|to find an example to incorporate into the Guidelines demonstrating LB's encoding solution for the issue raised in http://purl.org/TEI/FR/3523225.
|
|-
|GB
|add msDesc to att.typed per http://purl.org/TEI/FR/3526114.
|DONE
|-
|GB
|create a proposal for Council to consider based on http://purl.org/TEI/FR/3291540.
|
|-
|GB
|implement proposal a) in http://purl.org/TEI/Bug/3496949
|
|-
|GB
|incorporate http://purl.org/TEI/BUGS/3523082 into the SOM group discussion of TEI Pointers.
|
|-
|GB
|remove constraint and clarify Guidelines text per http://purl.org/TEI/Bug/3496958.
|Done, but needs examples
|-
|GB
|submit a more detailed proposal for http://purl.org/TEI/FR/3291540.
|
|-
|GB
|to submit a ticket requesting clarification in the prose of the Guidelines on the use of from on other elements such as locus and biblScope. Close the originating ticket http://purl.org/TEI/FR/3518932 as it stands as won’t fix.
|
|-
|JC and LB
|Resolved: JC and LB will produce a draft of a code bounty for a loose specification for a Roma rewrite, which will come back to Council for comments. This will include a list of preferred languages/tools, the need for a plugin API etc. Council aims to release a public call in about two to three months, with the idea that work will begin early in 2013.
|
|-
|JC and LB
|The scheme attribute should be redefined so that it need not point to a taxonomy element; it can point to an external scheme. Similarly, code should be defined as a pointer to some kind of external category or to a category element. A new ticket should be raised for this.
|
|-
|JC
|Contact stakeholders to remind them of upcoming TEI P4 deprecation; notify TEI-L community; Liaise with KH and David Sewell (TEI-C Webmaster) on changes to website.
|
|-
|JC
|Convert TEI ODD meeting notes and summary to TEI and put on website; Liaise with Laurent Romary and other participants about a possible publication of a summary article for Proceedings of DH 2012.
|
|-
|JC
|Council will discuss on list the precise wording of the prompt for the candidate statement; JC to initiate, and report back to nominations committee.
|
|-
|JC
|Finalize release date with PB.
|
|-
|JC
|Organize Council work for next release.||
|-
|JC
|While working on person, name etc. in another ticket, examine the parallelism between scheme, code, key and ref.
|
|-
|JC
|add more use-cases to http://purl.org/TEI/FR/3547558.
|
|-
|JC
|close http://purl.org/TEI/FR/3504690.
|
|-
|JC
|create a proposal for the changes required per http://purl.org/TEI/FR/3536363, and with reference to http://sourceforge.net/mailarchive/message.php?msg_id=29144155.
|
|-
|JC
|implement http://purl.org/TEI/BUGS/3519806.
|
|-
|JC
|implement http://purl.org/TEI/Bug/3540863.
|
|-
|JC
|produce a detailed proposal per http://purl.org/TEI/FR/3284816.
|
|-
|JC
|rend references throughout Guidelines will be clarified to note it is a sequence-indeterminate bag of space-separated tokens.
|
|-
|JC
|replace respStmt with model.respLike in editionStmt; then review monogr with the idea of simplifiying it and including model.respLike per http://purl.org/TEI/bug/3439587.
|
|-
|KH and RW
|Look at the definition of span and the explanation in 17.3 to see what needs to be done there as part of http://purl.org/tei/fr/3496494
|
|-
|KH
|Improve TEI-C Website page on customizations.
|
|-
|KH
|KH will find a place to put ODD meeting notes and summary, probably in TCW.
|
|-
|KH
|after Martin has finished updating the tutorial, synchronize the tutorial and the Guidelines by adding any essential bits from the tutorial to the guidelines (without turning the prose of the Guidelines into a tutorial), and checking for consistency between Guidelines and tutorial.
|
|-
|KH
|close http://purl.org/TEI/FR/3553304.
|
|-
|KH
|continue to liaise with physical bibliography group in producing a proposal.
|
|-
|KH
|create citedRange, allowing target to point out to a source. The full description of the cited range (e.g., volume, page, column, line) should simply be plain text inside citedRange. The content model of citedRange will be macro.phraseSeq. Change the gloss of biblScope from (scope of citation) to (scope of reference); Returning to Council as needed for implementation advice (see http://purl.org/TEI/FR/3555191). In addition, implement new ticket (http://purl.org/tei/fr/3570037): add unit to biblScope and deprecate the use of type.
|
|-
|KH
|keep up the pressure for a decision on Virginia's partnership.
|
|-
|KH
|remove experimental and restricted language from TEI Customization page. Use instead: the following are not available as DTD or XSD.
|
|-
|KH
|to carry out the work set out by KH and Laurent on the ticket (http://purl.org/TEI/bug/3547289).
|
|-
|LB / PB / MH / RW / JC
|A working group including LB, PB, MH, RW, JC will come back with a formal proposal for a standoff markup container element. See http://purl.org/TEI/FR/3561933.
|
|-
|LB / PS / KH
|Div.Liminal Working group will report back to council with rational proposals of how to deal with tops and bottoms of divs.
|
|-
|LB and KH
|work on TCW doc on deprecation, and bring it back to Council at the next FTF.
|
|-
|LB
|Add clarification of the issues raised in http://purl.org/TEI/FR/3523225 to the Guidelines (3.2.2) CO.html#COPU-2 existing discussion of hyphenation.
|
|-
|LB
|Add some prose to this chapter of the guidelines to put the idno within monogr, and/or analytic, and/or series (as it applies).
|
|-
|LB
|Ensure http://purl.org/TEI/FR/2834511 is completed.
|
|-
|LB
|In Roma, split the existing create customization from template button into two options: create customization from template and create customization from community customization, which can be opened from a list in the wiki (http://www.tei-c.org/wiki/index.php/Category:Customization) or the TEI-C Website. also remove the label experimental from those items in the drop down menu that have it.
|DONE
|-
|LB
|Normalize spelling of customization in Guidelines and Roma.
|
|-
|LB
|Propose new wording for Guidelines per http://purl.org/TEI/FR/3496494.
|
|-
|LB
|When deprecation procedure is formulated, deprecate use of gram except as a child of gramGrp per http://purl.org/TEI/Bug/3376456.
|
|-
|LB
|develop his Durand Conundrum paper into a specific set of proposals for a new content structure, so that we can then take that to the larger ODD-implementing community for work and feedback.
|
|-
|LB
|fix the TEI Guidelines bibliography so that its idnos are inside monogr; see ticket http://purl.org/TEI/FR/3565878.
|
|-
|LB
|implement Schematron rules per http://purl.org/TEI/FR/2834511.
|
|-
|LB
|implement http://purl.org/TEI/BUGS/3565137.
|
|-
|LB
|implement http://purl.org/TEI/Bug/3547934.
|DONE
|-
|LB
|implement http://purl.org/TEI/FR/3555190.
|
|-
|LB
|implement the style attribute per http://purl.org/TEI/FR/3519866.
|DONE. Test file still to be produced.
|-
|LB
|improve wording per http://purl.org/TEI/BUGS/3521714.
|DONE 2012-08-23
|-
|LB
|move cRef into a class, and give it the datatype data.text per http://purl.org/TEI/Bug/3480650.
|DONE 23/8/12
|-
|LB
|to close http://purl.org/TEI/FR/3523225 with explanation.
|
|-
|LB
|to correct the definition of g in the Guidelines: represents a glyph, or a non-standard character following issues raised in http://purl.org/TEI/FR/3523225.
|DONE 22-9-12 (rev 10855)
|-
|LB
|to find the text SR drafted, edit it, and tell KH where to put it on the website.
| SR has resent text to LB and KH
|-
|MH and JC
|implement expanded unique xml:id values in guidelines (http://purl.org/TEI/Bug/3472477).
|
|-
|MH
|Implement linking of the "Version 2.1.0" at the bottom of each HTML page to something, possibly to http://www.tei-c.org/Guidelines/P5/#previous, or better, to something which explains what version numbers mean and then links on to the above location.
|
|-
|MH
|Reject and close http://purl.org/TEI/FR/3561938 with an explanation.
|DONE 2012-10-09
|-
|MH
|The original issue of the broken link in http://purl.org/TEI/FR/3521288 must be fixed.
|Apparently already done in rev 10399 by Sebastian. Ticket closed 2012-10-10.
|-
|MH
|close http://purl.org/TEI/BUGS/3520414, and open a new ticket to deal with linking of quotations and references.
|DONE 2012-09-27
|-
|MH
|close http://purl.org/TEI/Bug/3413346 and open a cleaner ticket on the topic of deprecation of data.key.
|
|-
|MH
|consult such people as D. Anderson, F. Sasaki and M. Bingenheimer, along with the TEI-L list, to put together a group to create a recommendation for a new Guidelines section on encoding text directionality.
|
|-
|MH
|for http://purl.org/TEI/BUGS/3539329, copy definition of data.name into all four locations. On http://purl.org/TEI/FR/3511398, produce a list of candidate attribute values which might be constrained with Schematron.
|First item done 2012-10-10 in rev 10949. Second in progress.
|-
|MH
|implement http://purl.org/TEI/BUGS/3532022. (Add lg to content model of p.)
|Done in rev 10851 2012-09-20.
|-
|MH
|implement http://purl.org/TEI/Bug/3432216.
|List of priority items for translation generated and posted on the ticket 2012-10-07.
|-
|MH
|implement http://purl.org/TEI/FR/3511398.
|
|-
|MH
|implement http://purl.org/TEI/FR/3531957.
|DONE rev 10876 2012-09-27.
|-
|MH
|produce a draft for approval by Council based on http://purl.org/TEI/FR/3565152.
|Done rev 10946 2012-10-09.
|-
|MH
|proof and expand wiki documentation for oddbyexample by KH http://wiki.tei-c.org/index.php/Oddbyexample.
|
|-
|MH
|provide tech support to existing div.liminal working group (LB, KH, PS) regarding setup of eXist and eXide.
|
|-
|MH
|review the ODD tutorial on the website and update it as needed. New ticket created for this: http://purl.org/tei/bug/3570106.
|
|-
|MH
|rewrite the [http://wiki.tei-c.org/index.php/Private_URI_Schemes[Private URI Schemes]] proposal accordingly and bring this back to Council.
|Done 2012-10-11. New proposal is [http://wiki.tei-c.org/index.php/Prefix_Definition_Proposal Prefix Definition Proposal].
|-
|PB
|add link/linkGrp to place, org and event per http://purl.org/TEI/FR/3060867.
|
|-
|PB
|http://purl.org/TEI/FR/3561933 is already assigned to PB.
|
|-
|PS
|expand the Guidelines with more examples of the use of list/type, including some which use the putative style attribute; add a section to the P6 Development page to initiate discussion of future values.
|
|-
|RW and LB
|define a new element called punctuation which is a member of model.encodingDescPart and att.declarable, with prose content, and some attribute(s) defining the handling of punctuation marks. It should be repeatable.
|
|-
|RW
|Check that all action called for on http://purl.org/TEI/FR/3554294 has been carried out, and close the ticket.
|
|-
|SR
|Implement KH's recommendations from 2012-04-16 in http://purl.org/TEI/Bug/3440771.
|made some changes to prose, got GB to supply multi-loc example, moved geoDecl decl to header chapter
|-
|SR
|SR will continue his work to pare down the repository and remove non-Guidelines-related material.
|Am doing
|-
|SR
|Test Roma to see what it does with a namespace prefix on ident; clarify the examples in Chapter 23; create an attribute class to hold ns (instead of defining it separately on elementSpec and friends).
|new att class att.namespaceable defined. making exampe of namespace/ident
|-
|SR
|change the content model of signed to macro.paraContent, check for unexpected side-effects, and rationalize all current examples to a single practice and add one with list inside signed (see http://purl.org/TEI/Bug/3439980).
|DONE
|-
|SR
|give admin access to JC and MH to Oxygen TEI repository.
|DONE
|-
|SR
|reject and close http://purl.org/TEI/FR/3064757, but examine consistency of encoding in all current Schematron rules.
|DONE
|-
|SR
|review the tools, add ons, and other code currently in the TEI repository that perhaps should be removed (because they are not core to the functioning of the Guidelines).
|DONE
|-
|SR
|switch rendering system from use of entities to XInclude, if practical, per http://purl.org/TEI/FR/3547869.
|DONE

}
[[Category:Council]]

Council-ticketTriage

2012-09-20T09:26:30Z

GabrielBodard: sorting by traffic lights

These are tickets to be considered during the September 2012 Technical Council meeting in Oxford.

==Green==
There are only SIX GREEN tickets still open on 15 sep 12. I don't think
any of them needs any particular discussion at the meeting, unless the
assignee wants to decline the honour, or report progress. Here's the
list, just for completeness.

* http://purl.org/TEI/Bug/3547934 1.3.2.1 needs repair (clarification of "chunks", "components", and
related terminology)
- assigned to louburnard. Some comments on ticket. Revised wording to be drafted for mtg

* http://purl.org/TEI/Bug/3540863 Names and Dates chapter does not mention calendar -
- assigned to jcummings

* http://purl.org/TEI/Bug/3472477 AdBlock blocks 'msad' -
- assigned to martindholmes : requires action at next release to generate prefixed identifiers throughout text of GL

* http://purl.org/TEI/Bug/3432216 i18n revision due -
- assigned to mholmes

==Amber==

There are only 19 AMBER tickets as of 15/09.

Of these, I think three are actually fairly clear and just need action:
with a bit of tidying they could be green:

* http://purl.org/TEI/FR/3531957 allow a footer for a table
* http://purl.org/TEI/FR/3511398 Need to implement Schematron rules for attribute values
* http://purl.org/TEI/FR/2834511 Add more elements to att.spanning with schematron constraint

Three further tickets indicate clearly enough for drafting purposes some
places where clarifications and revisions to text of Glines are needed:

* http://purl.org/TEI/Bug/3496949 Guidelines, p. 388 - "<wit>[unattested]</wit>" (bodard)
* http://purl.org/TEI/Bug/3496958 Guidelines, p. 384 - number of <rdg> in <app> (bodard)
* http://purl.org/TEI/FR/3496494 make attributes @from and @to (as pointers) part of a class

And two more are concerned with some tweaking of current attribute
classes -- they just need some careful fiddling about, but nothing
controversial.

* http://purl.org/TEI/FR/3291540 att.editLike should not bring att.dimensions & att.ranging
* http://purl.org/TEI/FR/3284816 att.canonical for model.persTraitLike

Council probably needs to allocate time to discuss the following EIGHT
tickets, where the action proposed is controversial or may be
unnecessary. I've put them in (my perceived) descending order of priority.

* http://purl.org/TEI/Bug/3440771 Multiple <geo> tags in <location> (rahtz)
* http://purl.org/TEI/Bug/3439980 content model of <signed> (rahtz)
* http://purl.org/TEI/FR/3526114 add @type to msDesc
* http://purl.org/TEI/FR/3060867 Grouping traitlike, statelike, and eventlike elements
* http://purl.org/TEI/FR/3536363 rationalize content models of org and place (etc)
* http://purl.org/TEI/FR/3504690 floatingDiv proposal
* http://purl.org/TEI/Bug/3439587 Problems introduced by content models of bibl and imprint (kshawkin)
* http://purl.org/TEI/Bug/3555602 oddbyexample non-tei:TEI start (rahtz)

Which leaves just one ticket that seems to be concerned only with
meta-issues (how to indicate deprecation, if we wish to discuss that)

* http://purl.org/TEI/Bug/3376456 deprecate use of gram except as a child of gramGrp (kshawkin)

and two which are stuck, pending action elsewhere

* http://purl.org/TEI/FR/3423686 an <object> element
* http://purl.org/TEI/FR/3495987 members of model.respLike should be members of att.declarabl

==Red==
And finally, there are 8 RED tickets as of 15/09

Two of these have had extensive discussion and clarification and I think
should be recategorised as Amber. A both more discussion at the ftf, and
I think these could both be resolved:
* http://purl.org/TEI/FR/3519866 @rend from data.word to text
* http://purl.org/TEI/FR/3416130 Allow certainty etc. inside milestoneLike elements

Hopefully the ISO meeting on 22 Oct will give some ideas for progressing
the following two:
* http://purl.org/TEI/FR/2724997 Cater for audio/video facsimile
* http://purl.org/TEI/FR/2507305 Alignment and documentation of sound files

Unless anyone objects, I think this one can be closed
* http://purl.org/TEI/FR/3064757 XML construct encoding within Schematron

If there's anything further to be done here, it should be discussed when
we review MH's update to TCW20 about schematron

Which leaves the following three definitely red, all of which are still
in need of considerable amounts of work/discussion...

* http://purl.org/TEI/FR/3475007 New section on encoding text directionality
* http://purl.org/TEI/Bug/3480650 @cRef is a mess
* http://purl.org/TEI/Bug/3413346 Deprecation of data.key and data.word attributes

==Previously Ungrouped==
I've now reviewed all the previously ungrouped tickets (apologies again
for the delay) and made some tentative groupings of them, as indicated
below.

Where I've marked something GREEN it's because I think I know what
should be done, and it's clear, and the owner of the ticket should just
go ahead and do it unless anyone on council calls foul. I've tried to
add a comment clarifying what's to be done if it's not clear.

Where I've marked a ticket AMBER, I usually also have a clear idea of
what should be done, but am (un)comfortably aware that other views
exist. So Council needs to state firmly that it agrees with me (or of
course, conceivably, the other guy) before this ticket can move to GREEN
or (in most cases) be implemented. And of course there are some cases
where I actually have no view at all, and it's still not clear what to do.

There are also a few RED tickets, where the issue lacks clarity, or
requires lots of work before it is clear what actions are needed.

I've tried to group tickets by topic, on the assumption that we may want
to tackle some of them in breakout groups.

=== Various bibliographic matters, proposals for change===

* http://purl.org/TEI/FR/3555190 : Improve guidance and restrict usage of biblScope GREEN
* http://purl.org/TEI/FR/3553304 Add idno as child to biblFull GREEN

* http://purl.org/TEI/FR/3555191 New element <citedRange> for bibliography AMBER
* http://purl.org/TEI/FR/3513147 biblStruct for Patent citations AMBER
* http://purl.org/TEI/FR/3565878 where to put <idno> within <biblStruct>? AMBER

=== Ongoing activities for review ===

* http://purl.org/TEI/BUGS/3520704 : Most attributes lack good examples GREEN

* http://purl.org/TEI/BUGS/3557497 : New schematron constraint for datable elements AMBER

=== Suggestions for new content models/elements/classes ===

* http://purl.org/TEI/BUGS/3565137 : reconsider membership or use of model.glossLike GREEN

* http://purl.org/TEI/FR/3561933 : Encoding of Standoff annotations AMBER
* http://purl.org/TEI/BUGS/3532022 : <lg> should be allowed in <p> AMBER
* http://purl.org/TEI/BUGS/3519806 : <name> should be a member of att.datable AMBER
* http://purl.org/TEI/FR/3523791 : an addition to <timeline> to record stretches of time AMBER
* http://purl.org/TEI/FR/3518932 : Use @range instead of abusing @from on <span> AMBER
* http://purl.org/TEI/FR/3523225 : New attribute @keepHyphen AMBER
* http://purl.org/TEI/FR/3547289 : model.gramPart and <cit> AMBER

* http://purl.org/TEI/FR/3547558 : *Spec elements could have <keywords> or use @ana RED
* http://purl.org/TEI/FR/3561938 : New tag element for grouping elements RED

=== Revisions of the Guidelines documentation ===
* http://purl.org/TEI/FR/3565152 : reference application/tei+xml somewhere in the Guidelines GREEN
* http://purl.org/TEI/FR/3554294 : @xml:space GREEN
* http://purl.org/TEI/FR/3547869 : system entities vs. XInclude GREEN
* http://purl.org/TEI/BUGS/3539329 : Inconsistency in data.name GREEN (same as http://purl.org/TEI/FR/3511398)
* http://purl.org/TEI/BUGS/3520414 : Example does not conform with description in Core chapter GREEN
* http://purl.org/TEI/BUGS/3521714 : revise valList and valItem, revise ch. 22 accordingly GREEN

* http://purl.org/TEI/FR/3556778 : retaining punctuation marks in the text of a TEI document AMBER
* http://purl.org/TEI/BUGS/3515805 : confusing semantics of @ns AMBER
* http://purl.org/TEI/FR/3548625 : Extend the enumerated values for list/@type AMBER
* http://purl.org/TEI/FR/3521288 : Dead Link for http://www.ons.gov.uk/about-statistics/classif AMBER
* http://purl.org/TEI/FR/3522043 : Version numbers link to page about versions? AMBER

* http://purl.org/TEI/BUGS/3523082 : XPointer schemes may not nest, but see ch. 16 RED

[[Category:Council]]

Council

2012-08-09T14:30:51Z

GabrielBodard: /* Agenda */

The TEI Technical Council, often referred to as 'TEI Council' or 'Council' is the elected body that is responsible for maintaining and implementing the TEI Guidelines. Also see the [http://www.tei-c.org/Activities/Council/ Council section of the TEI-C website] for archived documents, and [[TEI-Council-FAQ]] for a Council FAQ. The TEI Council also uses this page to store some of its draft agendas while working them up before Face 2 Face meetings.

== Teleconference - 2012-08-09 20:00 BST ==
=== Agenda ===

* Brief Reports
** TEI Tite (KH)
** SIG reports (JC)
** Google Books (KH)
** Physical Bibliography (KH)
** ODD Meeting after DH2012 (JC)
** XPointer scheme proposal (GB)
** Face2Face Meeting: arrangements (JC)
* Replacement for SY or not? (JC)
* TEI Lite (LB)
* (more items TBD)

== F2F meeting - Ann Arbor 15-18 April 2012 ==

Turkish-American Friendship Room, Shapiro Science Library

Description : http://www.lib.umich.edu/node/22671/
Location : <location><geo>42.275832 -83.737265</geo></location>

Here is a list of [[AnnArbor2012-Actions]] to be done.

=== Agenda ===
==== Sunday 15 April 10:00-16:00 (optional) ====
Optional TEI HackFest for those arriving early (because of flights including a Saturday being cheaper) or local people who wish to attend.

Possible tasks for the day:

* From Sebastian: "I think there is some problem of ODD processing in a pending ticket which I said was doable with some concentration - was it the idea of redeclaration of attributes (i.e. datatypes) in the P5 source itself?"
* From Sebastian: "We need to reassess what is left over from EEBO/ECCO work which still needs resolving, to give a context for Monday"
* James-C: Vault-related tidying perhaps; Also have some TEI -> MARC (for Google eBooks from TEI -> ePub) XSLT to complete.
* Lou : I would like to work on accomodating some existing TEI-like schemas into proper TEI ODDs. Notably Vogeler's "Charters Encoding Initiative" dtd; other suggestions welcome. How about a proper effort to bring EAD back into the paths of righteousness? (Sebastian says: in a day?????)
* Lou : I would also like to work on some Garage case studies, of the Word -> P5 variety

'''10:00 - 12:30'ish:'''
* Hack on TEI-related development

'''12:30 - 14:30:'''
*lunch

'''14:30 - 16:00:'''
* More TEI-related hacking

'''19:00 -'''
* Supper

==== Monday 16 April 09:00 - 17:30 ====
(Tentative and flexible timetabled agenda)

'''09:00 - 10:00:'''
* TEI - Google Books
* TEI - EEBO / ECCO

'''10:00 - 12:30:'''
* TEI Bugs and FR: (Green and hopefully some amber ones)

'''12:30 - 14:30 (shorter if possible):'''
* Lunch

'''14:30 - 15:30:'''
* TEI and Schematron Tests
* TEI Exemplars (e.g. Tite)
* Best Practices for TEI in Libraries

'''15:30 - 17:30:'''
* TEI Bugs and FR: (Amber)

'''19:00-'''
Supper (optional)

==== Tuesday 17 April 09:00 - 17:30 ====

'''09:00-10:00:'''
* TEI Namespaces and Conformance
* Chapter/module fragmentation and consolidation (e.g. should things like 'dates' become a chapter of its own)
* TEI Examples

'''10:00 - 12:30:'''
* TEI Bugs and FR (Amber)

'''12:30 - 14:30:'''
* 'Open Lunch' with people from University of Michigan community interested in meeting us

'''14:30 - 15:30:'''
* TEI FR: Floating Div
* TEI ODD Meeting

'''15:30 - 17:30:'''
* TEI Bugs and FR (Amber)

'''19:00-'''
Supper (optional)

==== Wednesday 18 April 09:00 - 16:00 ====

'''09:00 - 10:00:'''
* TEI and URIs
* TEI Release Process
* TEI Outreach and Education
* Any Other Council Business

'''10:00 - 12:30:'''
* Bugs and FR (Amber / Red)

'''12:30 - 14:30 (or shorter):'''
* Lunch

'''14:30 - 16:00 (or longer?):'''
* Bugs and FR: outstanding / summary
*(early end for those who need flights)

== Teleconference - Tuesday 28 February 2012 at 18:00 GMT ==
# Brief Reports
## [[Ad-hoc_committee_on_encoding_of_bibliographic_citations|Bibliographic Citations]] (KH & MH)
## TEI Tite (KH)
## TEI and AdBlock (MH)
## Google Books (KH)
## Xpointer (GB)
## Attribute Datatypes (MH)
## Physical Bibliography (KH)
## TEI Release Process Document (MH)
## Future of ODD meeting, DH2012 (JC)
# @ref/key/cRef & Private URI Schemes (MH)
# Best Practices for TEI in Libraries (KH)
# Practical Arrangements for April Face2Face (RW)
# Agenda for the April Face2Face (JC)
# AOB

== F2F meeting - Paris 7-9 Nov. 2011 ==

Location: Inria, 23 avenue d'Italie, Paris

=== Agenda ===

==== Monday 7 - 10.00 - 17.00 ====
* organisational:
** 9:30: breakfast
** 12:30: lunch at Pizzeria Via Italia (Pizzeria Via Italia - 21, avenue d'Italie - 01 42 16 97 89)
** 15:30: coffee break
* topical
** Review of FRs / Bugs
** Genetic Work

==== Tuesday 9 - 9.00 - 17.00 ====
* organisational:
** 10:00: coffee break
** 12:30: lunch at restaurant de L'Avant-Goût (L'avant Goût - 26, rue Bobillot - 01 53 80 24 00)
** 15:30: coffee break
* topical
** FRs / Bugs
** EEBO stuff - with Brian L Pytlik Zillig
** floating objects...

==== Wednesday 10 - 9.00 - 16.00 ====
* organisational:
** 10:00: coffee break
** 12:30: lunch at restaurant de L'Avant-Goût
** 15:30: coffee break
* topical
** Wiki access restrictions
** P4 survey

** grp vs. list
** Magic tokens
** translations

** P6 discussion and visions
** community project
** core too big
** modifying attributes from a class
** revamping Roma
** Planning priorities for next year

=== Minutes/notes Paris 2011 Meeting ===

* [http://www.tei-c.org/Activities/Council/Meetings/tcm48.xml minutes in TEI]
* [[Paris 2011-11 minutes]]

== F2F meeting - Chicago 11-13 April 2010 ==

=== Agenda ===
Most of the three days will be dedicated to expediting SF tickets. In between we have the following items to consider for discussion.

* Automating guidelines production (Presentation by Sebastian, Tuesday morning)
* Presentation on editing the Guidelines (Lou cf. http://www.tei-c.org/Activities/Council/Working/tcw20.xml)
* TEI and Google: report from Martin M. and strategy
* TEI for publishing - next steps (reports from Lou (revues.org+PUC), Kevin for TEI PUB SIG?)
* deprecation, beta, etc.

* automatic generation of feeds/twitts from SF tickets (new ones; solved ones)

From the ongoing discussion, we may also want to discuss the following issues:
* usage of floatingText within other constructs: sp, quote, etc.

=== Notes ===
==== TEI and Google ====

very bare TEI with adequate but sparse functionalities for structural and linguistic annotation

MM: When we worked on the MONK project and prepared the various TEI P4 versions for linguistic annotation, it became immediately apparent that nobody had ever given any thought to the problems of tokenization that arose for the sqirrely ways of recording or not recording words that break at lines or pages. But the question "What should an annotatable text look like?" is an important question.

LR: cf. Kernkodierung in TextGrid - minimal token annotation (<w>)

SY Gate is a really good flexible framework that includes tokenisation, but only pretends to do XML: ( http://thread.gmane.org/gmane.comp.ai.gate.general/5257 )

KH: cf. http://purl.oclc.org/NET/teiinlibraries

=== Minutes ====

[http://www.tei-c.org/Activities/Council/Meetings/tcm46.xml Minutes of the Chicago meeting for reference]

== Item for further consideration ==
* Stable URIs to discrete bits of the guidelines
* [[Council FR assignments]]

== F2F meeting - Dublin 28-30 April 2010 ==

Thursday: 9:30 - 17:00; Friday: 9:30 - 15:00 (catered lunches 12:30-13:30, coffee breaks mid-morning and mid-afternoon)

=== Agenda ===
==== Thursday morning ====
* Welcome, overview of agenda
* Wrap-up from Symposium
* First SF session (see [http://www.tei-c.org/Activities/Council/Working/tcw17.html])
==== Thursday afternoon ====
* Manuscript (genetic editions)
* Second SF session
* 4 p.m.: biblStruct

==== Friday morning ====
* hyphenation
* ODD - (r)evolutions
* Third SF session
==== Friday afternoon ====
* remaining issues
* prospective

=== Topics for discussion ===
* Deprecating mechanisms
* Pointing and keying - can one absorb the other? (key?, target/targets)

=== Minutes ===

[http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml Minutes of the Dublin meeting for reference]

== Ad-hoc committee on encoding of bibliographic citations ==

[[Ad-hoc committee on encoding of bibliographic citations]]

== Telko October 2009 ==
=== Connexion details ===

Call information:

Conference Room: 1349998

Skype (free): +9900827041349998

Telephone numbers:
*Domestic*

USA USA 1-201-793-9022
Canada Canada 1-201-793-9022
Long distance costs apply
*International*

Austria Austria 0820 401 15470
Belgium Belgium 0703 57 134
France France 0826 109 071
Germany Germany 01805 00 9527
Ireland Ireland 0818 270 968
Italy Italy 848 390 177
Spain Spain 902 885 791
Switzerland Switzerland 0848 560 397
United Kingdom United Kingdom 0870 0990 931

=== Agenda ===
* SF
* reworking the generic TEI-to-HTML stylesheets
* HTML5
* valList and content
* report to TEI MM

== Face to face meeting - Lyon 1-3 April 2009 ==
=== Local organisation - programm of the seminar ===
[https://listes.cru.fr/wiki/tei-res/public/tei_council_2009_a_lyon Meeting in Lyon]
Available abstracts under: [https://listes.cru.fr/wiki/tei-res/prive/reunioncouncilavril09]

=== Draft Agenda ===
[http://www.tei-c.org/Activities/Council/Meetings/tcm40.xml Minutes of the October meeting for reference]
* Bug and features - SF
* Focussed technical discussions
** Placement of schematron constraints in ODD - Sebastian Rahtz
** Discussion of "canonical way of referencing TEI element definitions"
** Wider debate: the future of ODD
(SourceForge item 2411994) and related issue of permanent URLs for TEI
documentation - David Sewell
[http://sourceforge.net/tracker2/?func=detail&aid=2411994&group_id=106328&atid=644065 SF ID: 2411994]
** Reporting on stylesheets (SR, DOD)
*** Evolution towards XSL 2.0
**** main advantages (features) provided by a switch to 2.0
**** consequences on the TEI infrastructure; maintenance of one or two sets of stylesheets?
**** how much of this should be known by the TEI community?

* Getting started (PB)
* Projects
** TEI - ISO
* Perspective workshop on TEI for the next decade
** communities
*** role of TEI in research infrastructures (AC)
**event
*** Dagstuhl
*** ESF [http://www.esf.org/activities/exploratory-workshops.html]
* SIGs
** TEI in library SIG - TEI Tite status
** New SIG: Scientific bibliographies [http://www.tei-c.org/Activities/Council/Working/tcw16.xml]
** Report: TEI Manuscript[http://www.tei-c.org/Activities/SIG/Manuscript/mssigr03.pdf]
* Misc.
** Necessary work on www.tei-c.org (further rationalization of structure,
etc.)
** In particular, status of TEI vault
http://www.tei-c.org.uk/Vault/Vault-GL.html (LB)

http://quod.lib.umich.edu/t/tei/ (Chris Powell)

Chris Ruotolo: For now, you can find older versions of the Guidelines at http://www.tei-c.org.uk/Vault/Vault-GL.html, We are in the process of moving these archival files to the current website.

Syd:
They used to be at
http://www.tei-c.org/Vault/GL/P1/ [source only]
http://www.tei-c.org/Vault/GL/P2/ [source only]
http://www.tei-c.org/Vault/GL/P3/index.htm [source in P3X/]

But I don't know where old stuff went when we moved to the new
website. In any case, there are copies of P3 at:
http://quod.lib.umich.edu/t/tei/
http://etext.virginia.edu/standards/tei/teip3/

== Council Telco - 21 August 2008 ==
Minutes of the last meeting: http://www.tei-c.org/Activities/Council/Meetings/tcm39.xml
== Issues for next Telco - Oct 2008 ==
* update on SF bugs and features (Oxford)

* report to TEI MM

* naming releases/versions (tei vs. P5)

Peter Boot: tei.full - tei.components

This refers to my (PB's) question on the council list ([http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html http://lists.village.virginia.edu/pipermail/tei-council/2008/009971.html]) about identification of releases and the following discussions. The difference between the two packages (tei.full - tei.components ) on SF has been clarified. Sebastian has added version numbers to generated schema’s.

Issues that remain

- do we use the SF news mechanism (a project where the latest news item dates from a year ago doesn't seem very dynamic)

- Roma shows a version number of the software, not of the TEI release that is being used

* update on SIGs + responsabilities

* placement of Schematron rules in ODD
http://lists.village.virginia.edu/pipermail/tei-council/2008/010033.html

Note to be produced by SR

* update on '"getting started"', see https://USER@tei.svn.sourceforge.net/svnroot/tei/trunk/Documents/GettingStarted (replacing 'USER' with your SourceForge username) and [[Getting Started]]

Looking for candidates:
** 6. Choosing and installing an editor
** 9. Getting this to work on sample of own text
** 11. Where to go from here

== Issues for next F2F ==

* Discussion on ODD and its evolution--[[User:Romary|Romary]] 02:34, 9 September 2008 (EDT)

cf. @usage in elementSpec

ODD modifing an ODD (ODD architecture)

Namespaces

* Evolution of Roma

Proposal (SR): rewriting Roma almost entirely in Javascript, interacting with web services to deliver TEI and to generate outputs. The Javascript would grab a copy of TEI (cut down) from a chosen server, and load it into memory. Then it would use that to help you build your ODD. when you were done, it would send the ODD document to a web service whose job is to return a schema or documentation back to the browsers. So Roma would be a Javascript ODD editor, not needing server support beyond a simple Apache, but closely coupled to a pair of generic web services. The generator web service would be identical code to the Vesta desktop

Additional functionalities needed (PB):

- adding copy element functionality,

- supporting the creation/manipulation of content models (instead of the user having to write the models),

- support/help in creating schematron constraints?

- TEI schema validation service (cf. also ISO project)

* should the TEI-C we produce a general purpose online service which can validate and process documents (cf. ISO work)

== Highlights to be brought to the TEI MM 2008 ==

== Topics (could be moved up to one F2F or Telco meeting ==

* Stable reference to TEI objects

(For original source of these comments, see tei-council thread [http://lists.village.virginia.edu/pipermail/tei-council/2008/010041.html Quoting a TEI Object] from September 2008. DS has created a new wiki page for discussing [[Council:stable references|stable references]].)

[LR] In many cases, one has to map schemas and describe the mappings by reference to actual objects in the respective encoding schemes. In this context do (should) we have a mechanism to refer uniquely to TEI objects, beyond the reference to the TEI namespace (<author> in http://www.tei-c.org/ns/1.0), sort of TEI unique identifiers?

[JC] I'd think the proper way to cite an element, class, or datatype generally is to point to its reference page. http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-tree.html

However, we might want to re-examine that... while the hierarchy should remain the same, deprecated elements (etc.) disappear. I have no way easy way to point to something at a particular date in time...unless maybe I point to it at a particular revision in the SVN source tree?

Pointing to a location in the SVN source tree isn't necessarily very pretty but does work and is accurate:

See for example an earlier version of <event>: http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?revision=231&view=markup

As a cognate example, I can point to any revision of a page in the TEI wiki at any point in its history. We should be able to do this, somehow, in the official way we are meant to cite TEI sources as changing objects in time.

However, maybe an easier solution is to cite:
http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-event.html
but on the generated reference pages like this contain a link to the appropriate place in the SVN repository? i.e.
http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/event.xml?view=log
which lists all the revisions.

[AC] The only place on the website where I am ware there are some recommendations with URLs is the citation page:
http://www.tei-c.org/Guidelines/access.xml

This could certainly be enriched with notes on how to point to an element on the line James suggests, but in that case would the version number be enough to point to particular revisions?

[DS] As an alternative to using a TEI-specific convention for citing URLs, we
might want to consider adopting one or another of the standard systems
for permanent identifiers, for example DOI (Digital Object Identifier).

In the case of DOI, there would be some fairly minimal costs involved to
register the DOIs with one of the national registries, but some more
extensive costs in human time to set up a good system for mapping from
our existing nomenclature to a set of DOI identifiers. (Publishers
typically use DOIs to identify individual books or journal articles, but
they can be more granular: every reference page in the Guidelines could
have its own DOI, for example.)

The advantage of doing this would be that anyone accustomed to using
DOIs for citations could simply cite a DOI. So instead of the reference
for <name> in the Guidelines

http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-name.html

we would use something like

doi:10.1111/tei-p5-doc:en:ref-name

which would be resolved to the actual Web address by a DOI resolver.
(Many journal DOIs are mostly numeric but the syntax allows more
human-readable names).

If we seriously want to consider an option like this, we should put out
a call to the librarians/metadata gurus in our community for assistance
with implementation.

== Misc. ==
For general information concerning the council see [[TEI-Council-FAQ]] page and [[:Category: Council|category reserved for use by TEI Council]]...

[[Category:Council]]

Practices no longer recommended or now deprecated

2012-08-05T22:13:17Z

GabrielBodard: /* Hard deprecation */

Over the course of a few [[Council|TEI Technical Council]] meetings from 2010 to 2012, Council members agreed to establish two different deprecation mechanisms for practices in the Guidelines which are to be phased out at some point. (See [http://purl.org/tei/fr/1933481 a bit of history of the technical implementation].) Here are links to particular meetings where this was discussed:

* [http://www.tei-c.org/Activities/Council/Meetings/tcm45.xml April 2010 meeting in Dublin]
* [http://www.tei-c.org/Activities/Council/Meetings/tcm46.xml April 2011 meeting in Chicago]
* [http://www.tei-c.org/Activities/Council/Meetings/tcm48.xml November 2011 meeting in Paris]
* [http://www.tei-c.org/Activities/Council/Meetings/tcm50.xml April 2012 meeting in Ann Arbor]

== Soft deprecation ==

"Soft deprecation", sometimes called a "health warning", is a statement in the Guidelines that a practice is no longer recommended. However, no timeline is established for removing particular elements or attributes. There is currently no mechanism to find such statements in the Guidelines to actually remove them.

Examples:

* [http://purl.org/tei/fr/3520653 deprecate <relationGrp>] -- See the resulting [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-relationGrp.html note on definition of relationGrp]
* [http://purl.org/tei/fr/3266021 dictionary entries with a single <sense>]
* [http://purl.org/tei/fr/3437509 Use of @key]
* [http://purl.org/tei/fr/3286136 <altIdentifier> is deprecated within <msPart>] -- ''Perhaps this should have been done as a hard deprecation. We didn't specify.''

== Hard deprecation ==

We make adjustments to the prose of the Guidelines, and @status=deprecated is inserted in the Guidelines ODD(s) to mark the deprecated element or attribute.

Examples:

* [http://purl.org/tei/bug/3376456 deprecate use of gram except as a child of gramGrp] -- Kevin is waiting on clarification on whether to create a new ticket and needs guidance on where to put status="deprecated".
* [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-join.html @targets deprecated on <join>] -- This was implemented at revisions [http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/join.xml?r1=8457&r2=8763 8763] and [http://tei.svn.sourceforge.net/viewvc/tei/trunk/P5/Source/Specs/join.xml?r1=8763&r2=8808 8808] (but can't find a mention in any minutes, a ticket, or discussion of this on tei-council).

== To be resolved ==

For both soft and hard deprecation, a bug or feature request ticket is sometimes created -- or an existing bug or feature request is reassigned to the "Deprecated" category.

* [http://purl.org/tei/bug/3435326 We might change our practice to create a new type of tracker item instead of using a category].
* Should we use this category only for soft or only for hard deprecation? Should "closed" mean that the practice has been deprecated or, for a hard deprecation, should it mean that the element or attribute has actually been removed?

[[Category:Council]]

AnnArbor2012-Actions

2012-07-31T15:24:56Z

GabrielBodard: GB actions updated

A list of actions, those responsible, and what has been done about them from Ann Arbor 2012 face to face meeting of TEI Technical Council

{|class="wikitable"
|Who
|What
|Result
|-
|KH, LB, PS, and JC
|Get more examples from Ranjith of the current state of the output so that we can calculate some statistics on accuracy, and encourage Google towards making this output format public.
|samples sent to tei-council on 2012-06-28
|-
|SR
|will convert the EEBO-TCP <byline> to <signed> , which solves the issue of the EEBO-TCP import; the broader issue of <figure> will be addressed in the discussion of <floatingDiv> later.
|done
|-
|SR
|Add <trailer> to att.typed
|done
|-
|RW, JC
|http://purl.org/tei/bug/3480609 RW will check TEI documents and outputs to confirm everything licensed CC+BY and BSD2Clause (not CC+BY+SA or otherwise), and will report back about any inconsistencies. JC will close the bug, and a new one will be opened for any issues which emerge.
|done (RW investigating others--in progress, but won't be done before the 6/15 release. rw)
|-
|MH, JC
|http://purl.org/tei/bug/3472477 MH to implement change of IDs in output of guidelines
|Not for June 2012 release. I've had one shot at this and failed. I will try again when I have time, but it's not release-blocking.
|-
|MH, RW
|http://purl.org/tei/bug/3471119 MH will implement the consensus (no spaces around em dashes used parenthetically). RW will create the styleguide document with help from KH who knows the CMS system already. The text style guide will be deleted.
|Em dashes done: all spaces around em dashes used parenthetically should be gone, except in the case of examples, quotations and bibliographic titles (where presumably the spacing from the original source is preserved).
|-
|JC, KH
|http://purl.org/tei/bug/3395448 JC will try to discover whether Virginia is technically still a partner or not. When it’s resolved, KH will implement any changes to the website.
|Pending
|-
|JC, MH
|http://purl.org/tei/fr/3511134 JC and MH will conspire to implement an html:@id for attributes in HTML Guidelines output in the stylesheets.
|Done in rev 10655.
|-
|KH
|http://purl.org/tei/fr/3437509 KH will review the whole thread and make a recommendation about the form of @ref, and make the soft deprecation changes to the Guidelines; these will be reviewed by LB.
|done
|-
|SR, PB
|http://purl.org/tei/fr/3432520 Finish implementing standard attributes referring to ISOCAT
|done
|-
|PB
|http://purl.org/tei/fr/3046288 PB will contact LR and ask him to provide further examples.
|done
|-
|KH
|http://purl.org/tei/fr/3041605 KH to close ticket
|done
|-
|JC
|http://purl.org/tei/bug/3497369 (JC) Strike the sentence that’s under discussion, because then the paragraph is less confusing. We should also add a new section (12.2.4), which explains that you don’t have to use ids in @from and @to; you can also use any URIs and XPointers with TEI XPointer schemes.
|Sentence deleted, new section written but to be added after this release to give more time for feedback.
|-
|MH
|http://purl.org/tei/bug/3497356 MH will ask the submitter (and the TEI-L, pointing to the ticket) for any examples of the use of <div> which suggest that <listApp> might be useful (for instance, organization of <apps> into multiple <div> s with @type).
|An element spec for <listApp> is in SVN as of rev 10658, but it still needs examples, and the TC chapter will need revisions when it's included. The ticket itself was closed for some reason, and without comment, so I've reopened it and assigned it to myself.
|-
|LB
|http://purl.org/tei/bug/3496998 LB will add an additional example of how to combine <lacunaEnd> inside a <rdg> . Ticket will be closed.
|done
|-
|KH
|http://purl.org/tei/bug/3475748 KH to implement
|done
|-
|SR to coordinate, KH and GB to assist
|http://purl.org/tei/bug/3440771
*document how to point from a <geo> to the <geoDecl> in order to indicate which coordinate system is being used.
*Remove from the Guidelines the statement that “All uses of geo within a document are required to use the same coordinate system.”
*edit the definition of <location> to say something like “defines the location of a place as *one or more* sets of geographical coordinates...” to indicate that more than one system may be used at once
clarify relationship between <location> and <geo> in the prose of the Guidelines
|
|-
|LB
|http://purl.org/tei/bug/3458222 LB will add <pc> to pPart.edit and revise the prose accordingly
|done (but see note on ticket -- it's a matter of making <pc> reference pPart.edit, not changing its membership)
|-
|MH
|http://purl.org/tei/bug/3500088 MH to re-visit to determine what's unclear and correct Guidelines.
|Done in rev 10481.
|-
|SR
|http://purl.org/tei/fr/3423686 Sebastian to nag Ontology SIG
|done, tho no resolution
|-
|PB
|http://purl.org/tei/fr/3288293 PB will add a new attribute to att.pointing, called @targetLang.
|done
|-
|JC
|http://purl.org/tei/fr/2724997 and http://purl.org/tei/fr/2507305 linking audio/video; JC will write to TEI-L asking for people who are interested in this area to get in touch. He will run the message by Council first. These people will join a Council working group to come back with a consistent proposal to be discussed later at this meeting.
| (Not release-blocking)
|-
|MH, SR, LB
|MH will write a new section for “How to edit the Guidelines” which explains TEI testing framework in more detail; this will then be checked by SR and LB.
|
|-
|LB, MH
|LB and MH to make sure a new-style inclusion TEI Lite ODD is up to date, regenerate schemas and update prose to match. The result should be packaged and archived as a stable and unchanging resource.
|
|-
|KH, LB, MH
|KH will collaborate with LB and MH to carry out the same process of freezing with Tite.
|
|-
|KH
|KH will make the Best Practices for TEI in Libraries customization available through the TEI website (we will not incorporate it into our build process because it’s too restrictive); the document itself will be mined for good ideas, and turned into a set of recommendations for changes to the Guidelines. KH to submit tickets for items to be added to the main Guidelines, since most of the items are likely to be independent and can be assessed separately.
|added as community customization
|-
|MH
|http://purl.org/tei/bug/3496958 (MH) We leave the content model alone (it’s horrible), but we use this as an example for Council to collaborate on the creation of one or more Schematron constraints which will enforce the presence of at least one <rdg> , to everyone’s edification.
|Schematron constraint added, but wrote to Council to check that's what should have been done given comments on ticket (which is still open).
|-
|JC
|http://purl.org/tei/bug/3496954 No action required; JC to close ticket.
|done
|-
|LB
|http://purl.org/tei/bug/3496951 LB to create att.witnessed for @wit on <rdg> and <lem> and remove @wit from <rdgGrp>
|done at rev 10243
|-
|GB
|http://purl.org/tei/bug/3496949 GB will review the particular example mentioned on the ticket, and revise and expand it: firstly, use a straightforward witness; secondly add an example for the "unattested" case.
|(Needs more discussion--or someone else to implement)
|-
|JC
|http://purl.org/tei/fr/3490054 JC will close ticket with won't fix suggesting it for P6
|done
|-
|JC
|Start wiki page on P6 development ideas http://wiki.tei-c.org/index.php/P6-dev
|done
|-
|SY
|SY will send an email to tei-l to encourage people to add their docs to the samples page to keep open the statistical approach in the long term.
|done
|-
|MH
|MH look at existing pages for attribute classes and see if there are any examples, try adding an example to att.ascribed class spec to see if it works
|Done. Example for @who added to att.ascribed.xml in rev 10491.
|-
|SR
|SR Sebastian will "show all examples" so that at the top it lists examples from the appropriate chapter, and links to that chapter.
|done
|-
|MH
|MH to create a wiki page to coordinate adding examples to attribute classes. Since most attribute classes do not have examples, all of us should generate examples to be added to attribute class pages.
|Done. Page is at [[AttsWithoutEgs#Attributes_without_an_example_in_their_elementSpec_OR_classSpec|AttsWithoutEgs]]
|-
|SR
|change build process so that you can't build without examples on attribute classes (this would have to be implemented later)
|
|-
|MH
|http://purl.org/tei/fr/3434990 MH will write a Schematron rule requiring that <lg> contains <l> , <lg> , or <gap>
|Done 2012-06-17, in rev 10522. A Schematron test has been added, but I still have to document that process for the "How to edit the Guidelines" document.
|-
|SR
|http://purl.org/tei/fr/3305016 SR will implement the content model proposed by KH on SF
|done
|-
|GB
|http://purl.org/tei/fr/3416130 GB will survey the guidelines to see what kind of changes <certainty> within milestone elements would involve. He will report back via email, unless there is great disagreement the FR should be approved and implement. If there is disagreement, address at our next teleconference
|Survey done and Council emailed.
|-
|JC
|http://purl.org/tei/fr/3416130 JC will update the ticket in sourceforge to assign to GB and add a note about our decided action
|done
|-
|JC
|macro.paraContent out of place in <gram> etc [cf <u> discussion] link to ticket is broken, so group E did not discuss;
Action: JC to find out what happened to this ticket.
|JC: Found ticket at http://purl.org/tei/bug/3376863 needs more discussion.
|-
|KH
|http://purl.org/tei/fr/3500566 Implement proposal 'a' on SF ticket
|done
|-
|GB
|http://purl.org/tei/fr/3497079 GB to write a comment on the ticket giving examples of citations that would be problematic or confusing according to this proposal. Paul can also provide example citations from his U-M CV project. Kevin will discuss with Gabby and incorporate marked-up examples into proposal and revise proposal if appropriate. Leave ticket open for now
|GB commented. (More discussion needed?)
|-
|JC
|http://purl.org/tei/fr/3440977 Agreed: Suggest LR to implement. JC will contact him and report back to us if he will not implement.
|Done.
|-
|KH
|http://purl.org/tei/fr/2493417 Agreed and implemented but KH to add more examples/prose
|done
|-
|KH
|http://purl.org/tei/fr/3480057 KH to close
|done
|-
|KH (was MH)
|http://purl.org/tei/bugs/3439587 MH will revise definition of <titleStmt> to no longer imply responsibility for intellectual content only. MH will also investigate adding <distributor> and <publisher> to model.respLike.
|<titleStmt> changes done by MH. Issue of <distributor> and <publisher> remains outstanding and is a bit messy. The ticket has now been assigned by JC to KH.
|-
|RW
|http://purl.org/tei/fr/3496494 RW will adapt defintion of <span> to take better wording from 17.3
|
|-
|LB
|http://purl.org/tei/fr/3495987 LB will ask Laurent for examples in case we are assuming incorrectly and will look at TEI-L archives.
|
|-
|LB
|http://purl.org/tei/fr/2834511 LB will add proposed Schematron rules but not add any other elements without clear use cases.
|
|-
|SR
|http://purl.org/tei/fr/3291540 SR will take the ticket. We’ll leave it to SR to decide which of the second list of elements should be included as well. Sebastian will send a list to TEI-L so people could comment on any elements where it would be removed.
|
|-
|SR
|http://purl.org/tei/fr/3284816 SR to implement.
|did faith
|-
|SR
|http://purl.org/tei/fr/3415801 Allow modification of attributes belonging to a class; SR will implement (in long-term).
|
|-
|LB
|http://purl.org/tei/fr/3118435 LB to close ticket
|done
|-
|SR
|http://purl.org/tei/fr/3426828 SR to close this ticket noting that requestor hasn’t responded.
|done
|-
|MH
|http://purl.org/tei/fr/1650195 MH to implement adding <schemaSpec> to model.encodingDescPart.
|Done in revs 10314-10317. Ticket closed.
|-
|JC
|FloatingText proposal: JC will reply to the message on TEI-L: In light of the current text and examples in the Guidelines on <floatingText> and <spGrp> , we’d like examples of proposed “floating divs” and how they would differ from <floatingText>s.
|(Not release-blocking)
|-
|LB, KH, BB, PS
|http://purl.org/tei/bug/3439980 LB to chair an ad hoc council working group on div-liminal to report back on this before next face2face, KH, LB, and PS to be members, others as necessary.
|
|-
|SR, LB, MH, PB
|Audio/Video Facsimiles -- Working group to be chaired by SR, with LB, MH, and possibly PB; to approach TEI-L and others doing work in this area to get outside expertise; an initial proposal or detailed report of progress at next FTF with status reports at teleconferences.
|
|-
|MH, GB, SY
|MH will chair this working group on private URI schemes and their documention, bring in GB, SY, and outside people suggested by GB. They will develop concrete proposals for next FTF meeting with status reports at teleconferences.
|Work underway. Description of [[XPointer|current state of XPointer play|XPointer]] and list of [[Stand-off use cases]] done. Use cases circulated to TEI-L for consultation.
|-
|MH
|Private Uri Schemes (split from preceding): the issue of Private Uri Schemes, and a method of documenting their use, is not really part of the TEI Pointers issue at all.
|A proposal is being developed here: http://wiki.tei-c.org/index.php/Private_URI_Schemes (Have Matteo Romanello, Sebastian Heath, etc. been invited to comment on this?)
|-
|JC
|James will prod the critical apparatus working group before next teleconference.
|(Done, but will do again)
|-
|JC
|JC to produce a Council meeting/telco checklist on TEI-C Wiki to ensure we don't forget steps (like asking SIGs if they have technical things they want to report)
|(Not release-blocking)
|-
|SY, LB, PB
|UIMA, GATE and other tools. SY will follow up offline w/ LB, PB; PB will put SY in touch with others working in UIMA and interested in converting to TEI;PB and SY report back to Council on progress by next FTF
|
|-
|LB, RW
|http://purl.org/tei/bugs/3454814 LB will write up guidelines for purging comments and distribute to TEI-Council list, including describing first passes to deal with low-hanging fruit and suggested format for how we should comment going forward from there, work of reviewing and purging comments or turning them into notes will be divided among council members. RW will incorporate language from LB’s guidelines into the style guide when appropriate
|
|-
|MH
|http://purl.org/tei/bugs/3454803 MH will compare Chapter CH against the latest version of BCP 47 for inconsistencies
|Done in revs 10650 through 10652 (2012-07-08).
|-
|MH
|Create new Jenkins build script for Ubuntu 12.04 server.
|Done 2012-06-13.
|-
|SR, KH
|http://purl.org/tei/bugs/3432216 SR: double check FM1 to see if list of translators is up to date; KH will add this policy to the “how to edit the guidelines” working paper
|tcw20 now says to leave @version attribute unchanged. Korean translator name added to FM1
|-
|PS, RW
|http://purl.org/tei/bugs/3223636 Expand our explanation of xml:space in the Guidelines:
* in note: expand to acknowledge that many parsers may not handle xml:space properly
* clarify definition of xml:space’s “default” value to match the XML spec (that is, “whatever the processor would normally do)
* remove sentence in prose of guidelines in chapter 22 "the global @xml:space is available to indicate that white space should be preserved within the content of these elements"
|
|-
|SR
|http://purl.org/tei/bugs/3393781 SR per LB’s comment on Sourceforge: Agreed to rename @version in att.translatable as @versionDate and give it a date datatype. We don’t want all the possibilities of att.datable.
|done
|-
|JC
|JC to add TEI Sourceforge site to the TEI category so all TEI sourceforge projects can be located at once
|done
|}

Council FR assignments

2010-11-12T11:28:56Z

GabrielBodard: /* TEI Council Feature Request assignments (October 2010) */ fixed table structure

===TEI Council Feature Request assignments (October 2010)===

{| class="wikitable" border="1"
|+
| Group
| ticket(s)
| nuncle(s)
|-
| 1
|
* [https://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 3060909: add attribute for non-numeric characterisation of precision]
* [https://sourceforge.net/tracker/?func=detail&aid=3060919&group_id=106328&atid=644065 3060919: add way of expressing confidence for att.ranging values]
| GB, JN
|-
| 2
|
* [https://sourceforge.net/tracker/?func=detail&aid=3060874&group_id=106328&atid=644065 3060874: @source and @code for <faith>]
* [https://sourceforge.net/tracker/?func=detail&aid=3060867&group_id=106328&atid=644065 3060867: Grouping elements for traitlike, statelike, and eventlike elements]
| SR, LB
|-
| 3
|
* [https://sourceforge.net/tracker/?func=detail&aid=3051750&group_id=106328&atid=644065 3051750: Form of words needs to be proposed (schema langs)]
* [https://sourceforge.net/tracker/?func=detail&aid=2493417&group_id=106328&atid=644065 2493417: Ibid (idno)]
| JN, BB
|-
| 4
|
KH, LR and MH have now added final recommendations for the committee as comments on all of these tickets.
* [https://sourceforge.net/tracker/?func=detail&aid=2976715&group_id=106328&atid=644065 2976715: resp -> model.respLike in biblStruct. and other things.]
* [https://sourceforge.net/tracker/?func=detail&aid=2987832&group_id=106328&atid=644065 2987832: date within biblStruct]
* [https://sourceforge.net/tracker/?func=detail&aid=2714682&group_id=106328&atid=644062 2714682: biblScope should be in Imprint or not? (biblStruct)]
* [https://sourceforge.net/tracker/?func=detail&aid=2987241&group_id=106328&atid=644062 2987241: <monogr> and <analytic> should be allowed in <bibl>]
* Further recommendations arising from the working paper on bibliographic description
| MH, KH
|-
| 5
|
* [https://sourceforge.net/tracker/?func=detail&aid=2994685&group_id=106328&atid=644065 2994685: att.global shd be explicit in ODD source]
* [https://sourceforge.net/tracker/?func=detail&aid=1933481&group_id=106328&atid=644065 1933481: @status attribute to indicate deprecated elements]
| JC, SR
|-
| 6
|
* [https://sourceforge.net/tracker/?func=detail&aid=2724992&group_id=106328&atid=644065 2724992: features for alignment of audio and video]
* [https://sourceforge.net/tracker/?func=detail&aid=2507305&group_id=106328&atid=644065 2507305: alignment and documentation of sound files]
|
|-
| 7
|
* [https://sourceforge.net/tracker/?func=detail&aid=2811239&group_id=106328&atid=644065 2811239: "object" element]
| BB, GB, EP, DP
|-
| 8
|
* [https://sourceforge.net/tracker/?func=detail&aid=2925145&group_id=106328&atid=644065 2925145: generic dating class]
|GB, SR
|-
| 9
|
* [https://sourceforge.net/tracker/?func=detail&aid=2834511&group_id=106328&atid=644065 2834511: make more spanning elements]
* [https://sourceforge.net/tracker/?func=detail&atid=644065&aid=3095637&group_id=106328 3095637: new document, patch, line elements ]
* [https://sourceforge.net/tracker/?func=detail&atid=644065&aid=3095640&group_id=106328 3095640: new pPart.transcriptional elements]
* [https://sourceforge.net/tracker/?func=detail&atid=644065&aid=3095641&group_id=106328 3095641: new elements to document writing stages]
|LB, EP, DP
|}

Plus, still outstanding from last month, the following need reviewing as we did not reach consensus on them.

* [https://sourceforge.net/tracker/?func=detail&aid=3044329&group_id=106328&atid=644065 3044329: add @licence attribute to <availability>] Y N N ? Y N Y ? ?
* [https://sourceforge.net/tracker/?func=detail&aid=2994671&group_id=106328&atid=644065 2994671 Review suggested values for @calendar] Y N N Y N Y N Y Y
* [https://sourceforge.net/tracker/?func=detail&aid=2994666&group_id=106328&atid=644065 2994666 Change idno content model to macro.xText] N N Y Y Y Y Y N N
* [https://sourceforge.net/tracker/?func=detail&aid=2984463&group_id=106328&atid=644065 2984463 Add new class att.sortable] Y N Y ? Y ? Y N ?

Council FR assignments

2010-10-20T13:47:42Z

GabrielBodard: tidied wikicode

===TEI Council Feature Request assignments (October 2010)===

{| class="wikitable" border="1"
|+
| Group
| ticket(s)
| nuncle(s)
|-
| 1
|
* [https://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 3060909: add attribute for non-numeric characterisation of precision]
* [https://sourceforge.net/tracker/?func=detail&aid=3060919&group_id=106328&atid=644065 3060919: add way of expressing confidence for att.ranging values]
| GB, JN
|-
| 2
|
* [https://sourceforge.net/tracker/?func=detail&aid=3060874&group_id=106328&atid=644065 3060874: @source and @code for <faith>]
* [https://sourceforge.net/tracker/?func=detail&aid=3060867&group_id=106328&atid=644065 3060867: Grouping elements for traitlike, statelike, and eventlike elements]
| SR, LB
|-
| 3
|
* [https://sourceforge.net/tracker/?func=detail&aid=3051750&group_id=106328&atid=644065 3051750: Form of words needs to be proposed (schema langs)]
* [https://sourceforge.net/tracker/?func=detail&aid=2493417&group_id=106328&atid=644065 2493417: Ibid (idno)]
| JN, BB
|-
| 4
|
* [https://sourceforge.net/tracker/?func=detail&aid=2976715&group_id=106328&atid=644065 2976715: resp -> model.respLike in biblStruct. and other things.]
* [https://sourceforge.net/tracker/?func=detail&aid=2987832&group_id=106328&atid=644065 2987832: date within biblStruct]
* [https://sourceforge.net/tracker/?func=detail&aid=2714682&group_id=106328&atid=644062 2714682: biblScope should be in Imprint or not? (biblStruct)]
* [https://sourceforge.net/tracker/?func=detail&aid=2987241&group_id=106328&atid=644062 2987241: <monogr> and <analytic> should be allowed in <bibl>]
* Further recommendations arising from the working paper on bibliographic description
| MH, KH
|-
|rowspan=2| 5
|
* [https://sourceforge.net/tracker/?func=detail&aid=2994685&group_id=106328&atid=644065 2994685: att.global shd be explicit in ODD source]
* [https://sourceforge.net/tracker/?func=detail&aid=1933481&group_id=106328&atid=644065 1933481: @status attribute to indicate deprecated elements]
| JC, SR
|-
| colspan=2|This is a philosophical issue which just needs a vote - is att.global special or not? Making the change is relatively easy, and simplifies lots of code, but it means that a fundamental TEI magic rule is lost
|-
| 6
|
* [https://sourceforge.net/tracker/?func=detail&aid=2724992&group_id=106328&atid=644065 2724992: features for alignment of audio and video]
* [https://sourceforge.net/tracker/?func=detail&aid=2507305&group_id=106328&atid=644065 2507305: alignment and documentation of sound files]
|
|-
| 7
|
* [https://sourceforge.net/tracker/?func=detail&aid=2811239&group_id=106328&atid=644065 2811239: "object" element]
| BB, GB, EP, DP
|-
| 8
|
* [https://sourceforge.net/tracker/?func=detail&aid=2925145&group_id=106328&atid=644065 2925145: generic dating class]
|GB, SR
|-
|rowspan=2| 9
|
* [https://sourceforge.net/tracker/?func=detail&aid=2834511&group_id=106328&atid=644065 2834511: make more spanning elements]
|LB, EP, DP
|-
| colspan=2|a) New element <document> to be added to model.resourceLike ; new element <line> to be added to model.zonePart; new element <patch> allowed within <surface>

Together with existing <surface> and <zone> elements, these allow theory neutral transcription of physicality of document

b) several new elements to be added to model.pPart.transcriptional (<mod>, <modSpan>, <metaMark>, <used>, <undo>, <redo>, <rewrite>, <transposeGrp>, <transpose>)

These allow more detailed documentation of the writing process than previously possible

c) New <stageNotes> within the existing <creation> element containing new <stageNote> elements to document identified "writing stages" in genesis of a text. New att.staged class to supply @stage attributes for elements which can be assigned to a given writing stage

These allow marked up elements to be assigned to particular stages in the genesis of a text, or the writing of a document, or both!
|}

Council FR assignments

2010-10-19T14:02:43Z

GabrielBodard: prettified layout of comment

===TEI Council Feature Request assignments (October 2010)===

{| class="wikitable" border="1"
|+
| Group
| ticket(s)
| nuncle(s)
|-
| 1
| [https://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 3060909: add attribute for non-numeric characterisation of precision]
[https://sourceforge.net/tracker/?func=detail&aid=3060919&group_id=106328&atid=644065 3060919: add way of expressing confidence for att.ranging values]
| GB
|-
| 2
| [https://sourceforge.net/tracker/?func=detail&aid=3060874&group_id=106328&atid=644065 3060874: @source and @code for <faith>]
[https://sourceforge.net/tracker/?func=detail&aid=3060867&group_id=106328&atid=644065 3060867: Grouping elements for traitlike, statelike, and eventlike elements]
| SR, LB
|-
| 3
| [https://sourceforge.net/tracker/?func=detail&aid=3051750&group_id=106328&atid=644065 3051750: Form of words needs to be proposed (schema langs)]
[https://sourceforge.net/tracker/?func=detail&aid=2493417&group_id=106328&atid=644065 2493417: Ibid (idno)]
| JN, BB
|-
| 4
| [https://sourceforge.net/tracker/?func=detail&aid=2976715&group_id=106328&atid=644065 2976715: resp -> model.respLike in biblStruct. and other things.]
[https://sourceforge.net/tracker/?func=detail&aid=2987832&group_id=106328&atid=644065 2987832: date within biblStruct]
[https://sourceforge.net/tracker/?func=detail&aid=2714682&group_id=106328&atid=644062 2714682: biblScope should be in Imprint or not? (biblStruct)]
[https://sourceforge.net/tracker/?func=detail&aid=2987241&group_id=106328&atid=644062 2987241: <monogr> and <analytic> should be allowed in <bibl>]

Further recommendations arising from the working paper on bibliographic description
| MH, KH
|-
|rowspan=2| 5
| [https://sourceforge.net/tracker/?func=detail&aid=2994685&group_id=106328&atid=644065 2994685: att.global shd be explicit in ODD source]
[https://sourceforge.net/tracker/?func=detail&aid=1933481&group_id=106328&atid=644065 1933481: @status attribute to indicate deprecated elements]
| JC, SR
|-
|colspan=2|This is a philosophical issue which just needs a vote - is att.global special or not? Making the change is relatively easy, and simplifies lots of code, but it means that a fundamental TEI magic rule is lost
|-
| 6
| [https://sourceforge.net/tracker/?func=detail&aid=2724992&group_id=106328&atid=644065 2724992: features for alignment of audio and video]
[https://sourceforge.net/tracker/?func=detail&aid=2507305&group_id=106328&atid=644065 2507305: alignment and documentation of sound files]
|
|-
| 7
| [https://sourceforge.net/tracker/?func=detail&aid=2811239&group_id=106328&atid=644065 2811239: "object" element]
| BB, GB, EP, DP
|-
| 8
| [https://sourceforge.net/tracker/?func=detail&aid=2925145&group_id=106328&atid=644065 2925145: generic dating class]
| GB, SR
|-
| 9
| [https://sourceforge.net/tracker/?func=detail&aid=2834511&group_id=106328&atid=644065 2834511: make more spanning elements]
| LB, EP, DP
|}

Council FR assignments

2010-10-19T10:53:32Z

GabrielBodard: /* TEI Council Feature Request assignments (October 2010) */

===TEI Council Feature Request assignments (October 2010)===

{| class="wikitable" border="1"
|+
| Group
| ticket(s)
| nuncle(s)
|-
| 1
| [https://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 3060909: add attribute for non-numeric characterisation of precision]
[https://sourceforge.net/tracker/?func=detail&aid=3060919&group_id=106328&atid=644065 3060919: add way of expressing confidence for att.ranging values]
| GB
|-
| 2
| [https://sourceforge.net/tracker/?func=detail&aid=3060874&group_id=106328&atid=644065 3060874: @source and @code for <faith>]
[https://sourceforge.net/tracker/?func=detail&aid=3060867&group_id=106328&atid=644065 3060867: Grouping elements for traitlike, statelike, and eventlike elements]
| SR, LB
|-
| 3
| [https://sourceforge.net/tracker/?func=detail&aid=3051750&group_id=106328&atid=644065 3051750: Form of words needs to be proposed (schema langs)]
[https://sourceforge.net/tracker/?func=detail&aid=2493417&group_id=106328&atid=644065 2493417: Ibid (idno)]
| JN, BB
|-
| 4
| [https://sourceforge.net/tracker/?func=detail&aid=2976715&group_id=106328&atid=644065 2976715: resp -> model.respLike in biblStruct. and other things.]
[https://sourceforge.net/tracker/?func=detail&aid=2987832&group_id=106328&atid=644065 2987832: date within biblStruct]

Further recommendations arising from the working paper on bibliographic description
| MH, KH
|-
| 5
| [https://sourceforge.net/tracker/?func=detail&aid=2994685&group_id=106328&atid=644065 2994685: att.global shd be explicit in ODD source]
[https://sourceforge.net/tracker/?func=detail&aid=1933481&group_id=106328&atid=644065 1933481: @status attribute to indicate deprecated elements]
| JC, SR
|-
| 6
| [https://sourceforge.net/tracker/?func=detail&aid=2724992&group_id=106328&atid=644065 2724992: features for alignment of audio and video]
[https://sourceforge.net/tracker/?func=detail&aid=2507305&group_id=106328&atid=644065 2507305: alignment and documentation of sound files]
|
|-
| 7
| [https://sourceforge.net/tracker/?func=detail&aid=2811239&group_id=106328&atid=644065 2811239: "object" element]
| BB, GB, EP, DP
|-
| 8
| [https://sourceforge.net/tracker/?func=detail&aid=2925145&group_id=106328&atid=644065 2925145: generic dating class]
| GB, SR
|-
| 9
| [https://sourceforge.net/tracker/?func=detail&aid=2834511&group_id=106328&atid=644065 2834511: make more spanning elements]
| LB, EP, DP
|}

Council FR assignments

2010-10-19T10:53:13Z

GabrielBodard: fixed broken link

===TEI Council Feature Request assignments (October 2010)===

{| class="wikitable" border="1"
|+
| Group
| ticket(s)
| nuncle(s)
|-
| 1
| [https://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 3060909: add attribute for non-numeric characterisation of precision]
[https://sourceforge.net/tracker/?func=detail&aid=3060919&group_id=106328&atid=644065 3060919: add way of expressing confidence for att.ranging values]
| GB
|-
| 2
| [https://sourceforge.net/tracker/?func=detail&aid=3060874&group_id=106328&atid=644065 3060874: @source and @code for <faith>]
[https://sourceforge.net/tracker/?func=detail&aid=3060867&group_id=106328&atid=644065 3060867: Grouping elements for traitlike, statelike, and eventlike elements]
| SR, LB
|-
| 3
| [https://sourceforge.net/tracker/?func=detail&aid=3051750&group_id=106328&atid=644065 3051750: Form of words needs to be proposed (schema langs)]
[https://sourceforge.net/tracker/?func=detail&aid=2493417&group_id=106328&atid=644065 2493417: Ibid (idno)]
| JN, BB
|-
| 4
| [https://sourceforge.net/tracker/?func=detail&aid=2976715&group_id=106328&atid=644065 2976715: resp -> model.respLike in biblStruct. and other things.]
[https://sourceforge.net/tracker/?func=detail&aid=2987832&group_id=106328&atid=644065 2987832: date within biblStruct]
Further recommendations arising from the working paper on bibliographic description
| MH, KH
|-
| 5
| [https://sourceforge.net/tracker/?func=detail&aid=2994685&group_id=106328&atid=644065 2994685: att.global shd be explicit in ODD source]
[https://sourceforge.net/tracker/?func=detail&aid=1933481&group_id=106328&atid=644065 1933481: @status attribute to indicate deprecated elements]
| JC, SR
|-
| 6
| [https://sourceforge.net/tracker/?func=detail&aid=2724992&group_id=106328&atid=644065 2724992: features for alignment of audio and video]
[https://sourceforge.net/tracker/?func=detail&aid=2507305&group_id=106328&atid=644065 2507305: alignment and documentation of sound files]
|
|-
| 7
| [https://sourceforge.net/tracker/?func=detail&aid=2811239&group_id=106328&atid=644065 2811239: "object" element]
| BB, GB, EP, DP
|-
| 8
| [https://sourceforge.net/tracker/?func=detail&aid=2925145&group_id=106328&atid=644065 2925145: generic dating class]
| GB, SR
|-
| 9
| [https://sourceforge.net/tracker/?func=detail&aid=2834511&group_id=106328&atid=644065 2834511: make more spanning elements]
| LB, EP, DP
|}

Council FR assignments

2010-10-19T10:52:23Z

GabrielBodard: New page: ===TEI Council Feature Request assignments (October 2010)=== {| class="wikitable" border="1" |+ | Group | ticket(s) | nuncle(s) |- | 1 | [https://sourceforge.net/tracker/?func=detail&aid...

===TEI Council Feature Request assignments (October 2010)===

{| class="wikitable" border="1"
|+
| Group
| ticket(s)
| nuncle(s)
|-
| 1
| [https://sourceforge.net/tracker/?func=detail&aid=3060909&group_id=106328&atid=644065 3060909: add attribute for non-numeric characterisation of precision]
[https://sourceforge.net/tracker/?func=detail&aid=3060919&group_id=106328&atid=644065 3060919: add way of expressing confidence for att.ranging values]
| GB
|-
| 2
| [https://sourceforge.net/tracker/?func=detail&aid=3060874&group_id=106328&atid=644065 3060874: @source and @code for <faith>]
[https://sourceforge.net/tracker/?func=detail&aid=3060867&group_id=106328&atid=644065 3060867: Grouping elements for traitlike, statelike, and eventlike elements]
| SR, LB
|-
| 3
| [https://sourceforge.net/tracker/?func=detail&aid=3051750&group_id=106328&atid=644065 3051750: Form of words needs to be proposed (schema langs)]
[https://sourceforge.net/tracker/?func=detail&aid=2493417&group_id=106328&atid=644065 2493417: Ibid (idno)]
| JN, BB
|-
| 4
| [https://sourceforge.net/tracker/?func=detail&aid=2976715&group_id=106328&atid=644065 2976715: resp -> model.respLike in biblStruct. and other things.]
[https://sourceforge.net/tracker/?func=detail&aid=2987832&group_id=106328&atid=644065 2987832: date within biblStruct]
Further recommendations arising from the working paper on bibliographic description
| MH, KH
|-
| 5
| [https://sourceforge.net/tracker/?func=detail&aid=2994685&group_id=106328&atid=644065 2994685: att.global shd be explicit in ODD source]
[https://sourceforge.net/tracker/?func=detail&aid=1933481&group_id=106328&atid=644065 1933481: @status attribute to indicate deprecated elements]
| JC, SR
|-
| 6
| [https://sourceforge.net/tracker/?func=detail&aid=2724992&group_id=106328&atid=644065 2724992: features for alignment of audio and video]
[2507305: alignment and documentation of sound files]
|
|-
| 7
| [https://sourceforge.net/tracker/?func=detail&aid=2811239&group_id=106328&atid=644065 2811239: "object" element]
| BB, GB, EP, DP
|-
| 8
| [https://sourceforge.net/tracker/?func=detail&aid=2925145&group_id=106328&atid=644065 2925145: generic dating class]
| GB, SR
|-
| 9
| [https://sourceforge.net/tracker/?func=detail&aid=2834511&group_id=106328&atid=644065 2834511: make more spanning elements]
| LB, EP, DP
|}

Samples of TEI texts

2010-02-23T16:31:03Z

GabrielBodard: /* Texts */ added IRT

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ala2004] ([[EpiDoc]] XML) from the [http://insaph.kcl.ac.uk/ala2004 '''Aphrodisias in Late Antiquity'''] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)

* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5

* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* [http://papyri.info/idp_static/current/ '''Duke Databank'''/Heidelberg] ([[EpiDoc]] XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) and the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata). Approx 55,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.

* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [[EpiDoc]] XML files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)

* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.

* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' ([[EpiDoc]] XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)

* [http://irt.kcl.ac.uk/irt2009/inscr/xmlrepo.html '''Inscriptions of Roman Tripolitania''' 2009] ([[EpiDoc]] XML), about 1000 Latin and Greek inscriptions available for download under Creative Commons Attribution (CC-BY) licence. Format: TEI P4.

* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/Resources/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/Resources/U16.xsl transform], a [http://www.sbl-site.org/Resources/U16.css stylesheet] and a [http://www.sbl-site.org/Resources/U16.html web page] produced from the transcription by the transform. (Format: TEI P5)

* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:
** Use of <revisionDesc> and <change> tags to implement workflow
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).

* The '''[[Perseus Project]]''' makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.

* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html '''Samyukta Agama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.

* The [http://www.tei-c.org/Activities/Workgroups/MI/Samples/ '''SGML-to-XML''' Migration Task Force] has made some of its case studies and samples available, with restricted permissions. These are mostly SGML P3-encoded files. [http://www.tei-c.org/Activities/Workgroups/MI/miw06.xml Descriptions of these samples] are also available.

* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr/Epistemon/index.htm Epistemon]. These files are licenced under Creative Commons Attribution.

* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI P4-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Some are now in P5, for example http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/swa-eng/swa-eng.tei

== See also ==
* [[TEI by example]]

Samples of TEI texts

2010-02-23T16:26:53Z

GabrielBodard: /* Texts */ sorted and highlighted

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip '''ala2004''' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/ala2004 Aphrodisias in Late Antiquity] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)

* [http://archimedespalimpsest.net/ '''Archimedes Palimpsest'''], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5

* [http://www.ota.ox.ac.uk/headers/2493.xml The '''Auchinleck Manuscript'''], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* [http://papyri.info/idp_static/current/ '''Duke Databank'''/Heidelberg] (EpiDoc XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) and the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata). Approx 55,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.

* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html '''EpiDoc Demo''' Website], a growing collection of sample [http://epidoc.sf.net/ EpiDoc XML] files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)

* A subset of [http://www.gutenberg.org/ Project '''Gutenberg'''] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.

* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html '''IAph2007''' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)

* The [http://www.tei-c.org/Activities/MI/Samples/ '''Migration Samples'''] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "'''Manuscript Markup'''," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/Resources/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/Resources/U16.xsl transform], a [http://www.sbl-site.org/Resources/U16.css stylesheet] and a [http://www.sbl-site.org/Resources/U16.html web page] produced from the transcription by the transform. (Format: TEI P5)

* The [http://www.nzetc.org/ NZETC] has a range of '''New Zealand and Pacific-Islands''' texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:
** Use of <revisionDesc> and <change> tags to implement workflow
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).

* The '''[[Perseus Project]]''' makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.

* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html '''Samyukta Agama''' Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.

* The [http://www.tei-c.org/Activities/Workgroups/MI/Samples/ '''SGML-to-XML''' Migration Task Force] has made some of its case studies and samples available, with restricted permissions. These are mostly SGML P3-encoded files. [http://www.tei-c.org/Activities/Workgroups/MI/miw06.xml Descriptions of these samples] are also available.

* The [http://www.bvh.univ-tours.fr/ BVH] project ('''Virtual Humanistic Libraries''') is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr/Epistemon/index.htm Epistemon]. These files are licenced under Creative Commons Attribution.

* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI P4-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Some are now in P5, for example http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/swa-eng/swa-eng.tei

== See also ==
* [[TEI by example]]

Samples of TEI texts

2010-02-23T16:22:14Z

GabrielBodard: /* Texts */ added IDP (ddbdp/hgv)

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ''ala2004'' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/ala2004 Aphrodisias in Late Antiquity] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)

* [http://archimedespalimpsest.net/ Archimedes Palimpsest], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5

* [http://www.ota.ox.ac.uk/headers/2493.xml The Auchinleck Manuscript], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* [http://papyri.info/idp_static/current/ Duke Databank/Heidelberg] (EpiDoc XML) aggregated data from the Duke Databank of Documentary Papyri (DDbDP: transcribed Greek texts) and the Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens (HGV: metadata). Approx 55,000 XML files released under Creative Commons Attribution license (CC-BY), by the [http://idp.atlantides.org/trac/idp/wiki Integrating Digital Papyrology] project. Format: TEI P5.

* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html EpiDoc Demo Website], a growing collection of sample [http://epidoc.sf.net/ EpiDoc XML] files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)

* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html ''IAph2007'' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)

* The [http://www.tei-c.org/Activities/MI/Samples/ Migration Samples] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "Manuscript Markup," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/Resources/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/Resources/U16.xsl transform], a [http://www.sbl-site.org/Resources/U16.css stylesheet] and a [http://www.sbl-site.org/Resources/U16.html web page] produced from the transcription by the transform. (Format: TEI P5)

* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html Samyukta Agama Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.

* The [http://www.tei-c.org/Activities/Workgroups/MI/Samples/ SGML-to-XML Migration Task Force] has made some of its case studies and samples available, with restricted permissions. These are mostly SGML P3-encoded files. [http://www.tei-c.org/Activities/Workgroups/MI/miw06.xml Descriptions of these samples] are also available.

* The [http://www.nzetc.org/ NZETC] has a range of New Zealand and Pacific-Islands texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:
** Use of <revisionDesc> and <change> tags to implement workflow
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).

* A subset of [http://www.gutenberg.org/ Project Gutenberg] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.

* The [http://www.bvh.univ-tours.fr/ BVH] project (Virtual Humanistic Libraries) is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr/Epistemon/index.htm Epistemon]. These files are licenced under Creative Commons Attribution.

* The [[Perseus Project]] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.

* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI P4-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Some are now in P5, for example http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/swa-eng/swa-eng.tei

== See also ==
* [[TEI by example]]

User:GabrielBodard

2010-02-23T16:08:59Z

GabrielBodard: update

Dr Gabriel Bodard (TEI Council 2008-2011)

For more information see [http://wiki.digitalclassicist.org/User:GabrielBodard bio page on Digital Classicist wiki].

Samples of TEI texts

2010-02-23T16:07:45Z

GabrielBodard: /* Texts */ EpiDoc demo vintage 2007

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ''ala2004'' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/ala2004 Aphrodisias in Late Antiquity] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)

* [http://archimedespalimpsest.net/ Archimedes Palimpsest], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5

* [http://www.ota.ox.ac.uk/headers/2493.xml The Auchinleck Manuscript], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html EpiDoc Demo Website], a growing collection of sample [http://epidoc.sf.net/ EpiDoc XML] files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Vintage 2007.) (Format: TEI P4)

* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html ''IAph2007'' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)

* The [http://www.tei-c.org/Activities/MI/Samples/ Migration Samples] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "Manuscript Markup," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/Resources/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/Resources/U16.xsl transform], a [http://www.sbl-site.org/Resources/U16.css stylesheet] and a [http://www.sbl-site.org/Resources/U16.html web page] produced from the transcription by the transform. (Format: TEI P5)

* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html Samyukta Agama Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.

* The [http://www.tei-c.org/Activities/Workgroups/MI/Samples/ SGML-to-XML Migration Task Force] has made some of its case studies and samples available, with restricted permissions. These are mostly SGML P3-encoded files. [http://www.tei-c.org/Activities/Workgroups/MI/miw06.xml Descriptions of these samples] are also available.

* The [http://www.nzetc.org/ NZETC] has a range of New Zealand and Pacific-Islands texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:
** Use of <revisionDesc> and <change> tags to implement workflow
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).

* A subset of [http://www.gutenberg.org/ Project Gutenberg] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.

* The [http://www.bvh.univ-tours.fr/ BVH] project (Virtual Humanistic Libraries) is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr/Epistemon/index.htm Epistemon]. These files are licenced under Creative Commons Attribution.

* The [[Perseus Project]] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.

* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI P4-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Some are now in P5, for example http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/swa-eng/swa-eng.tei

== See also ==
* [[TEI by example]]

Samples of TEI texts

2010-02-23T16:06:34Z

GabrielBodard: /* Texts */ finney = p5

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ''ala2004'' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/ala2004 Aphrodisias in Late Antiquity] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)

* [http://archimedespalimpsest.net/ Archimedes Palimpsest], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5

* [http://www.ota.ox.ac.uk/headers/2493.xml The Auchinleck Manuscript], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html EpiDoc Demo Website], a growing collection of sample [http://epidoc.sf.net/ EpiDoc XML] files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Format: TEI P4)

* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html ''IAph2007'' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)

* The [http://www.tei-c.org/Activities/MI/Samples/ Migration Samples] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "Manuscript Markup," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/Resources/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/Resources/U16.xsl transform], a [http://www.sbl-site.org/Resources/U16.css stylesheet] and a [http://www.sbl-site.org/Resources/U16.html web page] produced from the transcription by the transform. (Format: TEI P5)

* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html Samyukta Agama Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.

* The [http://www.tei-c.org/Activities/Workgroups/MI/Samples/ SGML-to-XML Migration Task Force] has made some of its case studies and samples available, with restricted permissions. These are mostly SGML P3-encoded files. [http://www.tei-c.org/Activities/Workgroups/MI/miw06.xml Descriptions of these samples] are also available.

* The [http://www.nzetc.org/ NZETC] has a range of New Zealand and Pacific-Islands texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:
** Use of <revisionDesc> and <change> tags to implement workflow
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).

* A subset of [http://www.gutenberg.org/ Project Gutenberg] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.

* The [http://www.bvh.univ-tours.fr/ BVH] project (Virtual Humanistic Libraries) is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr/Epistemon/index.htm Epistemon]. These files are licenced under Creative Commons Attribution.

* The [[Perseus Project]] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.

* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI P4-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Some are now in P5, for example http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/swa-eng/swa-eng.tei

== See also ==
* [[TEI by example]]

Samples of TEI texts

2010-02-23T15:40:59Z

GabrielBodard: /* Texts */ Archimedes Palimpsest

[[Category: Markup]]
[[Category: TEI:P4]]
[[Category: TEI:P5]]
Please add links below to any TEI sample texts that are freely available for use by developers working on TEI-related software. By listing the texts here you are allowing the developers the right to test their software with your texts, but are not necessarily licensing any other use of these texts. Developers should ask permission of the text owners should they wish to make any more in-depth use of these materials.

== Texts ==

* [http://insaph.kcl.ac.uk/ala2004/redist/inscriptions/inscriptions.zip ''ala2004'' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/ala2004 Aphrodisias in Late Antiquity] publication. The downloadable .zip archive contains 230 XML files, each containing an ancient Greek inscription, which validate to the version 4 of the [http://epidoc.sf.net/ EpiDoc] DTD (a TEI localization)--the DTD is also included in the archive. These files are licenced under [http://creativecommons.org/licenses/by/2.5/ Creative Commons Attribution], so please feel free to do whatever you like with them! (Format: TEI P4)

* [http://archimedespalimpsest.net/ Archimedes Palimpsest], XML files containing the transcriptions of the Archimedes text, released (like all the Palimpsest data and metadata) under Creative Commons Attribution 3.0 Unported. Texts validate to TEI P5. One XML file per folio page (scroll down list of hi-res photographs in each directory). Format: TEI P5

* [http://www.ota.ox.ac.uk/headers/2493.xml The Auchinleck Manuscript], made available by the [http://www.ota.ox.ac.uk/ Oxford Text Archive] contact [mailto:ota-info@rt.oucs.ox.ac.uk ota-info@rt.oucs.ox.ac.uk]. This text originates from the [http://www.nls.uk/auchinleck/ Auchinleck Manuscript Project] at the National Library of Scotland, please see their website for more contextual material. Format: TEI P5.

* [http://epidoc.cch.kcl.ac.uk/inscriptions/index.html EpiDoc Demo Website], a growing collection of sample [http://epidoc.sf.net/ EpiDoc XML] files, including examples from epigraphic, papyrological, and other ancient projects. XML downloadable from each transformed inscription. (Format: TEI P4)

* [http://insaph.kcl.ac.uk/iaph2007/inscriptions/xml-repo.html ''IAph2007'' (EpiDoc XML files)] from the [http://insaph.kcl.ac.uk/iaph2007/ Inscriptions of Aphrodisias (2007)] publication. There are approx 1500 XML files available (either in a single .zip or as individual files either downloadable or linkable directly for dynamic processing), each containing an ancient Greek or Latin inscription. All files validate to the [[EpiDoc]] DTD (version 5). These files are licensed under [http://creativecommons.org/licenses/by/2.0/uk/ Creative Commons Attribution (UK)], so please feel free to do exciting things with them. (Format: TEI P4)

* The [http://www.tei-c.org/Activities/MI/Samples/ Migration Samples] page on the main TEI website includes sample texts from (inter alia) the British National Corpus, the Thomas McGreevey Archive, Early English Books Online, Multext East, Documenting the American South, and the Women Writers Project which were prepared as part of the TEI P4 Migration Work Group, the purpose of which was to demonstrate how to migrate TEI P3 (SGML) to TEI P4 (XML). Most of the material here is therefore of a certain antiquity.

* [http://www.sbl-site.org/Resources/Resources_ManuscriptMarkup.aspx Files] referenced in Timothy J. Finney, "Manuscript Markup," in ''The Freer Biblical Manuscripts: Fresh Studies of an American Treasure Trove'' (ed. Larry W. Hurtado; SBLTCS 6; Atlanta: Society of Biblical Literature, 2006), 263-87. These include a partial [http://www.sbl-site.org/Resources/U16.xml transcription] of the Freer manuscript of Paul (Gregory-Aland I 016), a [http://www.sbl-site.org/Resources/U16.xsl transform], a [http://www.sbl-site.org/Resources/U16.css stylesheet] and a [http://www.sbl-site.org/Resources/U16.html web page] produced from the transcription by the transform.

* The [http://buddhistinformatics.chibs.edu.tw/BZA/bzaComCatWeb.html Samyukta Agama Project] at Dharma Drum Buddhist College provides access to its more than 1000 TEI source files. Click on any cluster and find the link to the TEI source at the bottom of each column. The files are in Chinese, Pali and Sanskrit. This is an ongoing project, planned to end in winter 2008. Once the project is concluded markup documentation, schemas and stylesheets will be made available at the website.

* The [http://www.tei-c.org/Activities/Workgroups/MI/Samples/ SGML-to-XML Migration Task Force] has made some of its case studies and samples available, with restricted permissions. These are mostly SGML P3-encoded files. [http://www.tei-c.org/Activities/Workgroups/MI/miw06.xml Descriptions of these samples] are also available.

* The [http://www.nzetc.org/ NZETC] has a range of New Zealand and Pacific-Islands texts. The texts are P5 encoded and the TEI is generally downloadable from the document table of contents. Features include:
** Use of <revisionDesc> and <change> tags to implement workflow
** <name> tag used extensively for personal, ship, place, organisation and work names (keyed to external authority at [http://authority.nzetc.org/])
** Use of xml:lang="en" and xml:lang="mi" for texts with English and Maori (plus small amounts of other languages)
** Page images, facsimile PDFs and typeset PDFs (some texts only, for example [http://www.nzetc.org/tm/scholarly/tei-JCB-001.html this letter])
** Document-by-document licensing, some documents under a creative commons license (licensing info not currently stored in the TEI).

* A subset of [http://www.gutenberg.org/ Project Gutenberg] is available as TEI, go to [http://www.gutenberg.org/catalog/world/search http://www.gutenberg.org/catalog/world/search] and select "TEI Text Encoding Initiative (tei)" as the file type.

* The [http://www.bvh.univ-tours.fr/ BVH] project (Virtual Humanistic Libraries) is a virtual library of high-quality digitised documents, offering a selection of Renaissance books located in the libraries of the Région Centre, Paris, Poitiers, Lyons, Troyes, etc. Three samples of TEI texts are proposed in html, pdf and xml/tei on [http://www.bvh.univ-tours.fr/Epistemon/index.htm Epistemon]. These files are licenced under Creative Commons Attribution.

* The [[Perseus Project]] makes its TEI P4 XML collections in Greek, Latin, and English available from http://www.perseus.tufts.edu/hopper/opensource under a Creative Commons Sharalike/Non-Commercial/Attribution license.

* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

== Dictionaries ==
* [[FreeDict]] is a repository of various TEI P4-encoded bilingual translating dictionaries on free licenses (http://www.freedict.org/). Some are now in P5, for example http://freedict.svn.sourceforge.net/viewvc/freedict/trunk/swa-eng/swa-eng.tei

== See also ==
* [[TEI by example]]

Past events

2009-02-02T12:36:29Z

GabrielBodard: moved past events from calendar

* From the calendar of TEI events
** (most recent first)

==TEI Members Meeting 21==

King's College London, November 6-8, 2008

website: http://www.cch.kcl.ac.uk/tei2008/

==TEI training at CESR in Tours==

The BVH (Bibliothèques Virtuelles Humanistes) Project
Initiation to digital heritage encoding
XML/TEI session - October 6-7, 2008 - Initiation 2
Purpose
This two-day session offers a second level initiation to TEI encoding, with a specific application to Early Modern documents (encoded texts and image display). Priority is given to students of master level, but the session is open to other volunteers. Examples will be taken mainly among printed digital heritage documents.

With the participation of Lou Burnard.

Previous training: basic tagging, notions of TEI-P5 (www.tei-c.org/Guidelines/P5/), reading of the TEI-Renaissance Manual (www.bvh.univ-tours.fr)- not yet in English.

Location: CESR, computing room
59, rue Néricault-Destouches
37000 Tours - France

Organisation : Pr Marie-Luce Demonet (responsible), Dr Toshinori Uetani, CESR
Information and registration (maximum 20 persons) +33 2 47 36 77 86 : marie-christine.jossec@univ-tours.fr; Lunch (6, 7 on reservation) : 12 euros (students 6 euros)
Registration fee : students, scholars, employees of the University François-Rabelais, CNRS : free
Non University François-Rabelais: 25 euros/ day.

==Digitale Editionen: Methodische und technische Grundfertigkeiten==

Summer School: Köln, September 1-5, 2008

website: http://www.zfms.uni-koeln.de/veranstaltungen/SummerSchool.php

==Digital Humanities==

Oulu, Finland, June 25-28, 2008

Website: http://www.ekl.oulu.fi/dh2008/

TEI-based panels/papers include:

* TEI Panel, 9.00-10.30 Friday June 27th
* Zanasi, Silvi, Pizziconi, Musolino, Clinical applications of computer-assisted textual applications, a TEI dream? 11.00 Friday June 27th
* Cummings, ENRICHing Manuscript Descriptions with TEI P5, 11.30 Friday June 27th
* Schlitz, The TEI as luminol: forensic philology in a digital age 16.30 Friday June 27th
* Ramsay, Zillig, Text analytics: a TEI format for cross-collection text analysis, 17.00 Friday June 27th
* Cummings, Converting St Paul: A new TEI P5 edition of The Conversion of St Paul using stand-off linking, 10.00 Saturday June 28th
* Eide, Ore, TEI and cultural heritage ontologies, 14.30 Saturday 28th June

==[[EpiDoc]] summer school==

King's College London, July 14-18, 2008

See: http://www.currentepigraphy.org/2008/04/21/epidoc-summer-school-july-14th-18th-2008/

==TEI summer school, OUCS, Oxford==

* XML, TEI, and beyond: July 21st-23rd 2008

This three-day course combines in-depth coverage of the latest version
of the Text Encoding Initiative (TEI) Recommendations for the encoding
of digital text with hands-on practical exercises in their
application. If you are a project manager, research assistant, or
encoder working on any kind of project concerned with the creation or
management of large amounts of digital text, this course is for you.

* XML processing using XSLT: July 24th-25th 2008

This is a two-day technical course is a practical guide to the use of
XSLT to do more than simply render your XML documents. Aimed at
project research assistants, encoders, and programmers, it provides
in-depth coverage of the principles and practice of the W3C's
extensible Stylesheet language, focussing on its use as a general
purpose text manipulation and processing language.

Interested? Please register as soon as possible, as places are
limited. The two workshops are independent of each other, but we're
pleased to announce a 20% discount is available if you register for
both.

For further information and booking, please visit
http://www.oucs.ox.ac.uk/rts/events/

== TEI MM 21 ==
* [http://www.lib.umd.edu/dcr/events/teiconference/index.html TEI Members' Meeting: TEI@20 -- 20 Years of Supporting the Digital Humanities]
** See the [[MS SIG Agenda 2008]]

'''See also:'''
* [[Current events]]
* [[Conferences]]


[[Category:Community]]

Current events

2009-02-02T12:34:42Z

GabrielBodard: removed past events

EpiDoc

2008-09-08T13:38:10Z

GabrielBodard: /* Links */ link to GLs

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the [http://www.eagle-eagle.it/ EAGLE] and [http://www.rzuser.uni-heidelberg.de/~gv0/ HGV] databases.

=== Tools ===

The EpiDoc community also produce several Open Source tools for use by editors of epigraphic (and related) XML editions. Among which:

* EpiDoc Standard Stylesheets (XSL for rendering HTML or TXT representations recogisable by traditional editors [http://epidoc.sourceforge.net/resources.shtml#xslt])
* Transcoder (Java tool for translating between Beta Code, Unicode NF C, NF D, and other encodings [http://epidoc.sourceforge.net/resources.shtml#transcoder])
* CHETC (python tool for converting conventional Leiden to EpiDoc XML [http://epidoc.sourceforge.net/resources.shtml#chetc])
* Crosswalker (abstractable, customizable tool for defining relationships between XML schemas from [http://epidoc.sourceforge.net/resources.shtml#crosswalker])

== Agenda ==

Concerete plan to move into conformant TEI P5 in Fall 2008 (some modifications to P5 already proposed).

== Links ==

*[http://www.stoa.org/epidoc/gl/5/ EpiDoc Guidelines] at Stoa
*[http://epidoc.sourceforge.net/ SourceForge project page]
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources]
*[http://epidoc.sourceforge.net/projects.shtml EpiDoc projects]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]

EpiDoc

2008-09-08T13:03:57Z

GabrielBodard: /* Agenda */ "desire" -> "concrete plan"

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the [http://www.eagle-eagle.it/ EAGLE] and [http://www.rzuser.uni-heidelberg.de/~gv0/ HGV] databases.

=== Tools ===

The EpiDoc community also produce several Open Source tools for use by editors of epigraphic (and related) XML editions. Among which:

* EpiDoc Standard Stylesheets (XSL for rendering HTML or TXT representations recogisable by traditional editors [http://epidoc.sourceforge.net/resources.shtml#xslt])
* Transcoder (Java tool for translating between Beta Code, Unicode NF C, NF D, and other encodings [http://epidoc.sourceforge.net/resources.shtml#transcoder])
* CHETC (python tool for converting conventional Leiden to EpiDoc XML [http://epidoc.sourceforge.net/resources.shtml#chetc])
* Crosswalker (abstractable, customizable tool for defining relationships between XML schemas from [http://epidoc.sourceforge.net/resources.shtml#crosswalker])

== Agenda ==

Concerete plan to move into conformant TEI P5 in Fall 2008 (some modifications to P5 already proposed).

== Links ==
*[http://epidoc.sourceforge.net/ SourceForge project page]
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources]
*[http://epidoc.sourceforge.net/projects.shtml EpiDoc projects]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]

SIG:MSS

2008-09-08T13:02:20Z

GabrielBodard: /* Manuscript Transcription */ added link to EpiDoc

== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==

=== News ===

Dear all,

We got quite a good number of responses to our call for an informal meeting of the SIG MS at the DH2008 in Oulu. We would like to invite everyone who is interested to meet on '''Friday, 27 June, after the last session at 17:45h'''. The meeting will be held in hall HU206 (that's one of the conference rooms).

At the meeting, we would like to report about the submissions we did for the TEI Members Meeting in November, to collate ideas for the all-day SIG workshop and to start the needed activities for that, including an update on the task groups. Any input on these beforehand is very welcome, too.

See you in Finland,
Elena, Amanda, Malte

=== Introduction ===

The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who wish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.

This SIG will explore a range of issues common to editing manuscripts, including:
# how to handle time based encoding
# how to record place based encoding
# how to encode fragments
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented
# issues of substitutions
# issues of variation
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)

It will do this by:
* running a mailing list on this topic
* assess the TEI and suggest improvements/alterations to the TEI-Council

The SIG is setup by:
* Elena Pierazzo of the University of Pisa (Italy)
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.

The SIG is convened by Elena Pierazzo who also manages the TEI-MS-SIG List

The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html

=== Activities ===

The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].

The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].

The third meeting of the SIG was held at Seventh Annual TEI Member's Meeting at University of Maryland, College Park, 3nd of November 2007. The agenda of the meeting can be found [[MS SIG Agenda 2007|here]]; the report can be found [[MS SIG Report 07|here]]. During the meeting several task forces were created to deal with specific problems: the task forces main page can be found [[MS task forces|here]].

=== Useful links ===

==== Manuscript Description ====

Projects, resources, guidelines concerning MS description.

* [http://www.tei-c.org/release/doc/tei-p5-doc/html/MS.html TEI P5: 13. Manuscript Description]
* [http://sunsite3.berkeley.edu/Scriptorium/ Digital Scriptorium] (see especially the [http://sunsite3.berkeley.edu/Scriptorium/technical/description_dtd.html DESCRIPTION DTD] page).
* [http://www.hab.de/forschung/projekte/master-e.htm MASTER - Interface format for the description of medieval manuscripts]
* [http://www.tei-c.org/Activities/MS/msw05.xml Reviews of the manuscript description chapter: A summary]

==== Manuscript Transcription ====

Projects, resources, guidelines concerning MS transcription.

* [http://www.cdlib.org/inside/diglib/stwg/ms/ CDL Encoding Guidelines for Manuscripts and Rare Books]
* [http://www.kantl.be/ctb/project/dalf/ DALF: Digital Archive of Letters in Flanders]
* [http://www.scriptorium.columbia.edu/ Digital Scriptorium] (see especially the [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/transcription_dtd/index.html TRANSCRIPTION DTD] and [https://www1.columbia.edu/sec/cu/libraries/bts/digital_scriptorium/technical/ds-xml/description_dtd/index.html DESCRIPTION DTD] pages).
* [[EpiDoc]], guidelines for transcribing ancient texts
* [http://skaldic.arts.usyd.edu.au/docs/guidelines/guide.html Guidelines for the electronic edition of the skaldic corpus]
* [http://web.uvic.ca/hrd/lydgate/pilot.htm Partial Transcription of John Lydgate's "Fall of Princes"]
* [http://webapp1.dlib.indiana.edu/newton/index.jsp The Chymistry of Isaac Newton]
* [http://gandalf.aksis.uib.no/menota/guidelines/ The Menota handbook]
* [http://www.newtonproject.ic.ac.uk/prism.php?id=1 The Newton Project] (see also [http://ahds.ac.uk/creating/case-studies/newton/index.htm The Newton Project: Implementing and Exploiting XML]).
* [http://www.whitmanarchive.org/guidelines/ The Walt Whitman Archive Encoding Guidelines for Poetry Manuscripts]
* [http://jefferson.village.virginia.edu/seenet/piers/protocoltran.html Transcriptional Protocols: Piers Plowman Electronic Archive and SEENET]
* [http://elec.enc.sorbonne.fr/chroniqueslatines/ Chroniques latines de Saint-Denis] : critical edition using TEI P4 (but we hope to migrate in P5 this year) : [http://elec.enc.sorbonne.fr/chroniqueslatines/xml/chroniquesstdenis.xml XML Files]
* [http://lemo.irht.cnrs.fr/43/43-12.htm Réflexions sur l'utilisation de la TEI pour encoder les sources diplomatiques] and [http://elec.enc.sorbonne.fr/cartulaireblanc/guidebalisage/ Guide du balisage du Cartulaire blanc] : two resources in French

[[Category:SIG|MSS]]

Current events

2008-09-06T13:59:52Z

GabrielBodard: added TEI in Tours

Past events

2008-09-06T13:57:43Z

GabrielBodard: moved several events over from current

* From the calendar of TEI events

==Digital Humanities==

Oulu, Finland, June 25-28, 2008

Website: http://www.ekl.oulu.fi/dh2008/

TEI-based panels/papers include:

* TEI Panel, 9.00-10.30 Friday June 27th
* Zanasi, Silvi, Pizziconi, Musolino, Clinical applications of computer-assisted textual applications, a TEI dream? 11.00 Friday June 27th
* Cummings, ENRICHing Manuscript Descriptions with TEI P5, 11.30 Friday June 27th
* Schlitz, The TEI as luminol: forensic philology in a digital age 16.30 Friday June 27th
* Ramsay, Zillig, Text analytics: a TEI format for cross-collection text analysis, 17.00 Friday June 27th
* Cummings, Converting St Paul: A new TEI P5 edition of The Conversion of St Paul using stand-off linking, 10.00 Saturday June 28th
* Eide, Ore, TEI and cultural heritage ontologies, 14.30 Saturday 28th June

==[[EpiDoc]] summer school==

King's College London, July 14-18, 2008

See: http://www.currentepigraphy.org/2008/04/21/epidoc-summer-school-july-14th-18th-2008/

==TEI summer school, OUCS, Oxford==

* XML, TEI, and beyond: July 21st-23rd 2008

This three-day course combines in-depth coverage of the latest version
of the Text Encoding Initiative (TEI) Recommendations for the encoding
of digital text with hands-on practical exercises in their
application. If you are a project manager, research assistant, or
encoder working on any kind of project concerned with the creation or
management of large amounts of digital text, this course is for you.

* XML processing using XSLT: July 24th-25th 2008

This is a two-day technical course is a practical guide to the use of
XSLT to do more than simply render your XML documents. Aimed at
project research assistants, encoders, and programmers, it provides
in-depth coverage of the principles and practice of the W3C's
extensible Stylesheet language, focussing on its use as a general
purpose text manipulation and processing language.

Interested? Please register as soon as possible, as places are
limited. The two workshops are independent of each other, but we're
pleased to announce a 20% discount is available if you register for
both.

For further information and booking, please visit
http://www.oucs.ox.ac.uk/rts/events/

== TEI MM 21 ==
* [http://www.lib.umd.edu/dcr/events/teiconference/index.html TEI Members' Meeting: TEI@20 -- 20 Years of Supporting the Digital Humanities]
** See the [[MS SIG Agenda 2008]]

'''See also:'''
* [[Current events]]
* [[Conferences]]


[[Category:Community]]

Current events

2008-09-06T13:57:33Z

GabrielBodard: moved several events out to past

Current events

2008-05-20T14:50:42Z

GabrielBodard: /* TEI summer school Oxford */

(In chronological order, nearest events first.)


==Digital Humanities==

Oulu, Finland, June 25-28, 2008

Website: http://www.ekl.oulu.fi/dh2008/

TEI-based panels/papers include:

* TEI Panel, 9.00-10.30 Friday June 27th
* Zanasi, Silvi, Pizziconi, Musolino, Clinical applications of computer-assisted textual applications, a TEI dream? 11.00 Friday June 27th
* Cummings, ENRICHing Manuscript Descriptions with TEI P5, 11.30 Friday June 27th
* Schlitz, The TEI as luminol: forensic philology in a digital age 16.30 Friday June 27th
* Ramsay, Zillig, Text analytics: a TEI format for cross-collection text analysis, 17.00 Friday June 27th
* Cummings, Converting St Paul: A new TEI P5 edition of The Conversion of St Paul using stand-off linking, 10.00 Saturday June 28th
* Eide, Ore, TEI and cultural heritage ontologies, 14.30 Saturday 28th June

==[[EpiDoc]] summer school==

King's College London, July 14-18, 2008

See: http://www.currentepigraphy.org/2008/04/21/epidoc-summer-school-july-14th-18th-2008/

==TEI summer school, OUCS, Oxford==

* XML, TEI, and beyond: July 21st-23rd 2008

This three-day course combines in-depth coverage of the latest version
of the Text Encoding Initiative (TEI) Recommendations for the encoding
of digital text with hands-on practical exercises in their
application. If you are a project manager, research assistant, or
encoder working on any kind of project concerned with the creation or
management of large amounts of digital text, this course is for you.

* XML processing using XSLT: July 24th-25th 2008

This is a two-day technical course is a practical guide to the use of
XSLT to do more than simply render your XML documents. Aimed at
project research assistants, encoders, and programmers, it provides
in-depth coverage of the principles and practice of the W3C's
extensible Stylesheet language, focussing on its use as a general
purpose text manipulation and processing language.

Interested? Please register as soon as possible, as places are
limited. The two workshops are independent of each other, but we're
pleased to announce a 20% discount is available if you register for
both.

For further information and booking, please visit
http://www.oucs.ox.ac.uk/rts/events/

==Digitale Editionen: Methodische und technische Grundfertigkeiten==

Summer School: Köln, September 1-5, 2008

website: http://www.zfms.uni-koeln.de/veranstaltungen/SummerSchool.php

==TEI Members Meeting 21==

King's College London, November 6-8, 2008

website: http://www.cch.kcl.ac.uk/tei2008/

'''See also:'''
* [[Conferences]]
* [[Past events]]

[[Category:Community]]

Current events

2008-04-29T10:56:02Z

GabrielBodard: added Köln summer school

Current events

2008-04-29T10:52:49Z

GabrielBodard: /* EpiDoc summer school */ added URL

User:GabrielBodard

2008-04-12T17:14:33Z

GabrielBodard: brackets

Dr Gabriel Bodard (TEI Council 2008-2009)

For more information see [http://wiki.digitalclassicist.org/User:GabrielBodard bio page on Digital Classicist wiki].

User:GabrielBodard

2008-04-12T17:14:16Z

GabrielBodard: New page: Dr Gabriel Bodard (TEI Council 2008-2009) For more information see http://wiki.digitalclassicist.org/User:GabrielBodard bio page on Digital Classicist wiki.

Dr Gabriel Bodard (TEI Council 2008-2009)

For more information see [[http://wiki.digitalclassicist.org/User:GabrielBodard bio page on Digital Classicist wiki]].

EpiDoc

2008-04-12T17:10:29Z

GabrielBodard: /* Epigraphic and papyrological metadata crosswalking */ fixed EAGLE link

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the [http://www.eagle-eagle.it/ EAGLE] and [http://www.rzuser.uni-heidelberg.de/~gv0/ HGV] databases.

=== Tools ===

The EpiDoc community also produce several Open Source tools for use by editors of epigraphic (and related) XML editions. Among which:

* EpiDoc Standard Stylesheets (XSL for rendering HTML or TXT representations recogisable by traditional editors [http://epidoc.sourceforge.net/resources.shtml#xslt])
* Transcoder (Java tool for translating between Beta Code, Unicode NF C, NF D, and other encodings [http://epidoc.sourceforge.net/resources.shtml#transcoder])
* CHETC (python tool for converting conventional Leiden to EpiDoc XML [http://epidoc.sourceforge.net/resources.shtml#chetc])
* Crosswalker (abstractable, customizable tool for defining relationships between XML schemas from [http://epidoc.sourceforge.net/resources.shtml#crosswalker])

== Agenda ==

Desire to move into conformant TEI P5 (even if that involves adding functionality to P5).

== Links ==
*[http://epidoc.sourceforge.net/ SourceForge project page]
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources]
*[http://epidoc.sourceforge.net/projects.shtml EpiDoc projects]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]

Current events

2008-04-12T17:09:00Z

GabrielBodard: order; EpiDoc; DH

Calendar

2008-04-05T14:51:01Z

GabrielBodard: /* Calendar of TEI events */ headings

==Calendar of TEI events==

===TEI Members Meeting 21===

King's College London, November 6-8, 2008
website: http://www.cch.kcl.ac.uk/tei2008/

===TEI summer school===

Oxford, July 21-25, 2008

Calendar

2008-04-04T15:15:01Z

GabrielBodard: New page: =Calendar of TEI events= ==TEI Members Meeting 21== King's College London, November 6-8, 2008 website: http://www.cch.kcl.ac.uk/tei2008/ ==TEI summer school== Oxford, July 21-25, 2008

=Calendar of TEI events=

==TEI Members Meeting 21==

King's College London, November 6-8, 2008
website: http://www.cch.kcl.ac.uk/tei2008/

==TEI summer school==

Oxford, July 21-25, 2008

EpiDoc

2008-04-04T15:10:18Z

GabrielBodard: /* Links */

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the [http://rds.yahoo.com/_ylt=A0geu6XgIPZHq28AckxXNyoA;_ylu=X3oDMTE0am1mdHRrBHNlYwNzcgRwb3MDMgRjb2xvA2FjMgR2dGlkA1lTMjE1XzExNg--/SIG=11eaie1cb/EXP=1207399008/**http%3a//www.eagle-eagle.it/ EAGLE] and [http://www.rzuser.uni-heidelberg.de/~gv0/ HGV] databases.

=== Tools ===

The EpiDoc community also produce several Open Source tools for use by editors of epigraphic (and related) XML editions. Among which:

* EpiDoc Standard Stylesheets (XSL for rendering HTML or TXT representations recogisable by traditional editors [http://epidoc.sourceforge.net/resources.shtml#xslt])
* Transcoder (Java tool for translating between Beta Code, Unicode NF C, NF D, and other encodings [http://epidoc.sourceforge.net/resources.shtml#transcoder])
* CHETC (python tool for converting conventional Leiden to EpiDoc XML [http://epidoc.sourceforge.net/resources.shtml#chetc])
* Crosswalker (abstractable, customizable tool for defining relationships between XML schemas from [http://epidoc.sourceforge.net/resources.shtml#crosswalker])

== Agenda ==

Desire to move into conformant TEI P5 (even if that involves adding functionality to P5).

== Links ==
*[http://epidoc.sourceforge.net/ SourceForge project page]
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources]
*[http://epidoc.sourceforge.net/projects.shtml EpiDoc projects]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]

EpiDoc

2008-04-04T15:10:08Z

GabrielBodard: /* Links */

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the [http://rds.yahoo.com/_ylt=A0geu6XgIPZHq28AckxXNyoA;_ylu=X3oDMTE0am1mdHRrBHNlYwNzcgRwb3MDMgRjb2xvA2FjMgR2dGlkA1lTMjE1XzExNg--/SIG=11eaie1cb/EXP=1207399008/**http%3a//www.eagle-eagle.it/ EAGLE] and [http://www.rzuser.uni-heidelberg.de/~gv0/ HGV] databases.

=== Tools ===

The EpiDoc community also produce several Open Source tools for use by editors of epigraphic (and related) XML editions. Among which:

* EpiDoc Standard Stylesheets (XSL for rendering HTML or TXT representations recogisable by traditional editors [http://epidoc.sourceforge.net/resources.shtml#xslt])
* Transcoder (Java tool for translating between Beta Code, Unicode NF C, NF D, and other encodings [http://epidoc.sourceforge.net/resources.shtml#transcoder])
* CHETC (python tool for converting conventional Leiden to EpiDoc XML [http://epidoc.sourceforge.net/resources.shtml#chetc])
* Crosswalker (abstractable, customizable tool for defining relationships between XML schemas from [http://epidoc.sourceforge.net/resources.shtml#crosswalker])

== Agenda ==

Desire to move into conformant TEI P5 (even if that involves adding functionality to P5).

=== Links ===
*[http://epidoc.sourceforge.net/ SourceForge project page]
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources]
*[http://epidoc.sourceforge.net/projects.shtml EpiDoc projects]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]

EpiDoc

2008-04-04T15:09:39Z

GabrielBodard: /* Tools */

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the [http://rds.yahoo.com/_ylt=A0geu6XgIPZHq28AckxXNyoA;_ylu=X3oDMTE0am1mdHRrBHNlYwNzcgRwb3MDMgRjb2xvA2FjMgR2dGlkA1lTMjE1XzExNg--/SIG=11eaie1cb/EXP=1207399008/**http%3a//www.eagle-eagle.it/ EAGLE] and [http://www.rzuser.uni-heidelberg.de/~gv0/ HGV] databases.

=== Tools ===

The EpiDoc community also produce several Open Source tools for use by editors of epigraphic (and related) XML editions. Among which:

* EpiDoc Standard Stylesheets (XSL for rendering HTML or TXT representations recogisable by traditional editors [http://epidoc.sourceforge.net/resources.shtml#xslt])
* Transcoder (Java tool for translating between Beta Code, Unicode NF C, NF D, and other encodings [http://epidoc.sourceforge.net/resources.shtml#transcoder])
* CHETC (python tool for converting conventional Leiden to EpiDoc XML [http://epidoc.sourceforge.net/resources.shtml#chetc])
* Crosswalker (abstractable, customizable tool for defining relationships between XML schemas from [http://epidoc.sourceforge.net/resources.shtml#crosswalker])

== Agenda ==

Desire to move into conformant TEI P5 (even if that involves adding functionality to P5).

==== Links ====
*[http://epidoc.sourceforge.net/ SourceForge project page]
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources]
*[http://epidoc.sourceforge.net/projects.shtml EpiDoc projects]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]

EpiDoc

2008-04-04T12:38:27Z

GabrielBodard: /* Epigraphic and papyrological metadata crosswalking */

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata for interchange with the major epigraphic and papyrological databases. The initial work on such crosswalking has been carried out with reference to the [http://rds.yahoo.com/_ylt=A0geu6XgIPZHq28AckxXNyoA;_ylu=X3oDMTE0am1mdHRrBHNlYwNzcgRwb3MDMgRjb2xvA2FjMgR2dGlkA1lTMjE1XzExNg--/SIG=11eaie1cb/EXP=1207399008/**http%3a//www.eagle-eagle.it/ EAGLE] and [http://www.rzuser.uni-heidelberg.de/~gv0/ HGV] databases.

=== Tools ===

(3) tools

== Agenda ==

Desire to move into conformant TEI P5 (even if that involves adding functionality to P5).

==== Links ====
*[http://epidoc.sourceforge.net/ SourceForge project page]
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources]
*[http://epidoc.sourceforge.net/projects.shtml EpiDoc projects]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]

EpiDoc

2008-04-04T10:26:52Z

GabrielBodard: history and summary; removed {stub}

'''EpiDoc''' represents a growing, global collaboration of humanists and information technologists (a.k.a., the 'EpiDoc Community') whose joint aim is the creation of flexible but rigorous standards and tools for the digital encoding and interchange of [[wikipedia:epigraphy|epigraphic]] documents.

== History ==
In 2000 Tom Elliott (then at UNC-Chapel Hill) published, in response to a call for open standards from the electronic publication committee of the Association Internationale d'Épigraphie Grecque et Latine, a set of guidelines for the encoding of classical Epigraphic Documents in TEI XML. Since then the EpiDoc DTD has been much revised and customised, largely through the application of the XML guidelines to a wide range of projects, not only Greek and Latin (Etruscan, Hebrew, Cuneiform...) inscriptions, but papyri, coins, seal impressions, medieval and early modern inscriptions, south-east Asian texts. In recent years EpiDoc development has moved very closely in parallel with TEI P5, such that although the EpiDoc DTD is built in P4 using Pizza Chef, many P5 elements and functionalities have been locally imported to the DTD customization files (notably <choice> and <msDesc>), and some EpiDoc customizations have been proposed to and incorporated in P5 usage (e.g. apparatus model, abbreviation usage, dating and range attributes).

== EpiDoc Activities and focus ==

=== Text Transcription ===

The primary focus of EpiDoc was originally the transcription of epigraphic text editions. It is a core philosophy of the EpiDoc guidelines that essential distinctions in the editing of ancient documentary texts are those defined in the [[wikipedia:Leiden Conventions|Leiden Conventions]], especially (although not exclusively) as articulated by [http://en.wikipedia.org/wiki/Leiden_Conventions#cite_note-1 Krummrey-Panciera].

In practice this means that of the many TEI recommendations for transcription of primary sources, critical apparatus, names and dates, etc., EpiDoc mandates a subset of these elements and sometimes even a single practice for the tagging of ancient texts.

=== Epigraphic and papyrological metadata crosswalking ===

The second major activity of the EpiDoc community has been to propose element/attribute combinations for the tagging of basic metadata

=== Tools ===

(3) tools

== Agenda ==

Desire to move into conformant TEI P5 (even if that involves adding functionality to P5).

==== Links ====
*[http://epidoc.sourceforge.net/ SourceForge project page]
*[http://epidoc.sourceforge.net/resources.shtml EpiDoc resources]
*[http://epidoc.sourceforge.net/projects.shtml EpiDoc projects]
*[http://www.digitalmedievalist.org/journal/4/bodard/#N10109 Description of EpiDoc in ''Digital Medievalist'']

[[Category:Community]]