BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20080317T230000Z DTEND:20080318T000000Z DTSTAMP:20080317T230657Z ORGANIZER;CN=Andy Chambers:MAILTO:[EMAIL PROTECTED] UID:[EMAIL PROTECTED] ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;X-NUM-GUESTS=0:MAILTO:xalan-j-users@xml.apache.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=Andy Chambers;X-NUM-GUESTS=0:MAILTO:[EMAIL PROTECTED] CLASS:PRIVATE CREATED:20080317T230656Z DESCRIPTION:On Mon\, Mar 17\, 2008 at 10:14 PM\, Adam Jenkins <adamjenkins@ nti.com.au> wrote:\n> hmmmm\, I like your second idea (too many parameters to make it a function -- would get messy)...so you're saying something like the following should work?\n> \n> <xsl:variable name="myvar">\n> <htt p:queryString>\n> <param name="1" value="1"/>\n> <param name="2 " value="2"/>\n> </http:queryString>\n> </xsl:variable>\n> \n> I wasn 't aware you could put body text in xsl:variable\, but if that works that's a great solution.\n\nYou can but when you do\, the variable is a result tr ee fragment rather than a nodelist. If you want to treat the result as a n odelist (e.g. <xsl:for-each select="$myvar//a">...</xsl:for-each> to proces s all anchors in your page)\, you'll need to use an extension function to c onvert the result\ninto a node-list.\n\nSorry if this is obvious. It had m e stumped for a while the first time I came across it.\n \n--\nAndy\nView y our event at http://www.google.com/calendar/event?action=VIEW&ueid=81griabj 1dqet0i7m3vlcj0ehs. LAST-MODIFIED:20080317T230656Z SEQUENCE:0 STATUS:CONFIRMED SUMMARY: TRANSP:OPAQUE END:VEVENT END:VCALENDAR
invite20080317T230000.ics
Description: application/ics
