[tei-council] Report on Vilnius meeting

Daniel O'Donnell daniel.odonnell at uleth.ca
Fri Mar 23 16:38:29 EST 2007


Can we have an extension on this then? I'd started encoding Lethbridge
guessing a procedure on analogy with person and Matthew's email, but I
see now there is a lot to digest--especially since my other idea was to
encode the Old Man River.

Would 03-25 be good for us all?

On Fri, 2007-03-23 at 12:41 +0000, Lou Burnard wrote:
> Apologies -- I am still hoping to get the material on places back online 
> by the weekend -- it got pushed off by other committments. The ndextra 
> document is still accessible at www.tei-c.org/oldDrafts/ndextra.html 
> (along with all the other old junk that used to be in Drafts) if you're 
> desperate...
> 
> 
> Arianna Ciula wrote:
> > The resource at http://www.tei-c.org/Drafts/ndextra.html is not 
> > available any more and the proposal made accessible for the TEI list at 
> > http://www.tei-c.org/Drafts/testnym.html doesn't contain all the new 
> > examples for Places but just the Nym section.
> > 
> > Any idea where I can find the former examples that have disappeared?
> > 
> > Arianna
> > 
> > Lou Burnard wrote:
> >> Christian Wittern wrote:
> >>> Matthew James Driscoll wrote:
> >>>>
> >>>> <listNym>
> >>>
> >>> does that mean you also proposa a <gi>listNym</gi> for TEI?
> >>>
> >>>
> >>
> >> Yes. Matthew's report doesn't mention that there is a draft ODD, 
> >> probably because I have not yet got round to putting it anywhere where 
> >> Council members can see it easily. But if you look in the P5/Test 
> >> directory on sourceforge, you will see a file called testndextra.odd, 
> >> which contains the current state of the draft.
> >>
> >> I've just put a copy of the HTML generated from this by Roma on the 
> >> website at http://www.tei-c.org/Drafts/ndextra.html -- will try to 
> >> keep this up to date as the draft progresses
> >>
> >>
> >>>> Our principal task at this meeting was to develop mechanisms for 
> >>>> encoding
> >>>> place-names, analogous to those which were developed for personal 
> >>>> names at
> >>>> the meeting in Oxford last year, which would allow for the recording of
> >>>> abstracted information about a place, such as map coordinate, GIS
> >>>> information etc., as well as variant forms of the name, in different
> >>>> languages (e.g. Praha, Prague, Praga) and/or different forms over 
> >>>> time (e.g.
> >>>> Lundunum, London). On the analogy with <person>, we propose a <place>
> >>>> element, which will usually contain at least one, and possibly several,
> >>>> <placeName> elements, followed by one or more <location> elements to 
> >>>> provide
> >>>> geographical and/or geo-political information about the location of the
> >>>> place. 
> >>>
> >>> Why would you need more than one <location>?  I had the impression 
> >>> that the place is what stays constant? Is it because it also stands 
> >>> in for the geopolitical information? 
> >>
> >> Because a place might be located in more than one way (e.g. by its 
> >> geopolitical status, or by its co-ordinates), and may also move its 
> >> location over time.
> >>> However, if we talk about administrative geography here, you will 
> >>> also have to account for changes in the size and super/sub components 
> >>> of a place and a way to link this to coordinates defining the 
> >>> polygon.  Would the tagset be up to this task?
> >>
> >> probably... because we embed GML!
> >>
> >>
> >> _______________________________________________
> >> tei-council mailing list
> >> tei-council at lists.village.Virginia.EDU
> >> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> > 
> 
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
-- 
Daniel Paul O'Donnell, PhD
Director, Digital Medievalist Project http://www.digitalmedievalist.org/
Associate Professor and Chair, Department of English
University of Lethbridge
Lethbridge AB T1K 3M4
Canada
Vox: +1 403 329-2378
Fax: +1 403 382-7191




More information about the tei-council mailing list