#32 <roleDesc> should be allowed as child of <castGroup>

DR
closed
Lou Burnard
4
2007-02-14
2004-09-03
Syd Bauman
No

The <castGroup> content model needs to allow <roleDesc>.

The attached PNG is an extract from the cast list of
Margaret
Cavendish’s _A_Piece_of_a_Play_. In it, two
<castGroup>s each contain two <castItem>s. However,
there is only one role description for each <castGroup>.

Ideally, only one <roleDesc> should be permitted in a
<castGroup>, but it should be permitted either before
or after the series of <castItem>s or <castGroup>s
(which may or may not all have <label>s depending on
whether feature request 1022100 is enacted).

In order to make that clearer, here I have expressed
that idea useing straight RelaxNG compact syntax (i.e.,
not a TEI syntax pattern, as there are no references to
the globally included elements nor the TEI class and
pattern indirection system). This presumes both a
desire for <roleDesc> as described here, and for
<label> as requested in 1022100.

# maybe label caststuff pairs
mlcp = (
( label, ( castItem | castGroup ) )+
|
( castItem | castGroup )+
)
element castGroup = {
head?,
(
( roleDesc, mlcp )
|
( mlcp, roleDesc? )
),
trailer?
}

Discussion

  • Syd Bauman
    Syd Bauman
    2004-09-03

    partial page image of a cast list

     
    Attachments
  • Syd Bauman
    Syd Bauman
    2006-09-25

    • priority: 5 --> 4
    • assigned_to: nobody --> sbauman
     
  • Lou Burnard
    Lou Burnard
    2006-12-02

    • assigned_to: sbauman --> louburnard
     
  • Lou Burnard
    Lou Burnard
    2007-02-01

    • milestone: --> DR
     
  • Lou Burnard
    Lou Burnard
    2007-02-14

    • status: open --> closed
     
  • Lou Burnard
    Lou Burnard
    2007-02-14

    Logged In: YES
    user_id=1021146
    Originator: NO

    There is an example already in the Guidelines of something very similar (see the existing description for <castGroup> and discussion in the text). In that case, the role description is given as a <head> element. I have revised the description also the relevant part of DR to permit the use of a <roleDesc> instead and also to discuss in what circumstances one might prefer one or the other approach.