[tei-council] Bug: make geo declaring

[Martin Holmes]

No, the consensus is on <geo> only. We're still arguing about 
<location>. But the ticket requests "multiple <geo> tags in a <location> 
element (which AFAIK has always been permitted), and the removal of the 
restriction for all <geo> tags to use the same coordinate system. This 
change would accomplish that. Of course, before closing the ticket we 
should check that all references and descriptive text are appropriately 
updated, but the addition of <geo> to att.declaring alone answers the 
ticket, I think, and should solve the submitter's problem.

Cheers,
Martin

On 12-01-12 12:42 PM, Kevin Hawkins wrote:
> Is there really consensus to make<location>  a member of att.declaring?
>    I don't see that.  --Kevin
>
> On 1/12/12 6:44 AM, Gabriel Bodard wrote:
>> There's been a little bit of discussion on the ticket, and it looks like
>> we're more or less agreed that we could reasonable make both<geo>   and
>> <location>   members of att.declaring. I'll implement this today if no one
>> objects, but I thought I'd ask here if anyone wants to weigh in on the
>> minor debate between Martin and myself first...
>>
>> Cheers,
>>
>> Gabby
>>
>> On 2012-01-10 16:30, Gabriel Bodard wrote:
>>> Dear Councillors,
>>>
>>> A reminder of a bug ticket that was submitted last November (just too
>>> late to make it into the last release, apparently), suggesting that
>>> <geo>    be added to att.declaring:
>>>
>>> http://purl.org/TEI/BUGS/3440771
>>>
>>> If everyone is agreeable, I'm happy to go ahead and make this change in
>>> the source. (I know it won't be released for a while now, but if I do it
>>> now we won't forget in future.)
>>>
>>> Best,
>>>
>>> Gabby
>>>
>>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)