transfering w3.org namespace to my own server
In my xsl, I'm relying on http://www.w3.org/1999/XSL/Transform for the namespace.
I'm concerned about relying on this server for production. Would there be
a way to transfer that to my own server so I can control
Re: transfering w3.org namespace to my own server
"Nancy Kim" <firstname.lastname@example.org> wrote:
> In my xsl, I'm relying on http://www.w3.org/1999/XSL/Transform
> for the namespace.
>I'm concerned about relying on this server for production.
Don't be - the URI for the namespace is used ONLY as a name to uniquely identify
The idea is that using URI's for the canonical name of the namespace makes
it easy to avoid conflicts between schema. I can't (well, shouldn't) publish
a schema with a namespace URI beginning "http://www.w3.org" because I don't
have control of the www.w3.org domain. I *can* publish a schema with a namespace
beginning "http://home.clear.net.nz/pages/niche" because that *IS* something
In a lot of ways it is similiar to packages in Java - Sun publish packages
com.sun.* and at work we write packages com.actfs.* Even if we duplicate
a class name already written by Sun, there is no conflict because the package
names are based on domain ownership.
Hope this helps,
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL