Re: Shortrefs fatally flawed

At 11:09 AM 10/2/96 -0400, David G. Durand"  (David G. Durand wrote:
>   I just realized that we are seriously hosed if we endorse the use of
>shortrefs and some pseudo-element to implement an SGML-compatible a quoting
>syntax for XML. Say, we define a pseudo element <pe>, for the sake of
>argument. Now we need to document a restriction that no element may be
>called <pe>, or else we will generate a terribly wrong ESIS. We are also
>likely to make the process of creating content models extremely difficult,
>due to the name conflict, and content model cooking required in the
>conversion to an SGML DTD.

I think we can pick a name that is highly likely not to be used.  We could
also use some sort of psuedo SGML declaration to rename both the
psuedo-element element type and the delimiter pair used to quote data, e.g.:

 <foo>[This is quoted data]</foo>

Note also that "\" *can* be used with the RCS as a shortref delimiter, you
just have to use a numeric character reference in the SGML Declaration, e.g.:

                  SHORTREF SGMLREF  "&#092;<" 

These shortrefs provide "escapes" for the common delimters, e.g. \<, \&,
\[, \], \\, etc.


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.drmacro.com (home)
"If I never had existed, would you still remember me?..."
                                   --Austin Lounge Lizards, "1984 Blues"