This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: designing a xsl:uniq function



  Perhaps a new command for XSLT 2.0 ? It would look like :
 
  <xsl:for-each select="//indexentry[@level1=$my_first_level and @level2]">
           <xsl:sort select="@level2"/>
           <xsl:uniq select="@level2"/>
  [...]
  </xsl:for-each>

  What do you think of it ?


this is really just the "grouping" problem (the simple case where you
only process the group as a whole and not the individual elements)
see the XSLT2 requirements document (http://www.w3.org/TR/xslt20req)
for some thoughts on grouping.

xsl:uniq is slightly problematic as you have to decide which of the
elements you keep. They may all have th esame sort key but they are
different nodes so "." generate-id(.) etc would have different values
depending on which node was chosen. for this reason it's probably better
to have a grouping construct that lets you access each group of nodes
with the same sort key, and lets you chose in the stylesheet which if
any node out of each group that you process.


David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]