relative import path in public schema

[LesleyW]

I'm using a public set of schemas for GML, avaiable at www.opengis.net/gml.
They all include or import each other but live in a folder hierarchy, so the
import statement includes schemaLocation="../xlink/xlinks.xsd". I've written
a schema that imports the top level one using
schemaLocation="http://schemas.opengis.net/gml/3.1.0/base/feature.xsd". I've
also tried downloading it and putting it in the schema cache but in both
cases the build fails with 'Cannot resolve the schemaLocation attribute'.

I'm using Visual C# 2005 Express and I'm new to all this, so I'd be very
grateful indeed if anyone knows what I should do to resolve this.

Thanks very much.

Lesley

[Zafar Abbas]

The schemaLocation attribute must specify a targetNamespace and a locaiton
separated by a whitespace. Your example below just has the location.

All the imports are resolved relative to the base path of the parent schema.
If you add your schema to the cache all imports within should be resolvable
relative to its path.

Zafar

"LesleyW" <Le*****@discussions.microsoft.com> wrote in message
news:9A**********************************@microsof t.com...

I'm using a public set of schemas for GML, avaiable at www.opengis.net/gml. They all include or import each other but live in a folder hierarchy, so the import statement includes schemaLocation="../xlink/xlinks.xsd". I've written a schema that imports the top level one using
schemaLocation="http://schemas.opengis.net/gml/3.1.0/base/feature.xsd". I've also tried downloading it and putting it in the schema cache but in both
cases the build fails with 'Cannot resolve the schemaLocation attribute'.

I'm using Visual C# 2005 Express and I'm new to all this, so I'd be very
grateful indeed if anyone knows what I should do to resolve this.

Thanks very much.

Lesley

[LesleyW]

Thanks for your reply. The line does have the target namespace too. I just
didn't show it here. VS adds the schema to its cache (although I have also
tried including it manually) but still fails to resolve this path.

"Zafar Abbas" wrote:

The schemaLocation attribute must specify a targetNamespace and a locaiton
separated by a whitespace. Your example below just has the location.

All the imports are resolved relative to the base path of the parent schema.
If you add your schema to the cache all imports within should be resolvable
relative to its path.

Zafar

"LesleyW" <Le*****@discussions.microsoft.com> wrote in message
news:9A**********************************@microsof t.com...

I'm using a public set of schemas for GML, avaiable at

www.opengis.net/gml.

They all include or import each other but live in a folder hierarchy, so

the

import statement includes schemaLocation="../xlink/xlinks.xsd". I've

written

a schema that imports the top level one using
schemaLocation="http://schemas.opengis.net/gml/3.1.0/base/feature.xsd".

I've

also tried downloading it and putting it in the schema cache but in both
cases the build fails with 'Cannot resolve the schemaLocation attribute'.

I'm using Visual C# 2005 Express and I'm new to all this, so I'd be very
grateful indeed if anyone knows what I should do to resolve this.

Thanks very much.

Lesley