There were enough typos in that message that I'll send this cleaned-up
The TEI Guidelines ambiguous regarding the FRBR "group 1" entities
(work, expression, manifestation, and item). Descriptive bibliography
practice varies greatly, and Julian's sample seems to indicate that this
particular bibliography will collate editions of a publication (here I
intentionally avoid the FRBR terminology in case it's too specific) in
an outline form.
The elements for encoding bibliographic citations -- bibl, biblStruct,
and biblFull -- are all inter-level elements that can be embedded inside
chunk-level elements such as <p> or as siblings of them. This gives you
some flexibility in your encoding.
When encoding a descriptive bibliography, the first question in my view
is whether the annotations for each entry are just phrases or whether
there is ever more than one paragraph in an annotation.
If there are only phrases, you could use <listBibl>, perhaps with
<head>s and nested <listBibl>s for various sections. Each entry would
be a <bibl> containing a mix of tags for components of bibliographic
references (the children of <bilbStruct>) and elements not typically
found in bibliographic references (like <emph>) for the description.
If there is more than one paragraph in the description of each entry,
you're going to have to organize this encoded document not using
<listBibl> but instead using one <div type="entry"> for each entry.
Inside of each entry would be <bibl> elements that, depending on the
structure of the source document, either would be siblings of <p>s
containing the description or would be children of them.
Or, as others have suggested, you use the msDesc module, and its typical
encoding structure, in order to gain access to specific elements used in
In any case, as you can see, I recommend using <bibl> instead of
<biblStruct> or <biblFull>. When you are attempting to replicate a
source document, with its inconsistencies, rather than creating a
born-digital bibliography, it's the only workable option. On the other
hand, if you are trying to create a new edition of this bibliography,
with a regularized structure, you could try to use <biblStruct> or even
<biblFull>. Instead, I recommend that you consider sticking with <bibl>
but developing a TEI customization that includes Schematron rules to
check the structure of each <bibl> to make sure it has all the expected
components. In that way it will end up working like <biblStruct> in
enforcing some structural requirements.