|
|
 next
|
  Subject: RE: XSD will not load into Mapper
Author: (Deleted User)
Date: 03 Jul 2003 09:22 AM
|
> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
> Sent: Thursday, July 03, 2003 6:33 AM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: RE: XSD will not load into Mapper
>
>
> From: "Chris Lindley"
>
> Hi Song
>
> I've been able to reproduce the error.
>
> Firstly let me explain that the original well formed documnet is
> a respresentation of a csv file. The root is Invoices followed by
> a child element of Invoice which can occur many times. Its
> children; fld01, fld02 etc represent the columns in the origial csv file.
>
> Now, if I load the well formed doc into stylus studio and switch
> to the schema tab I select the Generate XMLSchema radio button
> and type in a file name for the xsd and press enter (it doesn't
> automatically add the .xsd extension by the way!). I can load
> this into the mapper no problem.
> However, I have all my schemas in a particular folder so if I
> repeat the above procedure except this time select a different
> folder to the original well formed doc that I'm creating a schema
> of and then save it this then fails to load in the mapper, as I
> mentioned b4 the drop down menu won't open for me to select the
> root element.
do you mean using the same xml file(InvoiceSample-JP.xml) and create a xsd
schema by switching tab in a diffrent directory, the created xsd schema file
can not be loaded into mapper? it does not happen to me. what does your
generated xsd file looks like.
> I have a large repository of all kinds of different schemas for
> mapping purposes so I don't use namespaces to physical files (or
> virtual for that matter) as the documents coming through my
> system arrive from many different remote systems, some with or
> without namespaces, non-xml formats etc so it's easier to just
> not use them. This also takes me back to my previous post
> (xsi:noNamespaceSchemaLocation issue) which I haven't received a
> response for yet.
the reason we add namespace is when you choose xsd file as source and this
xsd schema requires namespace in the xml instance, if mapper does not
genertate namespace in the xsl file, it will fail when you run the xsl if
the xml instance contains namespace(which means it is compliant with the
schema).
by the way, mapper does not generate namespace in your xslt if your xsd file
does not contains targetNamespace declaration.
we will investigate if we can make the namespace generation optional and let
user to decide if they want namespace or not...
song.
|
 top
|
  Subject: RE: XSD will not load into Mapper
Author: Minollo I.
Date: 03 Jul 2003 09:40 AM
|
>...
>I have a large repository of all kinds of different schemas for mapping
>purposes so I don't use namespaces to physical files (or virtual for that
>matter) as the documents coming through my system arrive from many
>different remote systems, some with or without namespaces, non-xml formats
>etc so it's easier to just not use them. This also takes me back to my
>previous post (xsi:noNamespaceSchemaLocation issue) which I haven't
>received a response for yet.
Chris,
no matter the origin of the XML documents you are using, if you choose
to use an XML Schema file as the source or destination of an XML to XML
mapping, Stylus Studio will assume that the information contained in the
XML Schema file(s) you are using is consistent for all the XML documents to
which you want to apply the transformation. So, if the XML Schema file you
are using contains a namespace declaration, or any other information which
is relevant to how the XML documents you have should be structured, XML to
XML mapper will use that information.
The rationale of adding the xsi:noNamespaceSchemaLocation to the target
document is that if you are targeting a specific schema, we assume you also
want a reference to that schema created in the transformed document. If
your target schema was defined for a specific namespace, then Stylus Studio
would add the proper xsi:schemaLocation entry to the generated document.
Hope this helps,
Minollo
|
|
|
|
COSample-IMS.xml