Print

Print


Sigh. Auto correction is a two edged sword which I haven't found out how to switch off on this gadget, I meant of course the gi element....




Sent from my Samsung Galaxy Tab®|PRO


-------- Original message --------
From: Piotr Bañski
Date:2015/11/25 15:51 (GMT+00:00)
To: Lou Burnard ,[log in to unmask]
Subject: Re: foliation - manuscript linking - list of elements

> Hope this helps!

It sure does. Especially the last point should help TEI encoders to
bravely go where no markup has gone before... Any other new elements
that you guys forgot to report on in Lyon? ;-)

Cheers,

   P.

On 25/11/15 16:28, Lou Burnard wrote:
> 1. There is ongoing discussion in the technical council and the ms sig
> about structuring the content of the foliation element better, but for
> the moment nothing precise has been agreed. See discussion under the
> subject on the ms sig list last week.
>
> 2. The surrogates element could be used to indicate any other digital or
> non digital edition of the ms being described. Alternative metadata
> records might be included or refrenced recordHist if they are part of
> the source for your ms Desc
>
> 3. The tagsDecl element is provided for this purpose. But if you prefer
> to use encodingDesc you might find it easier to use the girls element to
> tag element names rather than a c data section.
>
> Hope this helps!
>
>
>
> Sent from my Samsung Galaxy Tab®|PRO
> -------- Original message --------
> From: David Gniffke
> Date:2015/11/24 22:04 (GMT+00:00)
> To: [log in to unmask]
> Subject: foliation - manuscript linking - list of elements
>
> Dear list,
>
> for a project dealing with a digital edition of a french
> fifteenth-century treatise on obsequies, we need (as starters in this
> issue) some help regarding three questions:
>
> 1. As far as we know, the element <foliation> works with prose. Is there
> any preferred option to articulate in a machine processing way (e.g.
> with attributes) the foliation/pagination and the full number of
> folio/pages of a volume?
>
> 2. We would like to set links to digitised manuscripts and catalogue
> descriptions in the <msDesc>, as part of the header. The combination
> <locus facs=“http....“/> seems to relate only to a specific page of a
> digitised manuscript. How do we express a linking to a full digitised
> manuscript or an online catalogue description in a most convenient and
> common way?
>
> 3. As part of the header and introduction of the edition, we would like
> to list the elements used with a short explanation as part of the
> <encodingDesc>, in order to keep the work transparent for users. There
> is no suggestion in the TEI Guidelines. Is it completely uncommon or is
> there already an established way doing this? We tried a structure
> containing <p>, <list>, <item> and <!CDATA[<*element>]]>.
>
> We would be pleased and thankful if you had an advice for one or even
> all questions!
>
> For more information about our project, see
>
> - Project (German):
> <http://www.uni-muenster.de/Geschichte/histsem/JPGHuSMA/forschen/Obsequientraktat.html>http://www.uni-muenster.de/Geschichte/histsem/JPGHuSMA/forschen/Obsequientraktat.html
>
> - Blog Post with English summary:
> <https://heraldica.hypotheses.org/2511>https://heraldica.hypotheses.org/2511
>
> [log in to unmask]
> [log in to unmask]
>
> Best regards,
>
> David Gniffke
>
> (and supervisor Prof. Thorsten Hiltmann)
>
> --
> David Gniffke, M.A.
> Westfälische Wilhelms-Universität Münster
> Lehrstuhl für Mittelalterliche Geschichte III
> Domplatz 20-22
> 48143 Münster
> [log in to unmask]
> http://www.uni-muenster.de/Geschichte/histsem/MA-G/L3/organisation/gniffke.html
>
>
>
> ------------------------------------------------------------------------
> Avast logo <https://www.avast.com/antivirus>  
>
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> www.avast.com <https://www.avast.com/antivirus>
>
>