OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Well-established uses of processing instructions?

[ Lists Home | Date Index | Thread Index ]
  • To: xml-dev@lists.xml.org
  • Subject: RE: [xml-dev] Well-established uses of processing instructions?
  • From: "Rick Jelliffe" <ricko@allette.com.au>
  • Date: Tue, 10 May 2005 04:45:18 +1000 (EST)
  • Importance: Normal
  • In-reply-to: <200505090929.j499T2kL005303@modelo.allette.com.au>
  • References: <427F23ED.7000104@allette.com.au> <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
>> 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?

Rick Jelliffe


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS