Re: Why xsi:type works only inwards, not outwards?

Kevin Braun wrote:
> 
> Hi,
> 
> One brief comment embedded below.
> 
> Kevin
> 
> On 12/3/2009 11:13 AM, Krzysztof FF wrote:
>> Hi all,
>>
> [...]
>>
>> BUT USING xsi:type on both levels is illegal:
>>
>> <sys:Entity xsi:type="RoomType">
>> <!-- namespaces omitted for brevity -->
>>     <sys:category xsi:type="RoomCategoryType">living</sys:category>
>> </sys:Entity1>
>>
>>   
> I believe this would be invalid because you have indicated that 
> sys:Entity is actually a "RoomType", but then you give a sys:category 
> for the child, which is not legal according to "RoomType" - you need an 
> "app:roomCategory" element.  Once you tell it the type the element 
> should be validated against, you have to follow the model for that type.
> 

But I told that sys:category is actually RoomCategoryType using xsi:type, so
why id doesn't works? Why actual type is not exposed, only plain one?

It seems I have to live with that, but it doesn't suits me.

Thank you anyway.
-- 
View this message in context: http://old.nabble.com/Why-xsi%3Atype-works-only-inwards%2C-not-outwards--tp26628621p26632358.html
Sent from the w3.org - xmlschema-dev mailing list archive at Nabble.com.