- From: Kal Ahmed <kal@techquila.com>
- Date: Tue, 13 Apr 2004 10:00:37 +0100
- To: "'xmlschema-dev@w3.org'" <xmlschema-dev@w3.org>
If your parser / XML tools support XML catalogs (I believe that Xerces does at least), you could use a catalog to perform the necessary redirection. For a bite-size introduction, see [1]. For the full spec, see [2]. Cheers, Kal [1] http://norman.walsh.name/2003/06/05/xmlcatalogs [2] http://www.oasis-open.org/committees/download.php/2384/cs-entity-xml-catalogs-1.0.html Graeme English wrote: >Hi, > >I need to develop a schema for use at two different sites. The schema would >reside on a different internal web server at each site (the servers can't >see each other) say >http://webserver1/test.xsd and >http://webserver2/test.xsd > >(it can't be on a public server for various reasons, and having it locally >might present maintenance problems) > >There will be several people involved in writing xml documents based on the >test.xsd (which is the same file at both ends). These files will be >trasferred back and forward between sites. > >Is it possible to construct an xml document such that it somehow includes >both possible locations for the test.xsd file? I don't want to have to >modify the xml files each time there are transferred from site to site. > >Thanks for any help > >Graeme > > >******************************************** >Any opinions expressed in this email are those of the individual and not >necessarily the Company. This email and any files transmitted with it, >including replies and forwarded copies (which may contain alterations) >subsequently transmitted from the company, are confidential and solely >for the use of the intended recipient. > >If you are not the intended recipient or the person responsible for >delivering to the intended recipient, be advised that you have received >this email in error and that any use is strictly prohibited. > >If you have received this email in error please notify the IT Dept. via >email to IT.Helpdesk@Teleca.com, including a copy of the message. Please >then delete this email and destroy any copies of it. >********************************************* > > > > >
Received on Tuesday, 13 April 2004 05:01:13 UTC