Activity for Elli Mylonas
-
Elli Mylonas created ticket #171
Improve Verse Lines page in GL
-
Home
-
Training
-
Training
-
page on EpiDoc and Linked Data
-
Pending developments in other parts of the epigraphic community such as FAIR epigraphy and epi-ont.
-
multiple origDate elements
-
Ask for examples on Markup so we can add them to the Guidelines, as well as an example of one template that handles mutliple origDates. Should it be in htm-tpl-struct-sample?
-
Index of TEI elements: enhancements
-
Clear citation practice for parts of EpiDoc resources
-
Discuss consolidation of repositories in future EDAG meeting.
-
Index of TEI elements: enhancements
-
Text direction: GL and XSL need improving
-
@thomaskollatz will test various configurations to see why/when the arrow indicating directionality appears or not.
-
Schema
-
Schema
-
Schema
-
Home
-
Home
-
LatestRelease
-
LatestRelease
-
space betwean words
-
Also, see the section on white space handing in the Epidoc Guidelines. And a better place to continue this conversation is probably the Markup LIst - where you can reach a broader audience. Closing ticket.
-
This particular project encoded words using the <w> tag. In order to see the complete source, you should download the complete EpiDoc file from the link at the very bottom of the page. The XML tag actually displays a more readable, but not complete encoding. Other projects don't leave whitespace after elements which are not at a word boundary, so for ex. they might have: <supplied reason="lost">αὐ</supplied>τοκράτωρ</lb>
-
examples not handled by stylesheets are confusing
-
https://epidoc.stoa.org/gl/latest/trans-ligature.html has been edited. Closing as the rendering and stylesheets update will be handled in Ticket 162.
-
Consider nested ab for formatting changes
-
EM to post on Markup List for feedback. - Epidoc avoids multiple ways of doing the same thing (<lb> with @rend vs <ab> - On the other hand, adding @rend to <lb> is odd, as it's not rendering the break, it's rendering the line. - This recommendation is treating <ab>as a surrogate for <line>but p rimarily for describing the original rendition.
-
EM to add explanation that stylesheets aren't rendering properly. Item 3 will be handled in Ticket 162.
-
examples not handled by stylesheets are confusing
-
examples not handled by stylesheets are confusing
-
examples not handled by stylesheets are confusing
-
with @sdigiulio made change to Provenance of the Text Bearing Object and Modern and Last Known Locations to include a reference to the TEI curatorialHist element and to provide attribute values for provenance when type="transferred". Status changed to pending so it can be looked at before closing, in case it needs corrections or additions. Otherwise, it can be closed and included in the next release.
-
Address custodial history in Guidelines
-
changes per FR151
-
ligature display for more than 2 letters
-
resp attribute not allowed on div element in Epidoc
-
If we want to add a [Home] button near the main title of a page, his requires figuring out how the over-ride of the TEI stylesheets works. It's not possible as far as I can tell, to add a link around the Epidoc logo with CSS It may be possible to kludge the currently hidden <h1 class="subtitle"> element, which already has a link to the index. That sounds awkward.
-
Document structured bibliography in GL
-
Made simple recommendations for some <div type="bibliogaphy" subtype="xxx"> values for the @subtype attribute , and for <bibl type="xxx"> close with commit 2822
-
few updates per FR82
-
When this ticket is addressed, the page should also have a brief mention of how to handle directionality when different languages are involved. At least a reference to the page on Mult-language texts (https://epidoc.stoa.org/gl/latest/trans-foreigntext.html )
-
Yes, this is an issue because most of us aren't using XSLT 3.0. We ran into it when we upgraded USEP recently and solved the problem by kludging string-join() to add a null second argument. It's a stopgap, but formats just fine.
-
Archive static copy of 2006 version in Stoa. Note that on Guidelines version.
-
Document structured bibliography in GL
-
EM to open discussion on Markup.
-
Closing. There is a mechanism for adding projects wtih documentation, and a respectable selection of projects to explore. Where ever we add tasks that we have to do on a regular basis, we should check the wiki for anything that needs to be updated, including this section. Also request contributions.
-
facilitate discovery of comparative projects
-
page for alternative readings in Transcription section
-
This has been accepted by Alessio Sopracasa (with Gabby's support) Not assigned because not in SF yet.
-
Advice on embedding supplied/other tags in words, names, etc.
-
This has been accepted by Martina Filosa (with Gabby's support) Not assigned because not in SF yet.
-
closing per discussion linked above
-
Provide for editorial suppression and addition as normalisation
-
Text direction: GL and XSL need improving
-
"Gentle Introduction" is out of date
-
Archive static copy of 2006 version in Stoa. Note that on Guidelines version. Check with Charlotte and Julia first.
-
Inline editorial correction of previous edition
-
Add basic functionality for INTERNAL apparatus to XSLT
-
I checked the TEI chapter Characters, Glyphs, and Writing Modes which recommends encoding a ligature-like juxtaposition as a glyph, similar to ligatures or unique forms of a character. This is what Scott is trying to avoid. The recommendation is in section 5.3 Annotating Characters. Most of the terminology and properties that are provided in the chapter for defining a character using the glyph element are also appropriate for single characters, or common ligatures. The property list does mention...
-
Examples
-
Note sent out to Markup, we got a few additions. We've all been adding or plan to add projects. This can probably be closed unless we want to make the request for projects a more regular appeal.
-
resp attribute not allowed on div element in Epidoc
-
close - this isn't a real issue, just a fluke in our setup.
-
This seems to be allowed so this is likely a non-issue. @ellimylonas and @sdigiulio will check again
-
resp attribute not allowed on div element in Epidoc
-
Document structured bibliography in GL
-
Inline editorial correction of previous edition
-
Menu on all pages reflecting table of contents
-
Address custodial history in Guidelines
-
I've added two projects, with very simple accompanying links to source files and documentation. Please look over and add your own projects (and/or add lables for useful infomraiton that could accompany this. @paregorios I think you'd like us to include something lke "Providence, RI, USA" or is "Brown. University" sufficient. I thought about a contact email, but those are usually on the website. The projects can also be linked to their page on the DC wiki if they have one.
-
Examples
-
Examples
-
Examples
-
Examples
-
Examples
-
Examples
-
Examples
-
Examples
-
Examples
-
Examples
-
Examples
-
Add @rend value of 'inserted' to `hi` element
-
EM will do some research on other TEI/epigraphic methods for handling this type of containment before the next ticket sprint.
-
@ellimylonas and @sdigiulio discussed this and although we think that it is unlikely many editors will want to characterize the authoritativeness and source of the editions in the bib., if they do @gethia has proposed using@source on<bibl> with a recommended set of values as follows: please suggest better terms. 1. "photograph" 2. "autopsy" (edition prepared from viewing original object) 3. "squeeze" (all forms of physical reproduction, including estampage and rubbings) 4. "facsimile" (microfilm,...
-
@ellimylonas and @sdigiulio discussed this and although we think that it is unlikely many editors will want to characterize the authoritativeness and source of the editions in the bib., if they do @gethia has proposed using@source on<bibl> with a recommended set of values such as follows: please suggest better terms. 1. "photograph" 2. "autopsy" (edition prepared from viewing original object) 3. "squeeze" (all forms of physical reproduction, including estampage and rubbings) 4. "facsimile" (microfilm,...
-
@sdigiulio and @ellimylonas looked at this issue. The link in the opening comment refest to the TEI <custodialHistory> element which is part of msDesc/adminInfo. We feel that Epidoc doesn't use this element, but instead, puts the same informatio in the origin and provenance elements which appear in the history section. Those seem fairly well developed. If we want to improve the <provenance> recommendations and example, we could rationalize the lists of values, which in some cases seem to repeat or...
-
EM and SDG will report back.
-
EM will take this on for 9.2
-
EM will review this for next release. Ask for help if necessary
-
Address custodial history in Guidelines
-
Will work on this for next release
-
examples: https://github.com/Brown-University-Library/iip-texts/blob/master/epidoc-files/elus0045.xml https://github.com/Brown-University-Library/iip-texts/blob/master/epidoc-files/mger0258.xml
-
@hcayless looks for example in Duke Databank. @ellimylonas does too.
-
issues with release process
-
Update, format, correct, supplement examples in GL
-
Update, format, correct, supplement examples in GL
-
Menu on all pages reflecting table of contents
-
Inline editorial correction of previous edition
-
CHETC: period identified as gap
1 >