CR 1.8 Align behavior ID and STRUCTID requirements with actual practice

Currently both ID and STRUCTID are required attributes on the behavior element. Yet, at least I believe, in typical cases only one or the other would be required. The ID attribute, but not the STRUCTID attribute, would be necessary if the behavior element represents a transformFile behavior. In this case the TRANSFORMBEHAVIOR attribute on the pertinent transformFile element would reference the ID attribute value on the pertinent behavior. But unless this behavior also pertained to one or more div's in the structMap, the STRUCTID attribute would have no meaning here. Conversely, if a behavior applies to one or more div's in the METS structMap, then the STRUCTID element is needed to identify the div's to which the behavior pertains. But in this case a behavior ID attribute would not be necessary. When behaviors pertain to the structMap div's the direction of the link is from behavior to div(s), not vice versa.

While providing an ID attribute value when one is not strictly needed probably isn't a big deal, having to provide a STRUCTID attribute when one isn't needed would be misleading. Therefore I recommend that both ID and STRUCTID be made optional on the behavior element.

Submitted by Rick Beaubien