<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.text.tei.general">
    <title>gmane.text.tei.general</title>
    <link>http://blog.gmane.org/gmane.text.tei.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15549"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15543"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15541"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15540"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15534"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15531"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15484"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15483"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15481"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15473"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15472"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15471"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15442"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15438"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15436"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15435"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15433"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15422"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15417"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.text.tei.general/15416"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15549">
    <title>can a corpus have a facsimile?</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15549</link>
    <description>&lt;pre&gt;I find myself in a position where i have &amp;lt;teiCorpus&amp;gt; element and want to have a &amp;lt;facsimile&amp;gt;
child.   Why, you ask? because I have 2500 gravestones, which are "documents" in their
own right, so I have them  as a &amp;lt;TEI&amp;gt; each; but I also have a plan of the whole cemetery which
I represent as a &amp;lt;facsimile&amp;gt; with nice &amp;lt;surface&amp;gt;s and &amp;lt;zone&amp;gt;s. I want to wrap them all up together.

am I being silly? or should we allow &amp;lt;facsimile&amp;gt; as a child of &amp;lt;teiCorpus&amp;gt;?
--
Sebastian Rahtz      
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

&lt;/pre&gt;</description>
    <dc:creator>Sebastian Rahtz</dc:creator>
    <dc:date>2013-05-23T14:46:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15543">
    <title>encoding choices for a particular document in &lt;editorialDecl&gt;?</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15543</link>
    <description>&lt;pre&gt;hi

we would like to document, within each file, the choices we make regarding usage of TEI elements and attributes. Sometimes we even would like to list TEI alternatives for encoding the same thing, and why we chose one over the others

these are really meant for editors and developers so I suppose it would be better to store in the header (they are in no way part of body) 

i'm thinking &amp;lt;editorialDecl&amp;gt;

any thoughts, suggestions?

thanks :)



-------
andreas trianta(fillidis)
andreas&amp;lt; at &amp;gt;trianta.eu

resident SOB customer 
at thinking lpc

&lt;/pre&gt;</description>
    <dc:creator>Andreas Triantafillidis</dc:creator>
    <dc:date>2013-05-23T12:07:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15541">
    <title>Blackwell Companion to Digital Literary Studies</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15541</link>
    <description>&lt;pre&gt;The editors of The Companion to Digital Literary Studies, first published
by Blackwell in 2008, are pleased to announce that it has just been
released in paperback.

At $49.95, €36.00, and £29.99, it is now affordable for classroom use. Its
31 chapters -- ranging from ePhilology to e-Literature, from digital
poetry to cybertextuality -- are as provocative and pertinent now as when
the volume was first released. TEI is covered in many chapters.

For further details, and for instructors to request an evaluation copy,
please see
http://www.wiley.com/WileyCDA/WileyTitle/productCd-1118492277.html.

Susan Schreibman and Ray Siemens

&lt;/pre&gt;</description>
    <dc:creator>Susan Schreibman</dc:creator>
    <dc:date>2013-05-21T13:15:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15540">
    <title>ProDoc&lt; at &gt;DocEng 2013: Call for Submissions to the Doctoral Consortium</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15540</link>
    <description>&lt;pre&gt;--------------------------------------------------------------------
                            ProDoc&amp;lt; at &amp;gt;DocEng
   Doctoral Consortium at the ACM Symposium on Document Engineering
            http://www.doceng2013.org/doctoral-consortium/

Call for Submissions

* Submission Deadline: June 5, 2013 (24:00 CEST)

* Notification of Acceptance: June 20, 2013

--------------------------------------------------------------------

For the first time, the ACM Symposium on Document Engineering will
feature a doctoral consortium, called ProDoc&amp;lt; at &amp;gt;DocEng.

PhD students present their dissertation project and will get
feedback from a panel of senior researchers as well as from the
general audience.

ProDoc&amp;lt; at &amp;gt;DocEng is intended to provide constructive criticism and help
PhD students in formulating their research question, deciding about
methods and approaches to use, and creating further ideas.  It is a
good place to learn about how to conduct a dissertation project and to
learn about leading edge research, the results of which might be
presented at one of the next Symposia.  Participants of ProDoc&amp;lt; at &amp;gt;DocEng
register for DocEng 2013 and will thus be able to attend all sessions
of the Symposium.

ProDoc&amp;lt; at &amp;gt;DocEng will take place during the Symposium.  Each participant
will be allocated 10 minutes for presentation, followed feedback and
questions.  There will be no publication for ProDoc&amp;lt; at &amp;gt;DocEng.

You are not required to have an accepted paper/poster/demo for DocEng
2013 to be eligible for ProDoc&amp;lt; at &amp;gt;DocEng.  However, if you are author or
co-author of an accepted submission, we encourage you to present your
dissertation project at ProDoc&amp;lt; at &amp;gt;DocEng.

For participation, please provide a proposal, briefly outlining your
dissertation topic.  Please also state your affiliation or/and
employer, your main supervisor and your academic background.  See
below for details.

PhD students accepted for ProDoc&amp;lt; at &amp;gt;DocEng are eligible to apply for
Student Travel Awards, for details see:

&amp;lt;http://www.doceng2013.org/support-for-students&amp;gt;


*Submission process*

Submissions must be made electronically in PDF format by June 5,
2013, 24:00 CEST, via the easychair conference system:

&amp;lt;https://www.easychair.org/conferences/?conf=doceng2013&amp;gt;

Submissions must not exceed two pages and must conform to the ACM SIG
Proceedings format
&amp;lt;http://www.acm.org/sigs/publications/proceedings-templates&amp;gt;:

- State the working title and your name and your affiliation or/and
   employer in the header.

- State your main supervisor, your background (i.e., what kind of MA
   or MSc you obtained before, or what you are working on at the
   moment), when you started your PhD studies and when your thesis is
   planned to be completed.  If your institution has certain rules with
   respect to the duration of PhD studies or internal and external
   readers, please add this information.  Please also note if you are
   looking for a second supervisor.

- Then, describe your dissertation project including your research
   question, related work, and the current status of your work (i.e.,
   preliminary ideas, proposed approach, and results achieved so far).

- If you have already published on your topic, give references.

(Skip abstract and categories, and start with information on your
supervisor and personal background instead.)

The language of the consortium is English.  All submissions must be in
English.  Accepted submissions will not be published in the DocEng
2013 proceedings.


*Review process*

All submissions will be reviewed by two members of the ProDoc&amp;lt; at &amp;gt;DocEng
panel (to be announced).  The main evaluation criteria are: originality,
significance, maturity, and clarity.

Acceptance for the Doctoral Consortium is competitive in nature and is 
based on
the evaluation criteria above.


*Doctoral Consortium Chair*

Cerstin Mahlow, University of Konstanz, Germany
(cerstin.mahlow&amp;lt; at &amp;gt;uni-konstanz.de)

--
Sent by Tamir Hassan
University of Konstanz, Germany
Publicity Chair, DocEng 2013

&lt;/pre&gt;</description>
    <dc:creator>Tamir Hassan (DocEng13</dc:creator>
    <dc:date>2013-05-21T11:22:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15534">
    <title>Digital.Humanities&lt; at &gt;Oxford Summer School 2013</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15534</link>
    <description>&lt;pre&gt;Only a few weeks left to book!

Places for this year's Digital.Humanities&amp;lt; at &amp;gt;Oxford Summer School 
are filling up already, so book your place soon!  Visit 
http://digital.humanities.ox.ac.uk/dhoxss/2013/ for more 
information. If you are awaiting the results of local funding and 
want to to see whether your chosen workshop is almost full, email 
courses&amp;lt; at &amp;gt;it.ox.ac.uk to find out!

====
The Digital.Humanities&amp;lt; at &amp;gt;Oxford Summer School (DHOxSS) is an annual 
event for anyone working in the Digital Humanities. This year's 
Summer School will be held on 8 - 12 July, at the University of 
Oxford. If you are a researcher, project manager, research 
assistant, or student of the Humanities, this is an opportunity 
for you to learn about the tools and methodology of digital 
humanities, and to make contact with others in your field. You 
will be introduced to topics spanning from creating, managing, 
analysing, modelling, visualizing, to publication of digital data 
for the Humanities. Visit 
http://digital.humanities.ox.ac.uk/dhoxss/2013/ for more information.

With the Summer School's customisable schedule, you book on one 
of our five-day workshops, and supplement this by booking several 
guest lectures from experts in their fields.

The main five-day workshops this year are:

1. Cultural Connections: exchanging knowledge and widening 
participation in the Humanities
2. How to do Digital Humanities: Discovery, Analysis and 
Collaboration
3. A Humanities Web of Data: publishing, linking and querying on 
the semantic web.
4. An Introduction to XML and the Text Encoding Initiative
5. An Introduction to XSLT for Digital Humanists

There are a variety of evening events including a peer-reviewed 
poster session to give delegates a chance to demonstrate their 
work to the other delegates and speakers. The Thursday evening 
sees an elegant drinks reception and three-course banquet at 
historic Queen's College, Oxford!

DHOxSS is a collaboration for Digital.Humanities&amp;lt; at &amp;gt;Oxford between 
the University of Oxford's IT Services, the Oxford e-Research 
Centre (OeRC), the Bodleian Libraries, and The Oxford Research 
Centre in the Humanities.

If you have questions, then email us at courses&amp;lt; at &amp;gt;it.ox.ac.uk for 
answers.
More details at: http://digital.humanities.ox.ac.uk/dhoxss/2013/

James Cummings,
Director of DHOxSS

&lt;/pre&gt;</description>
    <dc:creator>James Cummings</dc:creator>
    <dc:date>2013-05-20T15:26:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15531">
    <title>Poetess Archive Question</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15531</link>
    <description>&lt;pre&gt;Dear All:

One of the PA editors sent me the following question, and I don't know how to answer it.

In eighteenth-century printed texts, a quoted bit has quotation marks at the beginning of every line, like this:
John F. Kennedy once said, "Ask
"not what your country can do
"for you but what you can do
"for your country." It was a really
good thing to say.

She is eliminating those introductory quotation marks, silently: should she indicate that in the quotation part of editorial declarations, or the normalization part?  Here follows what she intends to say, and her question:

Quotation marks that indicate block quotes have been silently eliminated. ... should it go under &amp;lt;quotation&amp;gt; after the declaration saying marks have been converted to entities or under &amp;lt;normalization&amp;gt; after the declaration saying catchwords and running titles have been eliminated?

Thanks for thoughts.
Best, Laura
--
Laura Mandell
Professor of English
Director, Initiative for Digital Humanities, Media, and Culture
Texas A&amp;amp;M University
440 LAAH, TAMU 4227
College Station, TX 77843-4227
(979) 845-8345
FAX: (979) 826-2292
mandell&amp;lt; at &amp;gt;tamu.edu
&amp;lt; at &amp;gt;mandellc

&lt;/pre&gt;</description>
    <dc:creator>Mandell, Laura</dc:creator>
    <dc:date>2013-05-20T14:23:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15484">
    <title>placeName types</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15484</link>
    <description>&lt;pre&gt;Dear all:

I don't know why it hasn't struck me before, but I'm finding myself bothered by the use of the "type" attribute on &amp;lt;placeName&amp;gt; and &amp;lt;geogName&amp;gt; that's modeled in the Guidelines (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html#NDPLAC E.g., type="settlement", type="city" and so forth).

It seems to me at the moment that there's a potential muddle here between two notions: "type of place" and "type of place name". I don't see any clear examples for the latter use case (e.g., "this is a type=fictitious place name (for a real place)" or "this is a type=former place name"). My knee-jerk reaction is that we shouldn't be glossing type of place on &amp;lt;placeName&amp;gt; at all; rather, that's a function for whatever markup or external resource the &amp;lt;placeName&amp;gt; is seen as referring to (i.e., that place indicated by the value of the &amp;lt; at &amp;gt;ref or &amp;lt; at &amp;gt;key attribute). But perhaps others would take a different view and offer an alternative approach, or suggest that both be allowed to exist side-by-side.

I poked around briefly in the list archives in case I missed an earlier discussion along these lines, but I didn't find anything. 

Thoughts? 

Tom

Tom Elliott, Ph.D.
Associate Director for Digital Programs and Senior Research Scholar
Institute for the Study of the Ancient World (NYU)
http://isaw.nyu.edu/people/staff/tom-elliott



&lt;/pre&gt;</description>
    <dc:creator>Tom Elliott</dc:creator>
    <dc:date>2013-05-17T18:10:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15483">
    <title>Introductory material for a primary source text</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15483</link>
    <description>&lt;pre&gt;Hi all,

I'd like to get a sense of how and where people typically encode 
substantial modern editorial content related to a primary source text. 
For instance, if you have such things as a Critical Introduction, or a 
lengthy Textual Note, where do you tend to put it?

My instinct is that this doesn't belong in the &amp;lt;text&amp;gt; along with the 
primary source transcription; mixing modern editorial content with the 
primary source seems completely wrong. Shorter notes obviously belong in 
the header in &amp;lt;notesStmt&amp;gt;, but the structure of &amp;lt;note&amp;gt; makes it 
inadequate for longer critical material (it can't contain &amp;lt;div&amp;gt; or 
&amp;lt;head&amp;gt;). &amp;lt;floatingText&amp;gt; is available in &amp;lt;note&amp;gt;, so that's one possible 
approach, but it seems wrong to use this in the header.

I'm inclined to place such material in a separate born-digital document 
and link the two together.

What do you typically do?

Cheers,
Martin

&lt;/pre&gt;</description>
    <dc:creator>Martin Holmes</dc:creator>
    <dc:date>2013-05-17T17:40:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15481">
    <title>2013 DARIAH-DE International Digital Humanities Summer School</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15481</link>
    <description>&lt;pre&gt;Dear TEIers,

 

The Göttingen Centre for Digital Humanities at the University of Göttingen,
Germany, is pleased to host the 2013 DARIAH-DE International Digital
Humanities Summer School.  This summer school will be a one-week crash course
in using the scripting language Python and its Natural Language Toolkit to
perform in-depth computational analysis of digital texts.  The summer school
will take place between August 19-23, 2013.  The instructors will be Mike
Kestemont &amp;lt;http://www.mike-kestemont.org/&amp;gt;  from the University of Antwerp
and Lars Wieneke &amp;lt;http://www.cvce.eu/le-cvce/equipe/lars_wieneke&amp;gt;  from the
CVCE &amp;lt;http://www.cvce.eu/&amp;gt; .  The summer school is aimed primarily at Ph.D.
and post-doctoral researchers and others with advanced knowledge of
humanities research.  The language of instruction and discussion will be
English.

More information on the summer school and information on how to apply can be
found here:
http://www.gcdh.de/en/events/calendar-view/2013-dariah-de-international-digit
al-humanities-summer-school/.  

We hope to hear from you soon!

 

Best,

 

Matt Munson

 

---

Matthew Munson

 

Georg-August-Universität Göttingen

Göttingen Centre for Digital Humanities (GCDH) Papendiek 16

37073 Göttingen

GERMANY

+49 (0)551-39-10 997

www: http://www.gcdh.de/en/people/team/matthew_munson/ 

 

&lt;/pre&gt;</description>
    <dc:creator>Munson, Matthew</dc:creator>
    <dc:date>2013-05-17T10:54:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15473">
    <title>Annotation of narrative sequences with TEI</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15473</link>
    <description>&lt;pre&gt;Hi,
I'm working on a literary text. I'd like to divide it in some narrative
sequences (text portions composed by time, place and actors). This division
is transverse to the editorial structure (paragraphs, chapters, ...); e.g.
it happens that a sequence starts with a chapter and ends with another one,
or that a chapter is splitted in more sequences.

My idea is to reference all the text elements covering a sequence within a
&amp;lt;span&amp;gt; tag.

Does make sense an annotation such as &amp;lt;span from="#chapter1"
to="#paragraph20"/&amp;gt;, where "chapter1" is the id of a div, and "paragraph20"
is the id of a paragraph inside another div?

I looked into the reference and it seems that TEI hasn't the rigth
attributes to express time, place and actors for my &amp;lt;span&amp;gt;. Can I extend
the &amp;lt;span&amp;gt; to declare new attributes? My proposal is something like:
&amp;lt;span from="#chapter1" to="#paragraph20" time="2004-11-04" place="
http://live.dbpedia.org/page/New_York_City" actors="
http://live.dbpedia.org/page/Barack_Obama"/&amp;gt;

Cheers,
   Riccardo
&lt;/pre&gt;</description>
    <dc:creator>Riccardo Tasso</dc:creator>
    <dc:date>2013-05-15T13:48:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15472">
    <title>Biblissima - Survey : XML editors for TEI/EAD</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15472</link>
    <description>&lt;pre&gt;Dear all,

As part of the Biblissima project, we are carrying out a survey on the user requirements for XML editors, especially for people doing TEI and/or EAD encoding. We would like to find out more about your habits and wishes, in order to develop tools that are best-suited to your needs. If you are involved with this kind of work, we would be pleased if you could answer our survey :

English version : http://www.biblissima-condorcet.fr/limesurvey/index.php/229321/lang-en

French version : http://www.biblissima-condorcet.fr/limesurvey/index.php/229321/lang-fr  

German version : http://www.biblissima-condorcet.fr/limesurvey/index.php/229321/lang-de

We invite you to transmit it as widely as possible to your colleagues, students or friends who use XML editor whether regularly or occasionally in the digital humanities.

With our grateful thanks,

The biblissima team.

----------------------------
Pool Biblissima
Campus Condorcet
3 rue de la Croix Faron
93210 Saint-Denis La Plaine
+33 (0)1 55 93 75 34
----------------------------

&lt;/pre&gt;</description>
    <dc:creator>Biblissima questionnaire</dc:creator>
    <dc:date>2013-05-15T13:15:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15471">
    <title>new version of TEI bibliography now available</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15471</link>
    <description>&lt;pre&gt;I am pleased to announce a major update to the TEI bibliography, 
available at:

http://www.tei-c.org/Support/Learn/tei_bibliography.xml

This document, created many years ago by the SIG on Education, has been 
revised and expanded over the years by contributions from a number of 
people. The citations are now stored in a Zotero group library, from 
which the data are exported and transformed into TEI &amp;lt;biblStruct&amp;gt;s using 
the Zotero plugin for Firefox (which incorporates code written by Stefan 
Majewski). Big thanks to Stefan, Sebastian Rahtz, and David Sewell for 
helping create the workflow for exporting.

Maintenance of the bibliography is being taken over by Arianna Ciula, 
who will periodically export from Zotero and update the page using XSLT, 
on behalf of the TEI Board of Directors. Additions and corrections to 
this bibliography are most welcome: please join the Zotero group 
(http://www.zotero.org/groups/tei) and add them directly, or email 
tei-bibliography&amp;lt; at &amp;gt;tei-c.org. We particularly welcome additions of 
references in languages other than English as well as to alternative 
forms of publications (e.g., forums and blogs) to enlarge the scope of 
material being represented.

--Kevin

&lt;/pre&gt;</description>
    <dc:creator>Kevin Hawkins</dc:creator>
    <dc:date>2013-05-15T01:15:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15442">
    <title>seeking help with segment of text crossing &lt;p&gt; and &lt;div&gt;</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15442</link>
    <description>&lt;pre&gt;Hello,
I am assisting with a manuscript project.  I’m new to TEI and looking for help concerning a text segment that crosses a large block of text.

The researcher’s  source document is a 17th century diary written in Spanish with annotations from the same period.  She will include her comments.



Interp and interGroup works well for what she wants to accomplish.  For one segment, the text crosses structure blocks.  As a place holder, the 2nd part of the segment is marked the same as the 1st part.   Is there a way to designate that the two parts are one segment and convey that it is same interpretation?



Here is the section of the text that crosses the large chunk.





&amp;lt;lb/&amp;gt;de poder enmendar mi mala vida y &amp;lt;seg ana="#vision1"&amp;gt;aſi Vna
&amp;lt;lb/&amp;gt;noche q entre otraſ m&amp;lt;hi rend="superscript"&amp;gt;s&amp;lt;/hi&amp;gt; . q me quito el ſueño el
&amp;lt;lb/&amp;gt;peligroso estado de mi conſienſia enpeſe con

… and more


&amp;lt;/p&amp;gt;

&amp;lt;/div&amp;gt;

&amp;lt;div n="2.2" type="segment"&amp;gt;
&amp;lt;p&amp;gt;
&amp;lt;lb/&amp;gt; &amp;lt;seg ana="#vision1"&amp;gt;Vnavoz q hablava ami ynterior y me deſia q Vna

… and more



&amp;lt;lb/&amp;gt;puede Dios echar por otro Camino maſ ſuave y pue
&amp;lt;lb/&amp;gt;de ſer eficaz p&amp;lt;hi rend="superscript"&amp;gt;a&amp;lt;/hi&amp;gt; mi Remedio.&amp;lt;/seg&amp;gt; No lo tubo ejeCuto





Do you know of projects that may have this characteristic?



Thanks!



Mary S. Alexander
Metadata Librarian/Associate Professor
Cataloging and Metadata Services Dept.
Box 870266
University of Alabama
Tuscaloosa, AL 35487

malexand&amp;lt; at &amp;gt;ua.edu&amp;lt;mailto:malexand&amp;lt; at &amp;gt;ua.edu&amp;gt;
voice: 205-348-1490
fax: 205-348-6358



&lt;/pre&gt;</description>
    <dc:creator>Alexander, Mary</dc:creator>
    <dc:date>2013-05-10T15:16:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15438">
    <title>Quotation and SemanticWeb URI</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15438</link>
    <description>&lt;pre&gt;Hi everybody,
   I'm a TEI newbie and I'm trying to annotate a novel for a project about
digital humanities.

I'd like to annotate dialogues in my text, and from TEI reference I've seen
the best tag should be the "quotation" &amp;lt;q type="speech"&amp;gt;.
In particular I'm interested in the "who" attribute, used to declare the
speaker. Inside the reference I read that each speaker should be declared
inside a document as an item, with its own xml:id.

I have an ontology (in owl/rdf) describing characters and their relations,
so to me it would be great to declare, as value for the "who" attribute,
the URI of my character.
For example it could be:
&amp;lt;q who="http://www.mydomain.org/novel.owl#person_1"&amp;gt;- Hello World! -&amp;lt;/q&amp;gt;

Can it be considered valid TEI?

Cheers,
   Riccardo
&lt;/pre&gt;</description>
    <dc:creator>Riccardo Tasso</dc:creator>
    <dc:date>2013-05-10T14:07:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15436">
    <title>teiHeader and CIP</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15436</link>
    <description>&lt;pre&gt;Hello,

I am required to insert a CIP record into the &amp;lt;teiHeader&amp;gt; of our digital
editions -- similarly as it appears in printed books. I wonder what is
the recommended place in the &amp;lt;teiHeader&amp;gt; to this scope. 

The CIP record is provided by the National library, prior to the
publication of the edition, as an unstructured paragraph(s) of text. So,
I basically need a simple &amp;lt;ab&amp;gt;, probably somewhere in the
&amp;lt;publicationStmt&amp;gt;? But non of the existing elements seems suitable for
CIP. 

I am sure that many others have dealt with this question earlier. Would
you kindly share your experience, please? 

Regards, 
Matija 


&lt;/pre&gt;</description>
    <dc:creator>Matija Ogrin</dc:creator>
    <dc:date>2013-05-10T13:36:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15435">
    <title>Slightly OT: how to use &lt;join&gt; with XSLT</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15435</link>
    <description>&lt;pre&gt;Dear all,
I'm encoding a poetic text which presents several problems due to 
multiple hierarchies, which is why I was planning to use a couple of 
&amp;lt;joinGrp&amp;gt;s and &amp;lt;join&amp;gt; to re-create, in a virtual fashion, lines and word 
groups (having used &amp;lt;w&amp;gt; to mark each single word in the text).

The student who's collaborating to the project and helping me with style 
sheets, however, is not sure how to produce something like &amp;lt;span 
class="line"&amp;gt; in HTML on the basis of &amp;lt;join&amp;gt;'s multiple targets. Could 
anyone point me to an example of XML text and XSLT code doing this? or 
explain how to do it?

Many thanks in advance!

All best,

R

&lt;/pre&gt;</description>
    <dc:creator>Roberto Rosselli Del Turco</dc:creator>
    <dc:date>2013-05-10T09:03:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15433">
    <title>DHQ: temporary moratorium on submissions</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15433</link>
    <description>&lt;pre&gt;This summer, Digital Humanities Quarterly will be moving its editorial operations to Northeastern University. During the transition period, we will observe a temporary moratorium on new submissions, to enable us to focus on a few infrastructural improvements.  The moratorium will last from May 15 through September 15, 2013. 

The journal's production work on articles and special issues already submitted will not be affected by the moratorium.  The journal will continue to publish as usual during this period.

Thanks to all for your patience during this transitional period, and we look forward to receiving your submissions in the fall!

best wishes, Julia

Julia Flanders
Editor in chief, DHQ
Director, Women Writers project

Please note my new email address, effective July 1
 j.flanders&amp;lt; at &amp;gt;neu.edu

&lt;/pre&gt;</description>
    <dc:creator>Julia Flanders</dc:creator>
    <dc:date>2013-05-09T18:21:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15422">
    <title>Duke Collaboratory for Classics Computing (DC3)</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15422</link>
    <description>&lt;pre&gt;Colleagues:

We are very pleased to announce the creation of the Duke Collaboratory for Classics Computing (DC3), a new Digital Classics R&amp;amp;D unit embedded in the Duke University Libraries, whose start-up has been generously funded by the Andrew W. Mellon Foundation and Duke University’s Dean of Arts &amp;amp; Sciences and Office of the Provost.

The DC3 goes live 1 July 2013, continuing a long tradition of collaboration between the Duke University Libraries and papyrologists in Duke’s Department of Classical Studies. The late Professors William H. Willis and John F. Oates began the Duke Databank of Documentary Papyri (DDbDP) more than 30 years ago, and in 1996 Duke was among the founding members of the Advanced Papyrological Information System (APIS). In recent years, Duke led the Mellon-funded Integrating Digital Papyrology effort, which brought together the DDbDP, Heidelberger Gesamtverzeichnis der Griechischen Papyrusurkunden Ägyptens (HGV), and APIS in a common search and collaborative curation environment (papyri.info), and which collaborates with other partners, including Trismegistos, Bibliographie Papyrologique, Brussels Coptic Database, and the Arabic Papyrology Database.

The DC3 team will see to the maintenance and enhancement of papyri.info data and tooling, cultivate new partnerships in the papyrological domain, experiment in the development of new complementary resources, and engage in teaching and outreach at Duke and beyond.

The team’s first push will be in the area of Greek and Latin Epigraphy, where it plans to leverage its papyrological experience to serve a much larger community. The team brings a wealth of experience in fields like image processing, text engineering, scholarly data modeling, and building scalable web services. It aims to help create a system in which the many worldwide digital epigraphy projects can interoperate by linking into the graph of scholarly relationships while maintaining the full force of their individuality.

The DC3 team is:

Ryan BAUMANN: Has worked on a wide range of Digital Humanities projects, from applying advanced imaging and visualization techniques to ancient artifacts, to developing systems for scholarly editing and collaboration.

Hugh CAYLESS: Has over a decade of software engineering expertise in both academic and industrial settings. He also holds a Ph.D. in Classics and a Master’s in Information Science. He is one of the founders of the EpiDoccollaborative and currently serves on the Technical Council of the Text Encoding Initiative.

Josh SOSIN: Associate Professor of Classical Studies and History, Co-Director of the DDbDP, Associate editor of Greek, Roman, and Byzantine Studies; an epigraphist and papyrologist interested in the intersection of ancient law, religion, and the economy.

http://www.stoa.org/archives/1736&lt;/pre&gt;</description>
    <dc:creator>Hugh Cayless</dc:creator>
    <dc:date>2013-05-08T16:23:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15417">
    <title>encoding some summary like parts in texts (called sootitr)</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15417</link>
    <description>&lt;pre&gt;Hello all,
sometimes we face with texts which has some parts displayed in a distinct way within main text which sometimes called (as I asked some people) sootitr (I don't know if they responded me exactly). That parts seems to be some summarization or collection of important points in the main text and may displayed everywhere near the related part (between lines or in margin or ...). This feature seems to be a common practice in newspapers and nowadays in some news sites and I saw that previously in some text books. I wanna ask that how we can encode such feature in TEI?
Regards, Saeed 

&lt;/pre&gt;</description>
    <dc:creator>Saeed Sarrafzadeh</dc:creator>
    <dc:date>2013-05-08T12:36:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15416">
    <title>[ann] A series of 3 webinars on XSLT development with oXygen</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15416</link>
    <description>&lt;pre&gt;Hello,

I would like to invite you to attend our XSLT development with oXygen 
webinars. We structured the XSLT development support in oXygen in 3 parts:

Part 1: Tomorrow, Wednesday, May 8th, between 11 AM and 12 PM EDT
Editing, Validation and Transformation
This covers the basics of XSLT support showing how to create a 
stylesheet from scratch to get a HTML report from XML data, step by step 
and outlining the oXygen functionality used during each step.
Details and registration link are available at
http://www.oxygenxml.com/events/2013/webinar_xslt_development_with_oXygen_Part1.html

Part 2: Wednesday, June 5th, between 11 AM and 12 PM EDT
Master Files, Modules and Refactoring
This explores what oXygen offers when you work with more than a single 
stylesheet file, when you have multiple modules. It shows also the views 
that provide insight into the stylesheet structure and how different 
components are used.
Details and registration link are available at
http://www.oxygenxml.com/events/2013/webinar_xslt_development_with_oXygen_Part2.html

Part 3: Wednesday, July 3rd, between 11 AM and 12 PM EDT
Debugging, Profiling and Unit-testing
In the 3rd part we will look into how you can identify issues with the 
debugger, how to identify performance problems with the profiler and how 
you can use the integrated XSLT unit testing.
Details and registration link are available at
http://www.oxygenxml.com/events/2013/webinar_xslt_development_with_oXygen_Part3.html

These events are free but registration is required.
I look forward to virtually meet many of you tomorrow!

Best Regards,
George
--
George Cristian Bina
&amp;lt;oXygen/&amp;gt; XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

&lt;/pre&gt;</description>
    <dc:creator>George Cristian Bina</dc:creator>
    <dc:date>2013-05-07T19:09:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.text.tei.general/15415">
    <title>PhD students in Digital Humanities at Passau</title>
    <link>http://comments.gmane.org/gmane.text.tei.general/15415</link>
    <description>&lt;pre&gt;Dear list,

In addition to the recently advertised PostDoc, I am searching for two
PhD students to join the Digital Humanities team at Passau as research
and teaching fellows.

Find more details in the job description:
http://www.uni-passau.de/fileadmin/dokumente/beschaeftigte/Stellenangebote/2013_04_WM_Prof_Rehbein_Doktoranden_engl_1_1.pdf

International candidates are welcome to apply in English, and German is
not a requirement for your research and teaching.

If you have any questions, please do not hesitate to get in touch with
me. The deadline for applications is May 27th.

Best regards,
Malte


&lt;/pre&gt;</description>
    <dc:creator>Malte Rehbein</dc:creator>
    <dc:date>2013-05-07T15:37:54</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.text.tei.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.text.tei.general</link>
  </textinput>
</rdf:RDF>
