XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Malaka GSubject: XML-2-XML Mapper, Unqualified Names
Author: Malaka G
Date: 23 Oct 2002 08:00 AM
According to my source schema, elements in the XML must be unqualified because of elementFormDefault="unqualified" is set in the schema.
My source XML file is valid against the XSD.
In my source XML file, only the root element has a qualifier which looks like .
As an example, if I map the name attribute of element to "xmi.id" at the target, the XSLT generated by Stylus Studio for this mapping looks like

1 2
3
4
5 ....>

At the line number 4 of the above code, the XSLT is looking for an element like

..........
....


But in the source XML, there is no "olap" qualifier for element. Then we will not get any matching element for this mapping. I guess this is because of SS is not handling elementFormDefault="unqualified" attribute properly.Do you have any idea to get rid of this...

Postnext
(Deleted User) Subject: XML-2-XML Mapper, Unqualified Names
Author: (Deleted User)
Date: 23 Oct 2002 09:59 AM
This is a multi-part message in MIME format.

------=_NextPart_000_0210_01C27A7D.0BA9C010
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi, Malaka

It seems to me you have a default namespace in your xml file. If this is =true, I don't see why the piece of code generated by mapper has problem. =Actually that is the only way to make xapth works right with default =namespace.

It will help us better understand the problem if you can send us your =xml file and the xsl file.

thanks.

song.

------=_NextPart_000_0210_01C27A7D.0BA9C010
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








Hi, size=3>Malaka

 

It seems to me you have a default =namespace in your
xml file. If this is true, I don't see why the piece of code =generated by
mapper has problem. Actually that is the only way to make xapth works =right with
default namespace.

 

It will help us better understand =the problem
if you can send us your xml file and the xsl file.

 

thanks.

 

song.


------=_NextPart_000_0210_01C27A7D.0BA9C010--

Postnext
Malaka GSubject: Re: XML-2-XML Mapper, Unqualified Names
Author: Malaka G
Date: 24 Oct 2002 08:53 AM
Hi Song,

Fisrt of all thanks for your quick reply...
Acually my XML file doesn't have a default namespace.
If I put mannually a default namespace, it invalidates
the file.Also we don't have a control over to modify
the XML but we can do slight modification to XSD only
for generating XSLT.

The workaround I have now, is to reomove "a:" prefix
mannually in the XSLT produced by SS. But you know
after that I can't use the XSLT with SS.
However I have attached my XSD and XML file as you can
see the actuall issue here.
Thanks a lot
~Malaka



(File attachment removed)

Postnext
(Deleted User) Subject: Re: XML-2-XML Mapper, Unqualified Names
Author: (Deleted User)
Date: 25 Oct 2002 09:14 AM

Hi, Malaka

Thanks to your test case, I see where the problem came from. If you use the
xsd schema file as source, Mapper currently use targetNameSpace as default
namespace and assume you will have a default namespace declaration
(xmlns=...) in your xml instance. This will give problem when
elementFormDefault attribute is 'unqualified'. I'll file a PCR to fix this
problem.

in the meanwhile, the best work around is not to use the xsd file as your
schema souce, instead, you can use the xml instance as the sschema source in
mapper. by doing this, Mapper won't append namespace prefix 'a' in your
xpath.

hope this helps.


song.

Posttop
Minollo I.Subject: Re: XML-2-XML Mapper, Unqualified Names
Author: Minollo I.
Date: 14 Nov 2002 05:41 PM
This issue has been addressed in BL103k, now available for download from:
http://www.stylusstudio.com/update (4.x section)

Please read the description of the fixes/changes in BL103k for further details.

Thanks,
Minollo

 
Topic Page 1 2 3 4 5 6 7 8 9 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.