Anonymous user
Talk:Find URI in text: Difference between revisions
m
→What actually parses as a URI may not be what is intended by the task author: grammar
m (→What actually parses as a URI is not what is intended by the task author: tweaked heading is -> may) |
|||
Line 6:
::: i suppose if the url has a delimiter like quotes or <http://go.here/to this place>, then i don't see why not. it's depends on the ability to figure out the users intent. and on the application. depending on where the parser is used there might even be an opportunity to verify that a url actually exists. (now that would actually be an interesting feature: you type some text on some website, and the browser or server tells you that the url you typed does not exist)--[[User:EMBee|eMBee]] 03:38, 6 January 2012 (UTC)
== What actually parses as a URI may not be what
I just had a look at this against the cited RFC. I believe the task description is inconsistent with the syntax spelled out in the RFC. For instance,
* Even though it doesn't make sense to a person "stop:" is a valid scheme and parses as a URI through 'path-empty'. To rule it out you must know what the valid schemes are.
| |||