Pony99CA wrote:It's harder because "yours" requires extra conditions to not return non-tagged URLs.
What kind of extra condition? It's simply tagged as a paragraph with nothing extra so it's plain text within a paragraph. No exclusion is needed.
Your hypothetical search engine only looks in A tags for URLs, so yours needs to exclude URLs outside of A tags. My hypothetical search engine grabs all URLs in an HTML file, so mine doesn't need to exclude anything (or write a harder, slower regular expression).
Ger wrote: Pony99CA wrote:
True, but what is HTML 5 doing?
HTML5 is doing the future. This whole topic is about whether or not to include http:// in present day.
And I thought there were HTML 5 browsers out already (like on the iPhone).
HTML 5 final
is the future; HTML 5 draft
is here today. My point was that, if the need were proven, somebody could update the draft in short order. (I'm not saying that it will be updated, merely that it could
Also, ignore the future at your own peril. Even if search engines today don't search for URLs outside of A tags, that doesn't mean that future engines won't. I wouldn't want to have to go back and update all of my content to add the protocol to content I posted all over the Internet.
As I said, adding the protocol won't hurt and it might help (today or in the future), so why not do it?