Re: [xml-dev] A design question for you please

First of all, your diagram has labels using "include" but your words say 
"import".  Those are not the same things in XML Schema, so you had 
better clarify what you are thinking about.

Second, what are you really trying to accomplish here?  You say you want 
to see a listing of schema file names and the associated schema 
contents, but why?  A listing like that is likely to be very long and 
dense;  how will that be useful?  Maybe there's another way.

Third, should the output be in XML?  Because if it is, you won't be able 
to simply copy in the various schemas as is.  If not, what format should 
the results be in, and why?

Fourth, if several of the included schemas themselves include the same 
subsidiary schema, should that subsidiary one be listed in full against 
all of the calling schemas?  That would be a lot of duplication.  If 
not, where should it be listed?

TomP

On 6/26/2015 10:37 AM, Costello, Roger L. wrote:
> Hi Folks,
>
> I’d like for you to put on your designer hat please.
>
> Suppose I have an XML schema document A that imports B and C. Both B and
> C import D. And D imports A.
>
> I want to create a tool. I feed into the tool the main schema document
> (e.g., schema document A) and it outputs a sequence of schema documents:
>
> <xs:schema>... A ... </xs:schema>
> <xs:schema>... B ... </xs:schema>
> <xs:schema>... C ... </xs:schema>
> <xs:schema>... D ... </xs:schema>
>
> However, I want the tool to also output the filename of each schema
> document. So, should the tool output a sequence of (filename, schema
> document) pairs?
>
> A.xsd
>
> <xs:schema>... A ... </xs:schema>
>
> B.xsd
> <xs:schema>... B ... </xs:schema>
>
> C.xsd
> <xs:schema>... C ... </xs:schema>
>
> D.xsd
> <xs:schema>... D ... </xs:schema>
>
> Is that how you would do it?
>
> /Roger
>