[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

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

  • To: "Eric van der Vlist" <vdv@d...>
  • Subject: RE: Rethinking namespaces, attribute remapping (wasRe: TAG on HLink)
  • From: "Dare Obasanjo" <dareo@m...>
  • Date: Fri, 27 Sep 2002 07:57:32 -0700
  • Cc: "Mike Champion" <mc@x...>,<xml-dev@l...>
  • Thread-index: AcJmMg0erQTaGbjySq6GXYsHlkRp2gAAnjZB
  • Thread-topic: Rethinking namespaces, attribute remapping (wasRe: TAG on HLink)

hlink example
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@d...] 
	Sent: Fri 9/27/2002 7:27 AM 
	To: Dare Obasanjo 
	Cc: Mike Champion; xml-dev@l... 
	Subject: RE:  Rethinking namespaces, attribute remapping (wasRe: 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"
	xsi:schemaLocation="http://www.example.org/whatever...
	
	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 ?
	
	Eric
	--
	Rendez-vous à Paris.
	                          http://www.technoforum.fr/integ2002/index.html
	------------------------------------------------------------------------
	Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
	(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
	------------------------------------------------------------------------
	
	


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.