One text over multiple codicological units #1805
-
BGV009 is a composite MS containing the Vita and Miracles of ʾEwosṭātewos. It has three codicological units p1, p2, and p3.
Please note that I had to state I do not know if my solution is the ideal one for such cases. In most cases textual units are simple submultiples of codicological units, so that the codicological subvidision forms the upper level and the textual subdivision the lower level, but here there's an overlap between the codicological and the textual sequences. Also, how can this phenomenon be visualized in a printed output? PS I am assigning also Thea for she is experienced in encoding and might have encountered a similar case |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Dear @MassimoVilla , I would have done just like you did, and I would have explained perhaps the same you are writing here in the record itself. <relation active="BGV009#p1" name="sdc:constituteUnite" passive="BGV009#UniProd1"/>
<relation active="BGV009#p1" name="sdc:constituteUnite" passive="BGV009#UniMat1"/>
<relation active="BGV009#p2" name="sdc:constituteUnite" passive="BGV009#UniProd2"/>
<relation active="BGV009#p2" name="sdc:constituteUnite" passive="BGV009#UniCont1"/>
<relation active="BGV009#p3" name="sdc:constituteUnite" passive="BGV009#UniProd2"/>
<relation active="BGV009#p3" name="sdc:constituteUnite" passive="BGV009#UniMat2"/>
<relation active="BGV009#UniProd1" name="sdc:undergoesTransformation" passive="BGV009#tr1"/>
<relation active="BGV009#UniProd2" name="sdc:undergoesTransformation" passive="BGV009#tr1"/>
<relation active="BGV009#tr1" name="sdc:hasTransformationModel" passive="sdc:A2">
<desc>This a transformation A2 Addition of material support and content.</desc>
</relation> In terms of presentation in print, this encoding can be used prioritizing content or units as desired, and can be made into a static rule. e.g. listing contents and grouping them by |
Beta Was this translation helpful? Give feedback.
-
Dear Pietro, thank you for your detailed reply. I will discuss the most convenient solution in terms of visualization in print (i.e. whether to prioritize content or units) together with the other members of our project. I am sure that even though we (at least I) do not appreciate now the full implications of the two options, everything will be clearer after a first try with the PDF package. |
Beta Was this translation helpful? Give feedback.
-
I think more than optional these encodings are incremental. you can simply do as you did, or add an additional msPart or add that and the relations, or only add the relations. It is all a matter of desired precision. for the PDF we will use what we have. If this encoding looks fine for you I would like to use it for an example in the Guidelines. |
Beta Was this translation helpful? Give feedback.
-
Of course you can use my example in the Guidelines and provide all the possible incremental encodings, i.e. just as I did, with the additional msPart and/or with the relations. I am inclined to add both the additional msPart and the relations in my record. |
Beta Was this translation helpful? Give feedback.
Dear @MassimoVilla , I would have done just like you did, and I would have explained perhaps the same you are writing here in the record itself.
Additionally, because there is no assumption AFAIK that a msPart is defined on the basis of a material unit of production, you could have, for example a production unit, thus a msPart, which only contains your text and is defined on the basis of content.
you would have, e.g.
msPart[@xml:id='p1']
with themsItem[@xml:id='p1_i3']
as above, amsPart[@xml:id='p2']
with themsItem[@xml:id='p2_i1']
which is your complete text, this msPart not having further definition of support and amsPart[@xml:id='p3']
with themsItem[@xml:id='p3_i1']
which lists th…