OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Rethinking namespaces, attribute remapping (wasRe:[xml-dev

[ Lists Home | Date Index | Thread Index ]
  • To: "Eric van der Vlist" <vdv@dyomedea.com>
  • Subject: RE: [xml-dev] Rethinking namespaces, attribute remapping (wasRe:[xml-dev] TAG on HLink)
  • From: "Dare Obasanjo" <dareo@microsoft.com>
  • Date: Fri, 27 Sep 2002 07:57:32 -0700
  • Cc: "Mike Champion" <mc@xegesis.org>,<xml-dev@lists.xml.org>
  • Thread-index: AcJmMg0erQTaGbjySq6GXYsHlkRp2gAAnjZB
  • Thread-topic: [xml-dev] Rethinking namespaces, attribute remapping (wasRe:[xml-dev] TAG on HLink)

In the case of schema it really depends on what kind of processing is being done. In general, most people I know feel that xsi:schemaLocation is a bad idea and are quite glad that it is merely a hint in the W3C XML Schema REC and not something required to be processed. 
Of course, currently there aren't applications that consume the PSVI so it isn't much of a problem seperating schema and XML instance although once they arise I may reconsider my position. For XQuery/XSLT 2.0/XPath 2.0, I would still say nay to xsi:schemaLocation 

	-----Original Message----- 
	From: Eric van der Vlist [mailto:vdv@dyomedea.com] 
	Sent: Fri 9/27/2002 7:27 AM 
	To: Dare Obasanjo 
	Cc: Mike Champion; xml-dev@lists.xml.org 
	Subject: RE: [xml-dev] Rethinking namespaces, attribute remapping (wasRe:[xml-dev] TAG on HLink)

	That's interesting...
	On Fri, 2002-09-27 at 16:10, Dare Obasanjo wrote:
	> 2.) The HLink way
	> <html xmlns="http://www.w3.org/1999/xhtml"; hlink:definition=http://www.example.org/whatever...
	> Advantages: Modular, easy for Joe Blow to use without understanding how it works
	> Disadvantages: Security issues, information necessary to process document no longer self contained
	> In my personal opinion, HLink is a step backwards for general XML processing. However given the unique constraints of the XHTML working group I can see why they chose HLink as a solution and agree that something like it is needed for XHTML which is intended for use by non-technical people in a simple and straightforward manner without placing undue cognitive load.
	Let's add
	3.) The W3C XML Schema way
	 <html xmlns="http://www.w3.org/1999/xhtml";
	Would you say it's a step backwards (or maybe two) if it leads to using
	a single namespace in the instance document and rely on datatypes
	compared to using a "namespace soup" and rely on element names ?
	Rendez-vous à Paris.
	Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
	(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS