Re: RS/RE, again (sorry)

In attempting to draft an argument to Paul Grosso, I've run into a

1) In the absence of a DTD, we must assume mixed content for

2) This could create whitespace nodes in element content.

3) A dichotomy between "DTD-ful" and DTD-less parsing will make any
   sibling-based relationship difficult at best; this will affect some
   TEI or HyQ based hyperlinks, as well as sibling-based stylistic

4) The only way to avoid the dichotomy is to preserve these whitespace
   nodes even when a DTD is present.

5) Since SEPCHAR is thrown away in element content, every element must
   be made mixed content, and any element declaration without #PCDATA
   is illegal.

This is clearly unacceptable.  Once the addressing issues are
considered, I don't think that either RE delenda est or Charles
Goldfarb's shortref hack cuts it - Paul Prescod's suggestions of
explicit mixed content delimiters or elimination of mixed content
whitespace seem to be the only workable suggestions.  They're icky,
but I don't see another way.


[*] There are proposals for heuristics to determine the difference,
    but I can think of a failure condition for any of the ones I've
    seen so far.
<!ENTITY crism PUBLIC "-//EBT//NONSGML Christopher R. Maden//EN" SYSTEM
"<URL>http://www.ebt.com <TEL>+1.401.421.9550 <FAX>+1.401.521.2030
<USMAIL>One Richmond Square, Providence, RI 02906 USA" NDATA SGML.Geek>

Follow-Ups: References: