W3C home > Mailing lists > Public > xmlschema-dev@w3.org > April 2002

RE: [xml-dev] which xml schema tools do it right concerning including attributes xml:lang and xml:space

From: Biron,Paul V <Paul.V.Biron@kp.org>
Date: Fri, 19 Apr 2002 14:32:41 -0700
Message-Id: <8904C60CACA7D51191BC00805FEAAF4358EC5E@crdc-exch-7.crdc.kp.org>
To: "'noah_mendelsohn@us.ibm.com'" <noah_mendelsohn@us.ibm.com>, Dare Obasanjo <dareo@microsoft.com>
Cc: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>, Stanley Guan <stanley.guan@oracle.com>, xmlschema-dev@w3.org
> -----Original Message-----
> From:	noah_mendelsohn@us.ibm.com [SMTP:noah_mendelsohn@us.ibm.com]
> Sent:	Friday, April 19, 2002 1:23 PM
> To:	Dare Obasanjo
> Cc:	Henry S. Thompson; Stanley Guan; xmlschema-dev@w3.org
> Subject:	RE: [xml-dev] which xml schema tools do it right concerning
> including  attributes xml:lang and xml:space
> 
> I've only followed some of this thread.  That said:  isn't it reasonable 
> that I might want to define xml:lang, for purposes of my schema, as being 
> an enumeration of say  {en,fr}?   Why prevent that? 
> 
I think that is a perfectly reasonable thing to do...and no, it should not
be forbidden.

> I think it would be a good thing if many parsers took switches to force 
> loading of particular schemas, to force schemaLocation to be honored on 
> import, etc.  Of course, there can be no conflict among (global) 
> definitions of a given element or attribute.
> 
Ditto. The fact that the REC says that schemaLocation is only a hint
shouldn't imply to implementors that they can always ignore it...they should
give uses the option of whether to ignore or honor it.

pvb
Received on Friday, 19 April 2002 17:39:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:30 GMT