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

Re: XHTML 2 Working Group won't be renewed?

  • From: Kurt Cagle <kurt.cagle@gmail.com>
  • To: Michael Kay <mike@saxonica.com>
  • Date: Wed, 8 Jul 2009 14:30:34 -0700

Re:  XHTML 2 Working Group won't be renewed?
Michael,

I'm not disagreeing with your assessment on namespaces, and I'd truly love to see a better solution emerge here for them. Ignoring that some kind of distributed extensibility mechanism is required is not an option, however, and given the steamroller process going on right now on the part of WHATWG, I have to admit to being more than a little concerned how this may turn out.

I keep seeing the idea being pushed of defining some sort of umbrella namespace that can be utilized to "wrap" other namespaces, so that you can essentially work with a default namespace for multiple tags. This way you can deploy namespaces when they are truly necessary while at the same time removing a lot of the redundency inherent in ns prefixes. Perhaps something along the lines of

<html>
   <nsinclude xmlns:my="http://www.myvocabulary.com/xmlns/mynamespace" map="http://www.w3.org/1999/xhtml"/>
   <nsinclude xmlns:foo="http://www.myvocabulary.com/xmlns/foonamespace" map="http://www.w3.org/1999/xhtml"/>
    <head>
    </head>
    <body>
            <cooltag>Ambiguous namespace, resolved by matching.</cooltag>
            <my:cooltag>Unambiguous namespace, resolved inline</my:cooltag>
    </body>
</html>

If <cooltag> is in the my: namepaces but not in the foo: namespace, then the first and second tags have the same rendering. If <cooltag> is in foo, then the foo implementation becomes the default rendering for the first line, unless an optional priority attribute is specified with a higher priority value than the default in a previous nsinclude.

Probably just wishful thinking on my part, however.

Kurt Cagle
Managing Editor
http://xmlToday.org


On Wed, Jul 8, 2009 at 1:54 PM, Michael Kay <mike@saxonica.com> wrote:
 > There's supposed to be an extensibility workshop in September at one of the F2Fs where namespaces in general will be hashed out - I plan to be monitoring that one carefully, as I suspect that there will be a move to "fix" namespaces in a way that will have long term negative repercussions for the XML community. 
 
Let's approach this positively. XML namespaces are a pretty awful piece of design. Perhaps this is an opportunity to revisit the requirement and do something a bit more elegant.
 

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay

 

 
 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


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.