XML / XSL

<?xml version="1.0" encoding="utf-8"?>
<contents>
  <content name="title">
    <span class="b1">Heart Attack</span> - Contact us
  </content>
</contents>

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:msxsl="urn:schemas-microsoft-com:xslt" exclude-result-prefixes="msxsl"
>
  <xsl:output method="xml" indent="yes"/>

  <xsl:template match="/contents">
    <results>
      <xsl:apply-templates select="content[@name='title']"/>
    </results>
  </xsl:template>

  <xsl:template match="content">
    <result>
      <xsl:value-of select="."/>
    </result>
  </xsl:template>
</xsl:stylesheet>

<?xml version="1.0" encoding="utf-8"?>
<results>
  <result>
    Heart Attack - Contact us
  </result>
</results>

<xsl:template match="/">
<scope>
<xsl:copy-of select="/scope/attribute" />
<boost name="df" />
<xsl:apply-templates />
</scope>
</xsl:template>
<xsl:template match="document">
<document url="{@url}">
<xsl:if test="viv:test(content[@name='snippet'], 'heart', 'case-insensitive-regex')">
<xsl:attribute name="boost-name">df</xsl:attribute>
<xsl:attribute name="boost-display">boost-and-list</xsl:attribute>
</xsl:if>
<xsl:copy-of select="@*" />
<xsl:copy-of select="* | text() | comment()" />
</document>
</xsl:template>

<xsl:output omit-xml-declaration="yes" />
<xsl:template match="boost" mode="list-boost-custom">
<fieldset style="border: 2px solid orange">
<legend style="font-size: 120%; color: #555">Good Choices:</legend>
<ul style="list-style-type:none; padding: 0 0.5em">
<xsl:for-each select="document">
<li style="margin: 0.5em 0;">
<span>
<a href="{@url}">
<xsl:value-of select="content[@name='title']" />
</a>
</span>
</li>
</xsl:for-each>
</ul>
</fieldset>
</xsl:template>

<xsl:copy-of select="@*" /><xsl:copy-of select="* | text() | comment()" />

<li style="margin: 0.5em 0;"><span><a href="{@url}"><xsl:value-of select="content[@name='title']" /></a></span></li>

mike123543 wrote:

The example I've seen in the book for MCTS exam 70-536 shows that you take your employee class and add the serializable attribute to it and implement IDeserializationCallback. You then use the attribute NonSerialized to mark a type that is not to be serialized

mike123543 wrote:

This issue would only arise if I needed to customise the xml serialization

Honeyboy_20 wrote:

i test it in this site http://www.validome.org/grammar/ but give me error