OLD XSL

Dear all,
I  have old XSL file with (<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">)
wherever I open the XSL file with xmlspay 2010 I got error
 File test.xsl is not valid.
      'http://www.w3.org/TR/WD-xsl' does not match the fixed default value 'http://www.w3.org/1999/XSL/Transform' for attribute 'xmlns:xsl'.
            Error location: xsl:stylesheet / @xmlns:xsl
            Details
                  VC: Fixed Attribute Default: 'http://www.w3.org/TR/WD-xsl' does not match the fixed default value 'http://www.w3.org/1999/XSL/Transform' for attribute 'xmlns:xsl'.

any idea how to solve this?
ethar1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
Try plugging in your xml to the validator http://validator.w3.org/  You can post a url or snippets of code.   This will help you determine what the issues are.  If you like, you can post the  url or code here as well and we can take a look if you don't understand what the validator spits out.
0
Geert BormansInformation ArchitectCommented:
ignore padas suggestion please, no use sending it to a validator, the error message is explicit enough

Small history lesson (we are taking 1998!)
Microsoft was the first to release an XSLT processor.
But they released the processor against the XSLT Working Draft,
sadly enough the XSLT standard changed a lot after this last Working Draft.
And noone else ever implemented the working draft.
MicroSoft released a compliant XSLT1.0 processor soon after, but a lot of programs (mainly Internet Explorer browser XSLT) were developed and MicroSoft decided to allow MSXML to support both XSLT versions.
MSXSL decides on the type of processor based on the namespace
'http://www.w3.org/TR/WD-xsl' for Working Draft XSLT
'http://www.w3.org/1999/XSL/Transform' for Recommendation 1.0 XSLT
No other processor supports the working draft
so if you take an old microsoft XSLT file, it might be completely wrong
I believe that with the advent of IE9 or IE10 microsoft dropped support for WD-XSLT in the browser

So the issue only starts with this first error message.
You have two options
- make sure the XSLT is processed by an earlier microsoft msxml that still supports the WD
- completely rewrite your XSLT

Given that I am old enough to a. remember this history and b. having done quiet a bit of WD-XSLT in the late nineties, I might be able to assist you in the migration. I would definitely opt for getting rid of the WD-XSLT, because some day soon you will no longer find processors that understand it... and I am pretty sure that you would have a hard time finding developers that understand it

Note that XML-Spy should have a way to tell them not to use the XML-Spy proprietary XSLT processor but an MSXML3 (earliest support for both versions) or MSXML4. www.oxygenxml.com and www.stylusstudio.com do that
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ethar1Author Commented:
any solution?
0
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

Geert BormansInformation ArchitectCommented:
I am not sure you read what I wrote?
There are some options in there for you to choose...
we now need more detail from you
0
ethar1Author Commented:
yes I read it and thank you very much ,,, but unfortunately I don't under stand thing.
what details you need?
I cant rewrite the xsl , its very huge and complicated ( more then 10,000 line of code + JavaScript functions).

I try all the processor on the attached file.
0
Geert BormansInformation ArchitectCommented:
I know it sounds tough but as I wrote you have two options

You have two options
- make sure the XSLT is processed by an earlier microsoft msxml that still supports the WD
- completely rewrite your XSLT

if the XSLT is 10000 lines and includes javascript and rewrite is not an option,
well make sure you process this using an msxml processor, preferably msxml4

So tell me how you want to execute the XSLT, if you can't access the msxml4 from where you execute the code, hire someone in to migrate the 10k xslt

Can you attach the xslt please, so I can have a look?
0
ethar1Author Commented:
cant show any xslt ( confidential ).
0
Geert BormansInformation ArchitectCommented:
well, you need to look at it this way:
you have a program written in an old programming language which never was a standard and only had one compiler. You are bound to either use that one old compiler or rewrite the program.

Did you manage to make it run with msxml4 or msxml3 ?

If the XSLT is confidential, I am always happy to sign an NDA so you can send it to me in private. Maybe I can make an estimate for the time it requires to migrate to real XSLT. If that is not an option either, I hope you can get hold of a working msxml4 for a long time to come.

But that would then conclude this question, no?

Best of luck

Geert
0
ethar1Author Commented:
I can easily render it with msxml3 , but we have a lot of modification on it and I need to use xml-spay to edit it.
anyway , is there is any online application to convert from the old format to the new one?
0
Geert BormansInformation ArchitectCommented:
well, you can edit it using xml spy, but you can't use the debugger... after all, it is not XSLT in the strict sense

microsoft never provided a migration tool. And all the others were never interested, they only started implementing XSLT at the first recomendation. I don't think a migration tool would actually be useful or even possible. The mindset of both versions is very different
0
Geert BormansInformation ArchitectCommented:
offer still stands... if you have a hard time figuring out how to change certain constructs... just mail the lot to me, maybe I can help
0
ethar1Author Commented:
ok, thank you
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
XML

From novice to tech pro — start learning today.