ansaurus

Question

remove xmlns attribute from namespace prefix node

Answer 1

+2 A:

Question: How can I remove the xmlns:esi from the HTML output? I tried including it in exclude-results-prefixes, but didn't work.

XSLT with output method xml cannot produce non-well-formed XML.

When the namespace declaration is deleted manually, the "esi:" prefix becomes not bound to any namespace and thie whole document thus becomes non-well-formed.

According to the ESI Spec., the esi namespace must typically be declared in the top element (<html>) of the document.

Try this:

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:esi="http://www.edge-delivery.org/esi/1.0"&gt;
<xsl:output indent="no" omit-xml-declaration="yes"/>

<xsl:template match="/">
   <html xmlns:esi="http://www.edge-delivery.org/esi/1.0"&gt;
    <esi:vars>
        <xsl:text>some text goes here</xsl:text>
    </esi:vars>
    </html>
</xsl:template>

</xsl:stylesheet>

which produces:

<html xmlns:esi="http://www.edge-delivery.org/esi/1.0"&gt;
    <esi:vars>some text goes here</esi:vars>
</html>

Dimitre Novatchev 2010-07-07 12:43:55

Thank you Dimitre, but my output method is html, <xsl:output method="html">. Guess that doesn't work anyway.Problem is, my html code fragment is to be included via esi:include, so i JUST need to produce the fragment without the wrapping <html> tag.

sh0uzama 2010-07-07 12:51:38

@sh0uzama: Then you are out of luck... In case you don't use esi:include this will work. You can try to do the include using XSLT.

Dimitre Novatchev 2010-07-07 13:36:17

@Dimitre: :( bad news then - I'll see if I can find a workaround. Writing it in xsl:text blocks will do the job (as stated below), but doesn't quite suits my needs (readability, mainly). Oh well.

sh0uzama 2010-07-07 14:40:05

@sh0uzama: You can also use DOE (disable-output-escaping="yes"), but this is even uglier and is not supported by all XSLT processors.

Dimitre Novatchev 2010-07-07 16:16:00

this line <xsl:output indent="no" omit-xml-declaration="yes"/> only works for XSL document. When it comes to .net, setting is passed exactly as stated in XSL document, but the XslCompiledTransform doesn't care. It ignores my changes...

Eduardo Xavier 2010-07-14 23:05:43

@Eduardo-Xavier: In .NET you need to take these decisions in the XmlWriter that you pass as argument to the transformation.

Dimitre Novatchev 2010-07-14 23:11:55

@Dimitre Novatchev: .NET classes left me on dire straits. Your wrapper solutions works nice for me. I did remove the wrapper tag using RegEx.

Eduardo Xavier 2010-07-16 01:40:03

@Eduardo-Xavier: Glad it worked well! If you are happy, you could even consider accepting my answer :)

Dimitre Novatchev 2010-07-16 02:41:42

Admitting a post-processing, yes, this is the best solution. It allows you to write esi code directly without DOE.

sh0uzama 2010-07-20 09:30:15

Answer 2

+2 A:

With any input, this stylesheet:

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"&gt;
<xsl:output method="text"/>

<xsl:template match="/">
    <xsl:text>&lt;esi:vars></xsl:text>
        <xsl:text>some text goes here</xsl:text>
    <xsl:text>&lt;/esi:vars></xsl:text>
</xsl:template>

</xsl:stylesheet>

Result:

<esi:vars>some text goes here</esi:vars>

Note: For no-well-formed output you can use DOE or TEXT serialization only.

Alejandro 2010-07-07 13:55:29

Thank you Alejandro. That was basically what I did before. It works without hassles, it's just very ugly to read.I was trying to find out a way to write down ESI code keeping readability.

sh0uzama 2010-07-07 14:37:33

@sh0uzama: You are wellcome! The problem here isn't to write down ESI code. The problem is that your output is a fragment (not the complete document) and this fragment without namespace declaration is not wellformed.

Alejandro 2010-07-07 14:56:54

I've spent the whole day trying figure out this shit. Apart from many oak samples in the internet, that shit doesn't work at all. We need somehow put < at HTML tags so that it can works.I'm sorry too... terrible I mean!

Eduardo Xavier 2010-07-14 23:03:37

@Eduardo Xavier: Yes, this is problematic. But all the blame lies with ESI because it request a prefix but does not handles namespaces well. All ESI's user should sumit a fix request.

Alejandro 2010-07-14 23:23:07

@Alejandro: Dimitre Novatcheve's solution is the best one. It worked for me. I manually removed the wrapper tag using C# and regex.

Eduardo Xavier 2010-07-16 01:35:59

@Eduardo Xavier: Yes, I also think that wrapping ESI elements with other (any) element that declare the namespace is better. But that does not cover every scenario. So, you endded up with two codes in two language for the same task. I think that the very best solution is doing the include directly with XSLT (this add the parser time in XLST 1.0 but don't in XSLT 2.0)

Alejandro 2010-07-16 12:31:27

@Alejandro: you are right. Best thing is, I think Dimitre's solution can fit to most scenarios (so I guess I had to give him the "Answer"), but for my specific case... I used your solution (well, actually we already used <![CDATA[]]> blocks to write ESI)

sh0uzama 2010-07-20 09:31:44

@sh0uzama: You can choose the answer that you want. I don't dispute that right. But, I think your questions is about output malformed XML, and this can be done only with DOE or text serialization.

Alejandro 2010-07-20 13:03:30

Yes, you are completely right... I can't give "Accepted Answer" to you both, but I wish I could... :(

sh0uzama 2010-07-22 16:24:24

@Alejandro @sh0uzama I've found a better way to do it. It worked for me.

Eduardo Xavier 2010-08-11 05:07:50

Answer 3

+1 A:

I've found the professional way to do it. The right answer depends on the following:

<xsl:stylesheet
  version="1.0" xmlns:asp="remove"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:app="http://myNamespace.com/app" 
  exclude-result-prefixes="app">

use this function here exclude prefixes

exclude-result-prefixes

For more information: http://msdn.microsoft.com/en-us/library/ms256204.aspx

Eduardo Xavier 2010-08-11 05:06:30

@Eduardo Xavier: First, your professional solution don't answer the question **How can I remove the xmlns:esi from the HTML output?** . This means: how can I have a namespace prefix without a namespace declaration. The answer, the only answer, is that if want a non well-formed tree you need DOE or text serialization. Second, `xsl:stylesheet/@exclude-result-prefixes` is a standar XSL attribute, so you should quot the specs (no MS documentation): http://www.w3.org/TR/xslt#literal-result-element . And last, with your answer, another process is needed: removing the namespace declaration...

Alejandro 2010-08-11 13:42:43

@Alejandro I used MS doc 'cause is what I use to perform transformation. Anyway.. it worked for me. I'll do more experiments and see...

Eduardo Xavier 2010-08-12 02:27:48

ansaurus

tags:

views:

answers:

remove xmlns attribute from namespace prefix node

related questions