I think we could just chain together @type values (for instance), like this:

<persName type="labourer"> ->

<name type="person labourer">

Any problem with that? It's not lossy, really. The stylesheets would 
have to be amended in some places so that they were looking for an @type 
_containing_ a particular value rather than _equal to_ a particular 
value, but that's not really problematic.


On 11-08-25 06:57 AM, Sebastian Rahtz wrote:
> On 25 Aug 2011, at 14:26, Syd Bauman wrote:
>> Martin has pointed out the quintessential hole in Sebastian's
>> (excellent) idea. Unless we bring back TEIform= (which I am *not*
>> suggesting), it's actually going to be difficult to find agreement on
>> how to represent the concept "this is a<tei:name type='person'>  that
>> in tei_all would have been a<tei:persName type='laborer'
>> subtype='unemployed'>'.
> well, we could add a sort of hidden global attribute @equiv,
> like the old TEIform, which we could use.
> we're all thinking out loud here, but locked in a room
> for a bit, I am fairly sure we could come up with a schema
> to annotate  (finger in air) 200 out the 500 TEI elements to
> say they can safely be "80ed" to one of the other 300.
> --
> Sebastian Rahtz
> Head of Information and Support Group
> Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
> Sólo le pido a Dios
> que el futuro no me sea indiferente

Martin Holmes
University of Victoria Humanities Computing and Media Centre
([log in to unmask])