[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Well-established uses of processing instructions?

• To: "'Rick Jelliffe'" <ricko@a...>,<xml-dev@l...>
• Subject: RE: Well-established uses of processing instructions?
• From: "Michael Kay" <mike@s...>
• Date: Mon, 9 May 2005 21:39:23 +0100
• In-reply-to: <4280.203.164.53.99.1115664318.squirrel@i...>
• Thread-index: AcVUx3NT8/hUGPIzR6euC4pLwI2J3QAD0DwA

n.
> 
> For cross-platform portability, just use the default entity 
> parser, have a
> little CGI at the URL to provide the date. Or have a cron job 
> generate a
> file with the date every night and reference that.  I don't get why a
> special entity resolver is required?

No, of course an EntityResolver isn't the only way of doing it. As you point
out, there are other ways of solving this problem.

Perhaps I'm unusual, but I find it easier to write

<xsl:template match="processing-instruction('current-dateTime')">
  <xsl:value-of select="current-dateTime()"/>
</xsl:template>

than to set up CGIs and cron jobs.

Michael Kay
http://www.saxonica.com/

• References:
  • RE: Well-established uses of processing instructions?
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: RE: Well-established uses of processing instructions?
• Next by Date: RE: Well-established uses of processing instructions?
• Previous by thread: RE: Well-established uses of processing instructions?
• Next by thread: RE: Well-established uses of processing instructions?
• Index(es):
  • Date
  • Thread