[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Random Access XML

• From: John Cowan <cowan@mercury.ccil.org>
• To: rjelliffe <rjelliffe@allette.com.au>
• Date: Sat, 19 Feb 2011 15:36:46 -0500

rjelliffe scripsit:

> 1) For a start, we need to be able to know whether "<" "</" and ">" are  
> tag delimiters without knowing context. So we must ban direct use of "<"  
> and ">" in attributes and also get rid of CDATA sections. We should get  
> rid of comments and PIs too, for the same reasons. (Actually, we only  
> need to ban comments and PIs from after the first start tag. For other  
> reasons, we might like to treat the first start-tag and before it  
> specially.)

Of course, random < is already banned everywhere, so if you ban > in
character content as well as attribute values, you get full reversibility:
each of <, </, <?, <!--, >, />, and --> is guaranteed to be the open or
close delimiter of a markup construct.

MicroXML already bans > in character content so that it doesn't have to
special-case ]]>, as required for full XML compatibility.  The only reason
it doesn't ban > in attribute values is that they are required for
compatibility with Canonical XML.

> 3) The generic identifier would have to be more like an XPath.

This could be achieved by convention, using a legal but rarely
employed delimiter like U+00B7 MIDDLE DOT, or any of the vast number of
delimiters allowed by XML 1.0 Fifth Edition.

-- 
At the end of the Metatarsal Age, the dinosaurs     John Cowan
abruptly vanished. The theory that a single         cowan@ccil.org
catastrophic event may have been responsible        http://www.ccil.org/~cowan
has been strengthened by the recent discovery of
a worldwide layer of whipped cream marking the
Creosote-Tutelary boundary.             --Science Made Stupid

• Follow-Ups:
  • Re: Random Access XML
    • From: rjelliffe <rjelliffe@allette.com.au>

• References:
  • Random Access XML
    • From: rjelliffe <rjelliffe@allette.com.au>