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

RE: Well-established uses of processing instructions?

• To: xml-dev@l...
• Subject: RE: Well-established uses of processing instructions?
• From: "Rick Jelliffe" <ricko@a...>
• Date: Tue, 10 May 2005 04:45:18 +1000 (EST)
• Importance: Normal
• In-reply-to: <200505090929.j499T2kL005303@m...>
• References: <427F23ED.7000104@a...> <200505090929.j499T2kL005303@m...>
• User-agent: SquirrelMail/1.4.2

>
>>
>> But PIs used to generate text are non-portable, and so
>> appropriate for
>> documents
>> that are being pre-processed. Probably what should be used is
>>  entities:
>>
>> ENTITY current-data SYSTEM
> "http://www.eg.com/dynamic?get-current-date">
>>
>> because the information is data content.
>
> Except that you then have to muck about with low-level coding to write an
> EntityResolver and register it with your XML parser, rather than just
> adding
> a simple template rule to your stylesheet.

Ah, you assume people are using a particular application.

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?

Cheers
Rick Jelliffe

• Follow-Ups:
  • RE: Well-established uses of processing instructions?
    • From: "Michael Kay" <mike@s...>

• 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