W3C home > Mailing lists > Public > public-iri@w3.org > July 2011

Re: I-D Action: draft-reschke-ref-parsing-00.txt

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Sun, 03 Jul 2011 18:44:49 +0200
To: Julian Reschke <julian.reschke@gmx.de>
Cc: public-iri@w3.org
Message-ID: <186117tb877n0b609o6jttdb4ufld1su0p@hive.bjoern.hoehrmann.de>
* Julian Reschke wrote:
>On 2011-07-03 12:30, Bjoern Hoehrmann wrote:
>> As for B.3., I would think the only people who might find that a vaguely
>> good idea are people who have trouble applying regular expressions, and
>> I see no reason to accomodate them with normative documents (I assume it
>Partly agreed. It's indeed an attempt to satisfy those people who claim 
>that the regexp isn't good enough.

We can turn the regular expression into a concise ABNF grammar if that
helps, we might also adapt it if that is found to be necessary, but I do
not see a reason why hundreds of lines of prose code or JavaScript code
would help (and anyone who would like to have that anyway can easily de-
rive it from the expression or from a grammar).

I note that I have not seen much commentary on what's wrong with using
the regular expression for fault-tolerant parsing, I've mostly seen the
usual distractions like pointing out how it's not normative. There are
some problems with it in that it leads to behavior that is inconsistent
with some implementations (does "$:" have a scheme of "$" where "$" is
a character not allowed in the scheme componant?) How would we get from
here to talking about such issues, if we want to address this at all?
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Sunday, 3 July 2011 16:45:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:14:42 UTC