On 11/2/12 6:32 AM, Roberta Presta wrote:
> Il 01/11/2012 17:57, Paul Kyzivat ha scritto:
>> On 10/31/12 6:42 AM, Roberta Presta wrote:
>>
>>>           <xs:choice>
>>>               <xs:sequence>
>>>                <xs:element name="spatialInformation"
>>> type="tns:spatialInformationType" maxOccurs="unbounded"/>
>>>              </xs:sequence>
>>>               <xs:element name="nonSpatiallyDefinible"
>>> type="xs:boolean" fixed="true"/>
>>>           </xs:choice>
>>
>> I'm an xml lightweight. In the above, why isn't it just:
>>
>> <xs:choice>
>>   <xs:element name="spatialInformation"
>>               type="tns:spatialInformationType" maxOccurs="unbounded"/>
>>   <xs:element name="nonSpatiallyDefinible"
>>               type="xs:boolean" fixed="true"/>
>> </xs:choice>
>>
>> What do the <sequence>s add?
>>
>>     Thanks,
>>     Paul
>
> Hi Paul,
>
> putting the <spatialInformation> element inside <sequence> with
> maxOccurs="unbounded" means that you can find more than one
> <spatialInformation> describing a capture.

Oh, duh! Sorry. I totally missed the "unbounded". Now I understand the 
difference.

> Using a definition without <sequence>, on the other hand, means that you
> can find only one <spatialInformation> describing a capture. The
> definition would look like the following:
>
> <xs:choice>
>    <xs:element name="spatialInformation"
>                type="tns:spatialInformationType"/>
>    <xs:element name="nonSpatiallyDefinible"
>                type="xs:boolean" fixed="true"/>
> </xs:choice>
>
>
> The current definition (the one with <sequence>) leaves open the
> possibility of specifying more than one <spatialInformation> for a
> capture.  That chance could be exploited in case of composed capture to
> describe spatially each component  by adding  a <spatialInformation>
> element for each of them (I don't know if it could be really useful, I
> have left the definition "as is" to the aim of discussing about it).

Thanks for pointing that out now. That deserves some discussion.

There is a slippery slope here into some major complexity. We started to 
talk about that at the interim. In the case of a switched capture where 
all of the switched sources come from the same scene this could be 
somewhat meaningful, though I wonder if it would be *useful*. In the 
case of a composed capture where all the sources come from the same 
scene I have difficulty understanding how to make any sense of this 
info. And this isn't even capable of representing the case of a switched 
or composed capture where the sources come from *different* scenes.

> Alternatively, we can decide that only one <spatialInformation> can be
> provided for a capture.
> In case of composed capture that are also spatially definible, the
> single <spatialInformation> element would carry the information of the
> maximum captured space.
> In that case, the XML Schema definition would remove the <sequence>
> envelope and the maxOccurs="unbounded" attribute, as reported above.
>
> What is the option that makes more sense to you?

Let's discuss a bit and see what others have to say. For now I think 
that the latter may be the most expedient choice.

	Thanks,
	Paul