Re: Element Structure for XML (Clause 7)

At 05:05 PM 9/12/96 -0400, Steven J. DeRose wrote:
I've been fortunate enough never to encounter a conflict in those
>self-assigned PI keywords -- anybody else actually hit one yet? (I'm not
>saying that would prove reliability, just good fortune or remarkable
>implementor restraint...)

The processing instructions used by Panorama to include style sheets and
navigators are generic enough that they could easily conflict: STYLESPEC,

I agree with Steve and Charles that the initial "PI keyword" is,
semantically, a notation name.  We could even propose a new public text
keyword for use in notation declarations: PROCINST, e.g.:

<!NOTATION Panorama PUBLIC "-//Synex AB//PROCINST Panorama control
instructions//NE" >

While I think PIs are a poor (if easy) way to do what Arbortext does, I
think Paul's argument that PIs exist and thus excluding them would cause a
lot of pain is a good one.  In the abstract, I agree with Martin that PIs
should be restricted to the prolog.


W. Eliot Kimber (kimber@passage.com) 
Senior SGML Consultant and HyTime Specialist
Passage Systems, Inc., (512)339-1400
10596 N. Tantau Ave., Cupertino, CA 95014-3535 (408) 366-0300, (408)
366-0320 (fax)
2608 Pinewood Terrace, Austin, TX 78757 (512) 339-1400 (fone/fax)
http://www.passage.com (work) http://www.squirrel.com/squirrel/drmacro (home)
"If I never had existed, would you still remember me?..."
                                   --Austin Lounge Lizards, "1984 Blues"