W3C home > Mailing lists > Public > w3c-sgml-wg@w3.org > May 1997

PIFLE (was Re: Are PIs useful?)

From: Rick Jelliffe <ricko@allette.com.au>
Date: Wed, 14 May 1997 16:54:03 +1000
Message-Id: <199705140702.RAA03314@jawa.chilli.net.au>
To: "Alex Milowski" <lex@www.copsol.com>, <w3c-sgml-wg@w3.org>
> From: Alex Milowski <lex@www.copsol.com>

> Because processing instructions are "single use" I consider them to be a
> hack.  I don't find them useful in SGML.  IMHO, the use of processing 
> instructions in XML to convey encodings and other information is rather
> borderline but I understand why they are used for that purpose.

One reason PIs are not as useful as they should be is because they do not
have any standard syntax.  So they languish as second-class SGML markup;
they insert unportable syntaxes inside SGML documents, and vendors and
users have to write proprietary parsing routines.  Which means elements
must be used to do the job of any generic processing instructions.  

We need to treat PIs more as in-band instructions to any part of the
system, rather than just as the foot-in-the-door of the stinky
format-devil. I have 
proposed to ISO WG8 that:

1) all PIs should start with the identifier of their notation (e.g. "XML"),
so that
applications (and parsers--for pragmas--, and storage managers--for
encoding PIs--) 
can at least look at the first name in a PI and know whether the PI is of
interest or not
(rather than the PIs-embedded-in-marked-sections system, which requires a
different grove
for each different application, and so is a little wrong-headed);

and, further, that 

2) all PIs should allow attributes (and have entity dereferencing). So a PI
more like an element start-tag, where the notation name takes the GI's

I would like XML to adopt PIFLE ("Processing Instructions, Formal, Like 
Elements"?) also, at least as far as requiring that the initial name token
in a 
processing instruction is a identifier of the notation for the PI.  I think
the general 
principle (which underlies much of XML, IMHO) that everything should be
requires it. 

Without it, processing instructions are just "single-use", and may not
contribute much
value to XML.

(For any one interested, I am also proposing that marked sections can begin
a notation name, and have attributes. So you could go <p>See character
<![Unicode radix="hex" script="Zh" [ABCD1234ABCD1234ABCD1234ABCD]]>, or
<![TeX [c=a+b]]>.</p>.  So element structure is not polluted by notation or
PI structures, 
if that will serve your system's purpose.  PIs, subdoc and marked sections
are currently 
if not stillborn then certainly failing to thrive in ISO 8879:1986)

Rick Jelliffe
Received on Wednesday, 14 May 1997 03:02:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:25:09 UTC