RE: Having trouble validating an existing XSD schema.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Allan F Cuthbertson (anonymous_at_discussions.microsoft.com)
Date: 12/20/04 

Date: Mon, 20 Dec 2004 11:34:27 -0800

Thank you for your list of suggestions below.
I hope you & your family have a nice holiday season.

I've started individually including some of the smaller
dependency files into a project first as you suggested
below. I'm struggling, but I have managed to get a few
of the external XSD file links included in my project and
validated.

I have a funny feeling I'm not going to be able to pull
this off with my current knowledge of the schema
structures. I'll give it some more time though.

Thanks again for you advice

Allan.

>-----Original Message-----
>Allan,
>
>I had some issues also when I tried to import an
existing schema. I finally
>got it to validate, but it wasn't easy. Here are some
tips that might help:
>
>1. Identify all schema dependencies, because you will
need to add every
>schema that is is referenced by another schema to your
project.
>
>2. Biztalk copies the added schema into the current
project folder, so you
>will lose any relative addressing. Example: When you
add 'common-types.xsd'
>to the project, it will be in the same folder
as 'archivearticle.xsd', so you
>need to 'flatten' out the schemaLocation attribute. So,
>schemaLocation="presentation/common-types.xsd" becomes
simply
>schemaLocation="common-types.xsd". You will need to do
this for every include
>in every schema, since all schemas will now be in the
same folder. This
>editing must be done outside of Biztalk.
>
>3. I found that the best way to proceed was to import
one schema at a time
>and validate it, then import the next schema, etc. I
found it helpful to
>identify all of the dependencies before hand, and start
by importing schemas
>with the least dependencies.
>
>4. Once you have imported a schema into BizTalk, pay
attention to the 'Root
>Reference' property. You may need to set this (it is a
drop down box)
>
>Good Luck.
>
>Bob Corcoran
>
>"Allan F Cuthbertson" wrote:
>
>>
>> I am currently trying to use Biztalk 2004 to transfer
magazine article
>> content to a group at the following website:
http://dtd.nlm.nih.gov/
>>
>> Here are the XSD schema source documents below.
>> ftp://ftp.ncbi.nih.gov/pub/archive_dtd/archive-
interchange-xsd-1.1.zip
>>
>> The primary XSD document which I need to use in the
above download is called:
>> ArticleArchive.xsd document.
>>
>> Unfortunately, I am unable to include the
ArticleArchive.xsd document in a
>> new BizTalk project in Visual Studio.Net. I get a
bunch of error messages,
>> which I believe are related to the import of various
namespace(s) & attribute
>> name collisions. Iā?Tm confident that the source XSD
documents are valid from
>> the source provider, i.e. (The National Library of
Medicine).
>>
>> I was wondering if someone could download the
following material from the
>> site above, and tell what I need to do to make the XSD
document usable in my
>> project.
>>
>> Allan Cuthbertson.
>>
>.
>

Relevant Pages

  • Re: Sixth normal form
    ... if two projections are independent, as is the case when moving from ... cyclic pair of nclusion dependencies if you want the new schema to be ... And if you only want the new schema to ... {Whse, Item, TranId, RcvdDate, QtyRcvd, QtySold, Cost} ...
    (comp.databases.theory)
  • Map failure with Biztalk 2004 to Biztalk 2006 R2 Upgrade
    ... We have a map that has failed to compile when upgrade from Biztalk 2004 to ... xsd:include elements, ... in Biztalk 2004 the map that uses a Client schema has 3 elements ... This Record to Element ONLY occurs in a MAP representation of a schema. ...
    (microsoft.public.biztalk.general)
  • GAC dependencies ...
    ... dependencies in a huge BizTalk projects. ... orchestrations and other assets that are spread over several BizTalk ... We give this schema name to the application and get a full ...
    (microsoft.public.biztalk.general)
  • RE: Having trouble validating an existing XSD schema.
    ... called "XMLSpy" and I'm making some progress there. ... I would have liked to have given Biztalk more time to ... albeit, in my case a fairly complex schema, before being ... Identify all schema dependencies, because you will ...
    (microsoft.public.biztalk.general)
  • Re: Principle of Orthogonal Design
    ...     KEY ... but you seem to do it here at schema level. ... few extra dependencies you haven't told us about? ... the database is inconsistent due in my opinion to a POOD violation. ...
    (comp.databases.theory)