OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] URL versus relative path schemaLocation imports

> We have a large number of XML schemas and have separated some 
> of these into common schemas that we reuse using the xsd 
> import element.
> e.g. 
> <xsd:import namespace="http://...."; schemaLocation="...."/>
> I was wondering if there are any best practices for choosing URL
> (http://....) over a relative path (../../schema.xsd). Any 
> references to documentation or discussions would be great.

It's exactly the same issue as relative vs absolute URLs in HTML web pages,
isn't it?

Use relative URIs for links within a package of related documents that will
be moved around together as a unit. Use absolute URIs when referring to
something that is developed separately.
> Using a HTTP URL requires that we host these schemas on a web 
> server 

No necessarily. There are many technologies that allow you to intercept the
attempt to dereference the http: URI and substitute a resource at a
different location: for example the URIResolver if you are in the Java


Michael Kay

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS