• From: Pete Cordell <pete++xmldev@c...>
• To: Amelia A Lewis <amyzing@t...>, xml-dev <xml-dev@l...>
• Date: Fri, 23 Jul 2021 10:13:15 +0100

On 23/07/2021 04:07, Amelia A Lewis wrote:

On Thu, 22 Jul 2021 23:20:37 +0100, Pete Cordell wrote:

If you're not interested in the new syntax being a subset of XML and
you still want namespaces, you'll want to consider an alternative way
of mapping namespace prefixes to namespaces so that the mapping is
available BEFORE it is required.  Currently the mapping mechanism
requires a fair bit of pre-fetching and caching which is sub-optimal.

Something like the following might work:

<:and http://www.whatever.com/:>
<and:harry />

Why? That still separates :and from and:, so if you start parsing on
the <and:harry /> line, you're busted. And why use a non-default prefix
for an element?

<harry xmlns="http://www.whatever.com">

It is almost never *necessary* to bind a namespace to a prefix for use
with elements. It can be verbose to repeatedly re-declare with a bad
schema design like this:

<root>
   <othernschild xmlns="http://other.ns.example.com" />
   <othernschild xmlns="http://other.ns.example.com" />
   <othernschild xmlns="http://other.ns.example.com" />
   <othernschild xmlns="http://other.ns.example.com" />
   <!-- ... -->
</root>

• References:
  • Napkin grammar
    • From: Rick Jelliffe <rjelliffe@a...>
  • Re: Napkin grammar
    • From: Tim Bray <tbray@t...>
  • Re: Napkin grammar
    • From: Rick Jelliffe <rjelliffe@a...>
  • Re: Napkin grammar
    • From: Pete Cordell <pete++xmldev@c...>
  • Re: Napkin grammar
    • From: Amelia A Lewis <amyzing@t...>