W3C home > Mailing lists > Public > xmlschema-dev@w3.org > March 2007

Re: schemaLocation

From: George Cristian Bina <george@oxygenxml.com>
Date: Sun, 18 Mar 2007 09:54:42 +0200
Message-ID: <45FCF042.2030908@oxygenxml.com>
To: Mystra x64 <mystra_x64@fastmail.fm>
CC: xmlschema-dev@w3.org

Hi,

One can think of many ways to do schema association, each have good 
points and bad points.
One bad point with your variant is that you reserve an infinite number 
of attributes, one in each possible namespace.
Anyway - the spec does not force you to use schema instance attributes, 
the application that processes a document is free to take the schema 
from wherever it wants so you can eventually implement your application 
to look for schemaLocation attributes in different namespaces and use 
them to find schemas - note that those schemas need to define also the 
schemaLocation attribute.

Regards,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

Mystra x64 wrote:
> Hi,
>  
> Why is schemaLocation is such a monstrous construct? I mean, let's say I
> have
> xmlns:mycoolns="http://url.com/ns". Then to specify a schema file I need
> to write
> xsi:schemaLocation="http://url.com/ns
> http://someothercoolurl.com/file.xsd" and
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" to boot.
>  
> Why not to use
> mycoolns:schemaLocation="http://someothercoolurl.com/file.xsd" for that?
>  
> i.e. any schema should have schemaLocation attribute in their namespace
> regardless of definition.
> Am I missing something?
Received on Sunday, 18 March 2007 07:48:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:15:41 UTC