search

tei-for-special-collections / consolidated-schema

0 stars 2 forks source link

layout: tei-breaking change to classes #31

Open mjhawkins opened 1 year ago

mjhawkins commented 1 year ago

att.typed was added to this element. Move to MC?

Dr-James-Freeman commented 1 year ago

What function does this serve in this context? Can you explain a little further? We (CUL + Bodleian) have made a number of customisations in layout and I don't know whether this pertains to one of them or not...

mjhawkins commented 1 year ago

This change has added the type and subtype attributes to <layout/>.

I have no idea what function it serves, but the main issue is whether we should be breaking the TEI data model, which any addition of non-namespaced attributes or elements is doing. Once we know what it's intended to record, we can investigate whether it can be done using non-modified TEI.

If it can't, we then need to decide whether we want to create these new attributes. If we do, then we should ensure that they aren't in the TEI namespace (ie. part of the TEI standard). This isn't difficult to do and it results in much clearer XML. If you are familiar with XML and were to read <layout cs:type="whatever">...</layout>, it's clear this cs:type isn't part of TEI. In contrast, there's no way anyone reading the following XML would know that we added type: <layout type="whatever">.

Dr-James-Freeman commented 1 year ago

I remember now: the purpose is to permit the description of the layout of more complex manuscripts, for instance glossed books. @type allows the cataloguer to differentiate between their description of the layout of the main text and their description of the gloss (although no control has been exercised yet over the values that accompany @type. For an example in which such a facility would be required, see MS Ii.3.21 on CUDL, where the text of De consolatione philosophiae is laid out in a different manner to the Middle English translation.

mjhawkins commented 1 year ago

We'll keep in the general schema for now. Do we want to raise this issue with TEI? They'll either agree or offer an alternative (non-breaking) way of encoding this information.