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 (was Re:[xml-de

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

Let's see if I understand this...
1.) The colonified names way 
<html xmlns="http://www.w3.org/1999/xhtml"; xmlns:x="http://www.w3.org/1999/xlink/ <http://www.w3.org/1999/xlink/> "...
Disadvantages: Verbose. 
Advantages:    All information necessary to process links is self contained in document. 
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. 

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

	On Fri, 2002-09-27 at 15:23, Mike Champion wrote:
	> So, HLink shows us a sketch of what an XLink without colonified namespaces might
	> look like. 
	That's not a bad analysis and what I find ironical is that is a sense
	one of the first applications to have shown the way is a highly
	colonified one: W3C XML Schema!
	The idea behind the PSVI is more or less to say that names (local or
	not) do not care if you know the type and that you might use namespaces
	or not if you like, it doesn't matter as long as you know the types.
	HLink can be seen as a lightweight mechanism to do a similar mapping,
	but it's kind of following the same path.
	Do you think colons might auto-anihilate themselves at the end of the
	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
	The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
	initiative of OASIS <http://www.oasis-open.org>
	The list archives are at http://lists.xml.org/archives/xml-dev/
	To subscribe or unsubscribe from this list use the subscription
	manager: <http://lists.xml.org/ob/adm.pl>


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

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