DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: transfering w3.org namespace to my own server

  1. #1
    Nancy Kim Guest

    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
    its availability?



  2. #2
    Bevan Arps Guest

    Re: transfering w3.org namespace to my own server


    "Nancy Kim" <n_kim@audiblemagic.com> 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 namespace.

    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
    I control.

    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,
    Bevan.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center