Hacker News new | past | comments | ask | show | jobs | submit login

Is there any evidence this matters at all?



Aside from, uh, being affected by it? I don't know what "matters" means to you.


Matters how? Microdata seems irrelevant to begin with, ignored by search engines or anything else (at least in my limited tests), and faking it with semi-semantic class names alongside auto generated ones will do what, exactly?

Like, what is this additional data layer actually for? What humans or software use it?


> Matters how?

I don't know. That's your word. You're the one who wrote it. I'm asking you.

> faking it with semi-semantic class names

Huh?


I mean why go through all this effort at all?


You're going to have to put more effort communicating that you've thought about what you're asking (including effort in laying out what you're even asking) if you expect any effort to be put into a response. Of your three comments here, two out of three are (ambiguous) one-liners, and three out of three come off like you took all of 10 seconds to bang them out before hitting the "reply" button.

Even if that happens, I'm past 50/50 on the question of "is this even worthy of further engagement?" at this point. (It's pretty much at a 100% "no".)


It's fine if you don't want to keep responding... but in case you want clarity, what I was asking is "Why should anyone spend any time at all adding microdata, or failing that, using CSS class names to emulate microdata?"

Your original comment read to me like, "Here's how you can do something similar using CSS class names without using the microformats standards." My question was, why do either?

With microformats, at least it's supposed to be a machine-parseable standard for crawlers and the like. It never got much traction, and of the times I've used it, absolutely no measurable benefits (in terms of SEO or indexability) were seen at all.

With descriptive CSS class names you come up with yourself, not adhering to any standard, it seems even less likely that any crawler would be able to use them meaningfully. It's even less "semantic" than microdata or semantic HTML5 tags.

So my question was, what is the benefit of doing that? Are these class names just reminders for yourself, months later, so you can remember what a certain component was supposed to do? Or does it help your development/debugging/testing workflow somehow (such as being able to easily target widgets in the DOM for automated testing, perhaps?)

I wasn't trying to dismiss your comment, just trying to understand the value of putting in that effort. I'm sorry if it came across as flippant, there's just a lot that gets lost in online posts. Anyway, feel free to elaborate if you'd like, but if you just want to move on, that's totally fine too :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: