Clever idea for func:script (was xmlns:exslt)

Uche Ogbuji <[email protected]>
Newsgroups gmane.text.xml.xslt.extensions
Organization Fourthought, Inc.
Message-ID <1088530988.6047.18767.camel@borgia>
On Tue, 2004-06-29 at 09:42, Daniel Stodden wrote:

> 3.
> 
> there is a totally different approach which does not require namespaces,
> but is build upon open standards and already has assignments for many
> languages: use MIME types. that's how HTML4 does it. if this works for
> HTML4, why should XSLT require a different approach?
> 
> mime types by themselves do not solve the versioning problem pointed out
> above, but then again: if there is such a problem and it never gets
> solved for MIME, would namespaces manage to solve it? probably not,
> because it is a coordination issue and not a technical one.

This is very clever thinking.  My only problem with this idea is that I
didn't come up with it myself.  :-)

I personally would be all for replacing the specification for
func:script/@language to be an Internet media type, although I wonder
whether it should then be renamed func:script/@type, with @language
immediately deprecated.

I also wonder how problematic this would be on deployed legacy.

Thoughts, anyone?


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
A survey of XML standards - http://www-106.ibm.com/developerworks/xml/library/x-stand4/
When to use elements versus attributes - http://www-106.ibm.com/developerworks/xml/library/x-eleatt.html
Introducing PyRXP - http://www.xml.com/pub/a/2004/02/11/py-xml.html
XML in the financial services industry - http://www-106.ibm.com/developerworks/xml/library/x-think22.html
Python Web services developer: The real world, Part 2 - http://www-106.ibm.com/developerworks/webservices/library/ws-pyth16/
Keep your XML clean - http://www.adtmag.com/article.asp?id=9012
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.