Lists Home |
Date Index |
- To: firstname.lastname@example.org
- Subject: RE: [xml-dev] Well-established uses of processing instructions?
- From: "Rick Jelliffe" <email@example.com>
- Date: Tue, 10 May 2005 04:45:18 +1000 (EST)
- Importance: Normal
- In-reply-to: <200505090929.j499T2kL005303@modelo.allette.com.au>
- References: <427F23ED.firstname.lastname@example.org> <200505090929.j499T2kL005303@modelo.allette.com.au>
- User-agent: SquirrelMail/1.4.2
>> But PIs used to generate text are non-portable, and so
>> appropriate for
>> that are being pre-processed. Probably what should be used is
>> ENTITY current-data SYSTEM
>> 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
> 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?