microid AT lists.ibiblio.org
Subject: Microid mailing list
List archive
Re: [Microid] Augmented Backus-Naur Form Scheme issues?
- From: Terrell Russell <terrellrussell AT gmail.com>
- To: microid AT lists.ibiblio.org
- Subject: Re: [Microid] Augmented Backus-Naur Form Scheme issues?
- Date: Tue, 14 Aug 2007 21:04:00 -0400
Peter Saint-Andre wrote:
> But I'm not sure what to do about it now. We could:
>
> 1. Change the separator to "_" or somesuch.
>
> Pro: Conforms to RFC 3986.
> Con: Breaks existing implementations.
>
> 2. Provide guidance for handling of "+".
>
> Pro: Doesn't break existing implementations.
> Con: Potentially confusing; does not conform to RFC 3986.
>
> The spec writer in me likes (1), but the documentation guy in me prefers
> (2) since I really don't like to break existing implementations.
>
> Peter
>
Considering there are very few implementations in the wild - it seems
we'd be better serving the future by making things RFC 3986 conformant
as soon as possible.
I'd guess that most of the people publishing live MicroID in the wild at
this time are paying attention to these conversations and would change
their code pretty soon.
Is there a place in the spec to suggest that MicroIDs encoded with a
single '+' should be parsed as separated with '+'? Another backwards
compatibility footnote?
Terrell
-
[Microid] Augmented Backus-Naur Form Scheme issues?,
Brian Suda, 08/14/2007
-
Re: [Microid] Augmented Backus-Naur Form Scheme issues?,
Peter Saint-Andre, 08/14/2007
- Re: [Microid] Augmented Backus-Naur Form Scheme issues?, Terrell Russell, 08/14/2007
-
Re: [Microid] Augmented Backus-Naur Form Scheme issues?,
Yaniv Golan, 08/15/2007
-
Re: [Microid] Augmented Backus-Naur Form Scheme issues?,
Peter Saint-Andre, 08/15/2007
- Re: [Microid] Augmented Backus-Naur Form Scheme issues?, Fred Stutzman, 08/15/2007
-
Re: [Microid] Augmented Backus-Naur Form Scheme issues?,
Peter Saint-Andre, 08/15/2007
-
Re: [Microid] Augmented Backus-Naur Form Scheme issues?,
Peter Saint-Andre, 08/14/2007
Archive powered by MHonArc 2.6.24.