Scrolls

We treat scrolls in the same way as codices and any other written artefacts, and only add in <objectDesc>↗ the value Scroll for @form. However, there are several specific features of encoding the descriptions of scrolls.

Since the scrolls are sewn together mostly of several parchment strips, there is a possibility of assigning <xml:id>↗s to single strips and of a consistent encoding of their sizes, as follows:

                        <dimensions type="outer" unit="mm">
                              <height>1590</height>
                           </dimensions>
                           <dimensions type="outer" unit="mm" xml:id="strip1">
                              <height>486</height>
                              <width>100</width>
                           </dimensions>
                           <dimensions type="outer" unit="mm" xml:id="strip2">
                              <height>588</height>
                              <width>120</width>
                           </dimensions>
                           <dimensions type="outer" unit="mm" xml:id="strip3">
                              <height>540</height>
                              <width>97</width>
                           </dimensions>
             

The assigned <xml:id>↗s can be referenced to while encoding other features. For example:

                    <layout columns="2" writtenLines="68" corresp="#strip1">
                      </layout>
                  

When structuring the text transcription of your scroll for referencing you may consider to use specific <div>↗s for recto and verso.

                    <div type="edition">
                        <div type="textpart" subtype="recto">
                            ...
                        </div>
                        <div type="textpart" subtype="verso">
                            ...
                        </div>
                    </div>
                

If you have <lb>↗ inside these divisions you will of course be able to use them as a referencing structure.

                    <ref cRef="MyScroll1.recto.12"></ref>
                

The same method can be used if desired to encode parchment strips, however it is likely that hierarchies problems will arise, it is thus advisable to use a simple <milestone unit="parchmentStip">↗ with @n. This will not become a referencing structure in the BM application but will allow you to encode in any point of the text where this is convenient the occurrence of this change. While a page break occurs only in one point, this type of change, as the one of block of stone for a running architectural inscription, for example, are likely to occur several times in one transcription. You will have where convenient this <milestone>↗ as many times as needed (with the same @n).

It is generally enough to encode the text of the inscription in the file, but there are cases in which you might need to separate the content from the support description, in which case, simply use a work record for the content and place there the edition of the text.