absolute path vs relative path for substitution group elements

ptn77 · June 15th, 2011, 06:52 PM

Hello All,
I'm running into an issue in my xslt where using the relative path resolves correctly but the absolute path does not.

Code:

The following is the sample xml:

<MittimusDocument>
  <cicjis-mitt-ext:Case>
    <cicjis-mitt-ext:CaseAugmentation>
      <j:CaseDefendantParty>
        <cicjis-mitt-ext:EntityPerson s:id="PER39176212">
          <nc:PersonEyeColorText>Brown</nc:PersonEyeColorText>
        </cicjis-mitt-ext:EntityPerson>
      </j:CaseDefendantParty>
    </cicjis-mitt-ext:CaseAugmentation>
  </cicjis-mitt-ext:Case>
</MittimusDocument>

The following is a snippet of the xslt code to retrieve the PersonEyeColorText using absolute path that doesn't work:

<xsl:template match="cicjis-mitt-ext:Case">
<xsl:value-of select="normalize-space(cicjis-mitt-ext:CaseAugmentation/j:CaseDefendantParty/cicjis-mitt-ext:EntityPerson/nc:PersonEyeColorText)"/>
</xsl:template>

The following is a snippet of the xslt code that uses the relative path expression which does work:

<xsl:template match="cicjis-mitt-ext:Case">

<xsl:value-of select="normalize-space(//cicjis-mitt-ext:EntityPerson/nc:PersonEyeColorText)"/>

</xsl:template>

I am confused as to why the absolute path is not working. Am I missing something? The path looks correct to me. I'm wondering if this has to do with the way the cicjis-mitt-ext:EntityPerson is defined in the schema. In the schema, the j:CaseDefendantParty contains an abstract element called nc:EntityRepresentation and cicjis-mitt-ext:EntityPerson is substituted for this using substitutionGroup.

Any help is appreciated!! Thanks in Advance!

mhkay · June 15th, 2011, 07:15 PM

The only explanation I can think of is that the namespace bindings in the stylesheet don't match those in the source document. You haven't shown either, which could indicate that you haven't realised how important it is to get these right.

ptn77 · June 16th, 2011, 09:58 AM

Sorry forgot to post the namespace bindings. The following is the namespace bindings:

Code:

xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
	xmlns:ccis="http://www.cbi.state.co.us/CCIS"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"
  	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  	xmlns:msxsl="urn:schemas-microsoft-com:xslt" 
  	xmlns:user="urn:schemas-xmlandasp-net:xslt"
  	xmlns:ch="http://localhost/"
	xmlns:j="http://niem.gov/niem/domains/jxdm/4.0"
	xmlns:nc="http://niem.gov/niem/niem-core/2.0"
	xmlns:cicjis-ext="http://www.colorado.gov/cicjis/IEPD/CICJIS/extensions/1.0"
	xmlns:cicjis-mitt="http://www.colorado.gov/cicjis/IEPD/Mittimus/1.0" 
	xmlns:cicjis-mitt-ext="http://www.colorado.gov/cicjis/IEPD/Mittimus/extensions/1.0"
	xmlns:s="http://niem.gov/niem/structures/2.0">

ptn77 · June 16th, 2011, 10:04 AM

After posting the namespace bindings, I went back to the schemas to make sure my namespaces were all correct and found that there was one mistake. The binding for "j" in the schema was version 4.1 instead of 4.0. After fixing this, the absolute path resolved.

xmlns:j="http://niem.gov/niem/domains/jxdm/4.1"

Thank you!!!