Re: ISSUE-18: How do we parse "18." in Turtle?

On Wed, Mar 30, 2011 at 6:00 PM, Pat Hayes <phayes@ihmc.us> wrote:

> If it ain't broken, don't fix it. And if nobody noticed this until now, I
> submit that it is not broken.
>
> Pat
>

It ain't broken in SPARQL because of the explicitly stated rule that longest
match wins, meaning there's only one way to tokenize a sequence of
characters.

I'm fine with using the same rule in Turtle, but I don't see any such
language in the Jan 2010 editor's draft.

-Alex



>
> On Mar 30, 2011, at 3:41 PM, Peter Frederick Patel-Schneider wrote:
>
> > From: Nathan <nathan@webr3.org>
> > Subject: Re: ISSUE-18: How do we parse "18." in Turtle?
> > Date: Wed, 30 Mar 2011 15:18:55 -0500
> >
> >> Andy Seaborne wrote:
> >>> By the way, this is not the only place that "longest token" is
> important:
> >>>
> >>> { :x :p18. }
> >>>
> >>> is that ":p1 8."  or ":p 18" or ":p18" and an error?  That has not been
> >>> a practical issue raised.
> >>
> >> Goodness, you're right, I've just noticed that there's hardly any white
> >> space requirements in the EBNF, which means a whole lot of garbage can
> >> be produced of course, for example this is a list of three integers
> (123).
> >>
> >> Needs fixed.
> >
> > I don't think that lists *need* to be fixed.  See one of my earlier
> > message for more on this.
> >
> > This is separate from *should" be fixed, but I don't think that this
> > should be fixed either.
> >
> > peter
> >
> >
>
> ------------------------------------------------------------
> IHMC                                     (850)434 8903 or (650)494 3973
> 40 South Alcaniz St.           (850)202 4416   office
> Pensacola                            (850)202 4440   fax
> FL 32502                              (850)291 0667   mobile
> phayesAT-SIGNihmc.us       http://www.ihmc.us/users/phayes
>
>
>
>
>
>
>