[osis-core] castGroup?

Wed, 17 Mar 2004 20:25:31 -0500

Guys,

Working my way through the manual and found we never said anything about 
castGroup.

Content model is:

<xs:complexType name="castGroupCT">
	<xs:choice minOccurs="0" maxOccurs="unbounded">
		<xs:element name="head" type="headCT"/>
		<xs:element name="castItem" type="castItemCT"/>
</xs:choice>

Strikes me as being completely wrong.

Suggest:

<xs:complexType name="castGroupCT">
	<xs:sequence>
		<xs:element name="head" type="headCT" maxOccurs="1" minOccurs="0"/>
		<xs:element name="castItem" type="castItemCT" maxOccurs="unbounded"/>
</xs:sequence>

Recall that this is work information only, but provides a place to 
record the actors in a work for later short reference and analysis.

Don't see the need for more than one <head> element, but do think 
<castItem> should be unbounded.

Also, <castItem> is choice as well:

<xs:complexType name="castItemCT">
	<xs:choice minOccurs="0" maxOccurs="unbounded">
		<xs:element name="actor" type="actorCT"/>
		<xs:element name="role" type="roleCT"/>
		<xs:element name="roleDesc" type="roleDescCT"/>
</xs:choice>

Suggest:

<xs:complexType name="castItemCT">
	<xs:sequence>
		<xs:element name="actor" type="actorCT" maxOccurs="1"/>
		<xs:element name="role" type="roleCT" maxOccurs="unbounded"/>
		<xs:element name="roleDesc" type="roleDescCT" maxOccurs="unbounded"/>
</xs:sequence>

Note this breaks backwards compatibility but I don't know of any texts 
that have used this feature yet.

Not real sure why we left it as choice other than there was not a lot of 
discussion about it.

Suggestions?

Hope everyone is having a great day!

Patrick

-- 
Patrick Durusau
Director of Research and Development
Society of Biblical Literature
Patrick.Durusau@sbl-site.org
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model

Topic Maps: Human, not artificial, intelligence at work!