[tei-council] [TEI-notify] SF.net SVN: tei:[9835] trunk/P5/Source/Specs
Pierazzo, Elena
elena.pierazzo at kcl.ac.uk
Mon Nov 28 16:48:56 EST 2011
It may be a mess, I agree, but at the end of the day we always said that
<line> is syntactic sugar for <zone type="line">, so I think this makes a
lot of sense, actually.
By the way, I have asked for having <zone> available within <line> since
at least last year when I encoded the examples fro Zadar: glad to see that
it finally makes sense to someone else, thanks Lou!
Best
Elena
-------
Dr Elena Pierazzo
Lecturer in Digital Humanities
Chair of the Teaching Committee
Department of Digital Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL
Phone: 0207-848-1949
Fax: 0207-848-2980
elena.pierazzo at kcl.ac.uk
http://www.kcl.ac.uk/ddh
On 28/11/2011 16:36, "Martin Holmes" <mholmes at uvic.ca> wrote:
>I'll have a good look at the Bovelles example when I get a chance. But I
>do think this will lead to rather a big mess. It'll now be legal to have
>lines containing zones containing surfaceGrps containing surfaces
>containing zones containing lines, won't it?
>
>Cheers,
>Martin
>
>On 11-11-28 08:18 AM, Lou Burnard wrote:
>> Yes, redoing the bovelles example made me realise that we have to permit
>> zones with lines. Horrible, I agree, but there's no other way of
>> transcribing the content of a zone which happens to be inside another
>> zone you're already transcribing. Consider the "pendans" zone.
>>
>> (Yes, I knew I screwed up the commit the first time round... hope it;s
>> right this time!)
>>
>>
>>
>> On 28/11/11 16:12, Martin Holmes wrote:
>>> Is this right -- zones within lines? I don't remember anything about
>>> this. Lines within zones certainly, but I thought that had been enacted
>>> a while ago.
>>>
>>> On 11-11-28 08:00 AM, louburnard at users.sourceforge.net wrote:
>>>> Revision: 9835
>>>> http://tei.svn.sourceforge.net/tei/?rev=9835&view=rev
>>>> Author: louburnard
>>>> Date: 2011-11-28 16:00:19 +0000 (Mon, 28 Nov 2011)
>>>> Log Message:
>>>> -----------
>>>> change content model to permit zones within lines
>>>>
>>>> Modified Paths:
>>>> --------------
>>>> trunk/P5/Source/Specs/line.xml
>>>> trunk/P5/Source/Specs/zone.xml
>>>>
>>>> This was sent by the SourceForge.net collaborative development
>>>>platform, the world's largest Open Source development site.
>>>>
>>>>
>>>>
>>>>-----------------------------------------------------------------------
>>>>-------
>>>> All the data continuously generated in your IT infrastructure
>>>> contains a definitive record of customers, application performance,
>>>> security threats, fraudulent activity, and more. Splunk takes this
>>>> data and makes sense of it. IT sense. And common sense.
>>>> http://p.sf.net/sfu/splunk-novd2d
>>>> _______________________________________________
>>>> TEI-notify mailing list
>>>> TEI-notify at lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/tei-notify
>>>>
>>>
>>
>> .
>>
>
>--
>Martin Holmes
>University of Victoria Humanities Computing and Media Centre
>(mholmes at uvic.ca)
>--
>tei-council mailing list
>tei-council at lists.village.Virginia.EDU
>http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
>PLEASE NOTE: postings to this list are publicly archived
More information about the tei-council
mailing list