Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anchors should be anchors, links should be links, and includes should be includes. #5

Open
leoj3n opened this issue Jan 7, 2013 · 4 comments · May be fixed by #23
Open

Anchors should be anchors, links should be links, and includes should be includes. #5

leoj3n opened this issue Jan 7, 2013 · 4 comments · May be fixed by #23

Comments

@leoj3n
Copy link

leoj3n commented Jan 7, 2013

Everyday terminology refers to the semantic <a> element as a "link" OR an "anchor", giving the tag a double meaning.

Specs refer to a "link" as what everyday terminology refers to as an "include".

This is a serious barrier of entry for anyone trying to learn HTML. "I've been told links are what take you to new documents my whole life, but why are they something completely different in HTML land?", students ask. "Because the HTML gods made it so", I tell them.

Everyday peoples understand the (HUGE) difference between a website "link" and an "anchor". It's an easy concept, conceptually. However, once they get into HTML, real-world understanding doesn't map to the reality ( cough poorly invented conventions cough ) of HTML-fairytale-land.

I've always had this question, but figured there was some mystical force at work that justified such idiotic terminology. After exploring the deepest caverns of HTML I can finally put that myth to rest, and take a stand against this retardation!

A ludicrous proposal: a "link" actually be what normal people understand a "link" to be. This means <html:a> or possibly <html:anchor> will only be used for ANCHORS and <html:link> will only be used for LINKS in the true sense of the term. Now that <html:link> is taken, we must endow a new term for the inclusion of source files; I propose <html:include>.

Please poke holes in this philosophy if you can, because from where I sit it seems sound; but perhaps I missed one of those secret underground passageways that leads you to the bonus level where there's flying pigs and this all makes sense.

PS: "HTML6" seems like a splendid idea, regardless of if my points are valid.

@OscarGodson
Copy link
Owner

Yeah, totally, <a> isn't very semantic at all when you're not talking about an anchor and I've always been curious about that too, "why is an anchor also a link?". I'm not sure I follow the include idea tho. Include implies including the source of something on the page. Like if it were:

<p>
<html:include src="/helloworld.html"></html:include>
</p>

I'd assume it was going to put the content of /helloworld.html on the page between the <p> tags since the keyword include is used in programming languages that way.

@icalvo
Copy link

icalvo commented Jan 9, 2013

<html:import> or <html:using>?

@cshaa
Copy link
Contributor

cshaa commented May 10, 2013

It could be this way:
<html:link> for hyperlink to another page
<html:anchor> for anchor (but maybe it's too long, anch or a could be enough)
<html:using> for scripts and style sheets
<html:alter> for alternatives like RSS or Atom feeds

cshaa added a commit to cshaa/html6-feat-OscarGodson that referenced this issue Aug 12, 2013
@cshaa cshaa linked a pull request Aug 12, 2013 that will close this issue
@cshaa
Copy link
Contributor

cshaa commented Oct 4, 2013

And what about removing html:a completely - leaving just href or html:href attributes would be great. Even W3C was trying to do this in their XHTML2. Less tags, less writing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants