[tei-council] att.typed and syntactic sugar

[Martin Holmes]

Hi Kevin,

I think the basis of the confusion is in your sentence:

"Alternatively, use the attribute to create syntactic sugar for another 
TEI element."

Actually, it's the other way round, isn't it? <person> is syntactic 
sugar for <name type="person">, not the reverse. You don't use the @type 
attribute to create syntactic sugar for an element; you could devolve 
the syntactic sugar (if you see what I mean) by converting <person> to 
<name type="person">.

This is based on my assumption that "syntactic sugaring" goes in only 
one direction: <name type="person"> is the simpler form (requiring a 
smaller schema with fewer elements and attributes), while <person> is 
the sugared form (a bit less verbose, so "sweeter" to use, but requiring 
a larger schema with an extra element).

Cheers,
Martin

On 11-11-30 03:02 PM, Kevin Hawkins wrote:
> The December 2 deadline for implementing tickets so that Sebastian can
> produce a release this month is rapidly approaching, but I'm still not
> sure how to complete this ticket.  Should this be postponed for further
> discussion during the next Council meeting?
>
> On 11/26/2011 9:02 PM, Kevin Hawkins wrote:
>> Colleagues,
>>
>> I was trying to implement:
>>
>> https://sourceforge.net/tracker/index.php?func=detail&aid=3064014&group_id=106328&atid=644065
>>
>>
>> but realized I don't quite understand what we had in mind for our advice
>> on syntactic sugar. I've added a comment with my question. Could anyone
>> who understands this weigh in? Thanks,
>>
>> Kevin

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