W3C home > Mailing lists > Public > xml-dist-app@w3.org > March 2002

Re: xsi:type for multiref targets.

From: Jacek Kopecky <jacek@systinet.com>
Date: Mon, 4 Mar 2002 14:59:43 +0100 (CET)
To: "'XMLDISTAPP'" <xml-dist-app@w3.org>
Message-ID: <Pine.LNX.4.33.0203041451190.24385-100000@mail.idoox.com>
 My take on the issue:
 At the f2f, Gudge and Noah (I think) proposed that we make the 
type name an optional attribute of a graph node. The actual value 
of the type name would be taken from a) xsi:type attribute, 
failing this b) parent's enc:itemType attribute, or c) from other 
source if available.
 Moreover, if we don't stick strictly to the meaning of xsi:type, 
we're redefining the function of an attribute in somebody else's 
namespace, and this doesn't seem right, even though this 
particular issue doesn't trouble me much.
 In effect, I don't see any problem with just changing the
xsi:type to enc:type, ridding ourselves of all the (wrongly)  
implied XML Schema validation. SOAP Data Model and SOAP Encoding
should depend on just XML Schema part 2 - Datatypes. The
structures part (which, IIRC, defines the xsi:type attribute),
has a different data model and trying to fit one onto another
always results in some degree of clashes.
 It seems to me that XML Schema is overvalued.
 Best regards,

                   Jacek Kopecky

                   Senior Architect, Systinet (formerly Idoox)
Received on Monday, 4 March 2002 08:59:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:11:47 UTC