Re: [apps-discuss] Scope of RFC3986 and successor - what is a URI?

[Graham Klyne <[e-mail]>]

On 18/01/2015 21:09, Larry Masinter wrote:
>>          The primary role of a URI parser is to simply decide if a given
>>          string is or is not a valid URI.  A parser can only be
>>          RFC3986-compliant in the extent to which it correctly makes
>>          this determination in accordance with RFC3986.
>
> I disagree with both these sentences, at least as I understand the
> terms "primary role", "parser", "valid", "compliant".
>
> The primary role of a parser http://en.wikipedia.org/wiki/Parsing#Parser
> is to take input data and give a structural representation of the input,
> while checking for correct syntax in the process.

At risk or going down an unhelpful rathole...

A key phrase in your quote is "while checking for correct syntax".

In the absence of a definition of a "structural representation" in RFC3986, I 
don't see how RFC3986 compliance can extend beyond the determination of correct 
syntax, which is what I meant by "valid".

>
> Deciding validity is the role of a http://en.wikipedia.org/wiki/Validator.

Per that definition, I would say a parser is (or incorporates) a particular kind 
of validator.

#g
--