Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: DOCTYPE questions and problem(s)

From: Martin <a@-.->
To: NULL
Date: 4/9/2008 9:53:00 AM

Ahh. Ok.

Martin Honnen wrote:
> Martin wrote:
> 
>> Actually I'd come up with another solution using the HOSTS file 
>> instead. My concern is that I'm likely to encounter this or a similar 
>> problem when I start to build schemas for my documents. I'm very 
>> uncertain of my ground here - schemas is next on my todo list - but I 
>> foresee problems with targetNamespace and xmlns:mstns, for example.
> 
> Namespaces are URIs where the URI scheme is used to have globally unique 
> names but where there is not usually a resource at the location. So 
> targetNamespace="http://example.com/ns1" or 
> xmlns:ns1="http://example.com/ns1" is not a problem as XML parsers do 
> not try to dereference those URIs.
> xsi:schemaLocation or xsi:noNamespaceSchemaLocation is where parsers get 
> locations to fetch schemas from. But you can apply the approach with a 
> custom XmlResolver for that as well.
> 
> 


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent