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

Re: XML Blueberry (non-ASCII name characters in Japan)

• From: David Brownell <david-b@p...>
• To: xml-dev@l...
• Date: Mon, 09 Jul 2001 10:05:56 -0700

A few years back, I noticed that most XML parsers had logic
that went pretty much like:

    if (!"1.0".equals (version))
        panic ()

It might be an appropriate time for folk to start planning how
that logic will need to change.  Perhaps

    if (!("1.0".equals (version) || "blueberry".equals (version) ))
        panic ();

will be the way to go?  I don't really like the idea of accepting
just any version string there, because of a suspicion (grounded
in history) that all kinds of XML "versions" will start to show
up, perhaps starting with "VendorM" (or "VendorI", etc) with
all sorts of exotic rules about what each variant means (this
one just deletes DTDs, that one embeds W3C's schemas,
this other extended the standard with proprietary syntax).

Note that the issue isn't "what should the string be"; it's "how
should such a transition be handled", along with "what should
the interoperability consequences be".

- Dave

• References:
  • Re: XML Blueberry (non-ASCII name characters in Japan)
    • From: Murata Makoto <mura034@a...>
  • Re: XML Blueberry (non-ASCII name characters in Japan)
    • From: Joel Rees <rees@s...>
  • Re: XML Blueberry (non-ASCII name characters in Japan)
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: RE: OS other than Win
• Next by Date: Re: Presumption of XML's Stability (was RE: XML Blueberry (non-ASCIInamecharacters in Japan))
• Previous by thread: Re: XML Blueberry (non-ASCII name characters in Japan)
• Next by thread: Re: XML Blueberry (non-ASCII name characters in Japan)
• Index(es):
  • Date
  • Thread