Slashdot Mirror


Schema.org — Google, Microsoft and Yahoo! Agree On Markup Vocabulary

aabelro writes "Google, Microsoft and Yahoo! have decided to propose a common markup vocabulary, Schema.org, based on the Microdata format, simplifying the job of webmasters who want to give meaning to their web pages' content." Manu Sporny, chair of the W3C group that created RDFa, added his (personal) dissenting opinion about Schema, calling it a 'false choice,' and saying, "The entire Web community should decide which features should be supported – not just Microsoft or Google or Yahoo."

192 comments

  1. All I'm hearing is... by Cryacin · · Score: 0, Troll

    WAAAHHH!!!! The W3C didn't make up this standard!!! We're still debating what the dickens to define as HTML5!

    No fair that the other children are running off with their ball to do their own thing...

    --
    Science advances one funeral at a time- Max Planck
    1. Re:All I'm hearing is... by Anonymous Coward · · Score: 1

      indeed. they had a chance to do this right when defining rdf and xml (two concepts that should be complementary,
      but are completely detatched), and they pretty much failed to deliver anything that qualified as 'sematic web', not that
      xml hasn't found plenty of other uses.

      skimming the proposals, they both seem less than ideal for both authors and analyzers, but basically
      the same. who can really fault an industry group for floating a standard without wanting to get stuck
      in a decade of w3c limbo?

    2. Re:All I'm hearing is... by Samantha+Wright · · Score: 4, Interesting

      For those out of the loop: this is funnier when you are aware of a certain alarmingly long schedule proposed by Ian Hickson, which would not see HTML 5 completely finished until 2020 or 2022 depending on your definition.

      Incidentally, this problem is similar to why the Athenians abandoned democracy (lack of rapid response) and has been presented as an explanation for why Lisp isn't as popular as it once was (endless disagreements about how to do things.)

      The really remarkable part, though, is that they're making any progress at all with HTML5, so some kudos is in order.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    3. Re:All I'm hearing is... by rubycodez · · Score: 4, Funny

      ooo, snide Perl 6 remark would go here if I were immature

    4. Re:All I'm hearing is... by lennier · · Score: 4, Funny

      ooo, snide Perl 6 remark would go here if I were immature

      Perl, wasn't that an early pre-release beta of Python...?

        "Three signs shall there be before the end: the duke of atoms shall walk forever, the sixth pearl be released, and the freeman lift his crowbar thrice..."

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    5. Re:All I'm hearing is... by exomondo · · Score: 0

      WAAAHHH!!!! The W3C didn't make up this standard!!! We're still debating what the dickens to define as HTML5! No fair that the other children are running off with their ball to do their own thing...

      Not only that but he seems to ignore the fact that it's a proposed vocabulary and the entire web community can and will be the ones to decide if it is to be used or not.

    6. Re:All I'm hearing is... by interkin3tic · · Score: 2

      It does seem true to me that in general, if someone says "Wait, not enough people participated in making that decision!!!" they
      -don't actually care about the number of people making the decision so much as they care that they were not ONE of that number
      -are more interested in trying to sound smart than doing anything.
      or
      -are opposed for some reason to the outcome of the decision but don't have any really convincing arguments to make against it

      "The entire Web community should decide which features should be supported." Yeah, uh, the internet troll association just called. The features they want are whatever features no one else wants, and the features they're opposed to are any features that anyone else wants. Also they have some pictures from the .cx domain they want to submit for your consideration.

      We also made a suggestion box for features to be supported, but they're all "FRIST SUGGESTION POST!!!1!!!!" for some reason.

      Oh, and since we're consulting the whole community, the RIAA, MPAA, and Sony have several boxes of suggestions for features, but you can't look at them, they're mega-super-duper secret. I've just been sued for even mentioning the suggestions' existences.

    7. Re:All I'm hearing is... by countertrolling · · Score: 3, Interesting

      It doesn't matter what standard they float. It will be dumped in less than five years anyway for the next big gimmick.. I remember a time when real standards would last 50 years or more. You know.. like film, phones, roads, electricity, NTSC, PAL, ohm's law, arithmetic, spelling of words, money...

      --
      For justice, we must go to Don Corleone
    8. Re:All I'm hearing is... by blue+trane · · Score: 1

      Note: poster takes one sentence from the wikipedia summary, and infers that the article cited supports her (?) claim. In fact, the sentence referred to reads: "One downside was that the new democracy was less capable of rapid response." The downside is not mentioned again in the lengthy section. Many other criticisms of Athenian democracy are discussed at much greater length (including its extreme severity, its overreaching its own laws, and its conviction of Socrates) than the one she (?) chooses to highlight.

      In conclusion, "lack of rapid response" was not "why the Athenians abandoned democracy", as the poster blithely asserts; the source cited provides no supporting evidence for the claim.

    9. Re:All I'm hearing is... by Samantha+Wright · · Score: 2

      I apologise; it appears that I conflated some details of the Four Hundred with the democracy that it interrupted.

      You could have been more polite about it, though.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    10. Re:All I'm hearing is... by Anonymous Coward · · Score: 1

      well, i think its a bit far afield, but thanks about the article about lisp. i still believe that its an historical accident rather
      than something fundamental about expressive language frameworks, but alot of points rang true.

      here, there is just a syntactic requirement to express relational data inline, or less, just tags. they aren't event discussing any
      overreaching semantic system where such declarations might be said to have some meaning.

      here is the antipode to lisp, billion dollar multi-year arguments about whether we should say or

    11. Re:All I'm hearing is... by Anonymous Coward · · Score: 0

      There be a fourth sign: and the Hurd shall run Free across the land...

    12. Re:All I'm hearing is... by Anonymous Coward · · Score: 0

      Isn't part of the problem of coming up with a standard via the W3C involve members of the W3C like Microsoft, Google, and Yahoo, and others not agreeing on things and holding up the release of said standard? And standards being butchered by trying to satisfy too many members wants. Like too many cooks spoiling the broth?

    13. Re:All I'm hearing is... by omfgnosis · · Score: 1

      Polite? This is Slashdot. But to be fair, being polite rarely gets anything other than passed over here.

    14. Re:All I'm hearing is... by omfgnosis · · Score: 1

      You mean... the entire web community "can" or "will" be the ones to decide whether they will cooperate with the source of most, if not almost all, of their traffic? And what happens when Google, Microsoft and Yahoo agree to index the syntax they agreed to propose? That's a lot of weight to be pitted against. Even more weight than that (frankly, Apple and Adobe) which undermined the "web community" by choosing h.264 over any free alternative. Don't mistake the fact that there's a "standards process" with "public comment" for anything resembling the will of the people who have to actually consume this stuff.

      And don't get me wrong; most of HTML5 is a welcome departure from the W3C direction, despite being dictated by a handful of huge corporations. It's just silly to pretend that that departure came from anything other than a handful of huge corporations.

    15. Re:All I'm hearing is... by jgagnon · · Score: 1

      The computing world moves at a MUCH faster pace because it needs to evolve... 50 year computer standards would be a TERRIBLE idea.

      --
      Remember to maintain your supply of /facepalm oil to prevent chafing.
    16. Re:All I'm hearing is... by rubycodez · · Score: 1

      and the Norseman's codes shall possess and dominate the workbench ciphering apparatus for all peoples in that year,

      (pauses to snort more volcanic fumes)

      and the Orders of the Red Whorl and the Arch of Blueness shall claim the deceived followers from the once-righteous wealthy African merchant, for his falling into great sin, of confounding the Portal of Knowledge with his evil Unification spell that bends the eyesight and hinders the labors of man

    17. Re:All I'm hearing is... by GameboyRMH · · Score: 1

      Slightly off-topic but...

      Ancient authors were almost invariably from an elite background for whom giving poor and uneducated people power over their betters seemed a reversal of the proper, rational order of society. For them the demos in democracy meant not the whole people, but the people as opposed to the elite. Instead of seeing it as a fair system under which 'everyone' has equal rights, they saw it as the numerically preponderant poor tyrannizing over the rich.

      LOL some things never change...

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    18. Re:All I'm hearing is... by petermgreen · · Score: 1

      The thing is that web standards are only of use if all the major browser vendors (that is MS, mozilla, apple and google) actually support them. Since the w3c has no power to force browser vendors to implement their standards and since many of the vendors are deeply opposed on key issues (such as video codecs) they are stuck between a rock and a hard place.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    19. Re:All I'm hearing is... by exomondo · · Score: 1

      You mean... the entire web community "can" or "will" be the ones to decide whether they will cooperate with the source of most, if not almost all, of their traffic? And what happens when Google, Microsoft and Yahoo agree to index the syntax they agreed to propose?

      Then they will only get those sites that have chosen their standard. If RDFa is indeed superior then a search engine utilising it will ultimately win out over those who choose to ignore it. I'm guessing that unless it is significantly better, RDFa will eventually lose out by virtue of it being a mediocre competitor instead of having real tangible advantages.

      That's a lot of weight to be pitted against. Even more weight than that (frankly, Apple and Adobe) which undermined the "web community" by choosing h.264 over any free alternative.

      And h.264 has been widely adopted simply because it's downsides over a free alternative don't affect the decision-makers in a measurable way, why push back against these companies when there is so little reason to do so?

    20. Re:All I'm hearing is... by omfgnosis · · Score: 1

      Then they will only get those sites that have chosen their standard. If RDFa is indeed superior then a search engine utilising it will ultimately win out over those who choose to ignore it.

      All of the major search engines have coordinated to support an opposing standard. It's incredibly naïve to suggest that merit alone is enough to challenge collusion of massive corporations, especially when those massive corporations represent almost the entire market. Merit doesn't dictate which standard wins; power does.

      And h.264 has been widely adopted simply because it's downsides over a free alternative don't affect the decision-makers in a measurable way

      Right, it just affects everyone else in a negative way. Thanks for demonstrating my point.

      why push back against these companies when there is so little reason to do so?

      There's tremendous reason to do so. h.264 represents a huge barrier to entry for a huge majority of people into a huge segment of the web. Fortunately, this is a space where corporate collusion is not nearly so great, and there is still a chance that the fates aren't sealed.

    21. Re:All I'm hearing is... by exomondo · · Score: 1

      All of the major search engines have coordinated to support an opposing standard. It's incredibly naïve to suggest that merit alone is enough to challenge collusion of massive corporations, especially when those massive corporations represent almost the entire market. Merit doesn't dictate which standard wins; power does.

      If content producers don't jump on board the search engines have no content, but they will jump on board because benefit of opposing it just isn't there. Why fight it if there's next to nothing to gain?

      Right, it just affects everyone else in a negative way.

      It doesn't affect end users in a negative way and those who make the decision to use h.264 do so even though solutions like WebM exist.

      Thanks for demonstrating my point.

      I didn't demonstrate your point at all, you just wrote something that has nothing to do with what i wrote and then followed it with that sentence. I could do the same thing.

      There's tremendous reason to do so. h.264 represents a huge barrier to entry for a huge majority of people into a huge segment of the web.

      It represents a barrier to entry for web browser developers, that is not a huge segment of the web or a majority of people.

    22. Re:All I'm hearing is... by omfgnosis · · Score: 1
      Do you realize your whole might-makes-right argument totally undermines the proposition that merit will determine the chosen standard?

      If content producers don't jump on board the search engines have no content, but they will jump on board because benefit of opposing it just isn't there. Why fight it if there's next to nothing to gain?

      You suggested before that the merit of a better standard would be enough to overcome the choice of the major corporations. Now, by arguing that the "benefit of opposing it just isn't there", you're begging the question—you're saying that if corporations use their leverage to manipulate choice, then the merit is determined by that manipulated outcome. You can't have it both ways.

      It doesn't affect end users in a negative way

      Yes, of course it does. End users can't (currently) have both an open Internet and HTML5 video. Either trade-off is a negative for end users.

      and those who make the decision to use h.264 do so even though solutions like WebM exist.

      Right... but not because the merits of h.264 outweigh those of WebM, only because there is a massive barrier to entry for WebM and in the short term content producers/distributors will be losing a huge audience if they go WebM-only. In a world where the potential audience wasn't fragmented by codec support, content producers/distributors would almost certainly choose WebM, on monetary cost alone; but they (currently) can't.

      I didn't demonstrate your point at all

      Yes, you did. You demonstrated that the choice is made by the powerful, based on how the choice affects those making the choice, regardless of how it affects others.

      you just wrote something that has nothing to do with what i wrote and then followed it with that sentence.

      You wrote: "downsides over a free alternative don't affect the decision-makers in a measurable way". How does "it just affects everyone else in a negative way" have nothing to do with that? It's a direct response.

      It represents a barrier to entry for web browser developers, that is not a huge segment of the web or a majority of people.

      It's not just a barrier to entry for web browser developers; it's a barrier to entry for web site/application developers as well as content producers (potentially *everyone*).

    23. Re:All I'm hearing is... by exomondo · · Score: 1

      Do you realize your whole might-makes-right argument totally undermines the proposition that merit will determine the chosen standard?

      Merit is judged by the majority, pretty obvious.

      You suggested before that the merit of a better standard would be enough to overcome the choice of the major corporations. Now, by arguing that the "benefit of opposing it just isn't there", you're begging the question—you're saying that if corporations use their leverage to manipulate choice, then the merit is determined by that manipulated outcome. You can't have it both ways.

      Cost is always a factor in determining merit, it's pretty simple. One of the merits is that the major corporations support Microdata, so alternatives had better be able to counter that merit.

      Yes, of course it does. End users can't (currently) have both an open Internet and HTML5 video. Either trade-off is a negative for end users.

      How is that a negative for end users? It might be news to you but the *vast* majority of people don't give a fuck about openness, and they don't see lack of it as a negative. Yes some of the geek minority screams about the virtues of openness but most people don't care, the proof is all around you.

      Right... but not because the merits of h.264 outweigh those of WebM, only because there is a massive barrier to entry for WebM

      Again with your 'massive barrier to entry' bullshit, there is no barrier to entry for WebM, it's free and the most popular browsers support it.

      Yes, you did. You demonstrated that the choice is made by the powerful, based on how the choice affects those making the choice, regardless of how it affects others.

      No, 'the powerful' is a rubbish term you made up, what I said is the 'decision-makers', as in the people who make the decision to use the format, which is anyone doing content production/distribution.

      You wrote: "downsides over a free alternative don't affect the decision-makers in a measurable way". How does "it just affects everyone else in a negative way" have nothing to do with that? It's a direct response.

      Because what i wrote in no way implies that, just because it doesn't affect the decision-makers in a measurable way *does not* mean it affects everyone else in a negative way, your assumption just shows your desperation to support your idea with information that simply is not there.

      It's not just a barrier to entry for web browser developers; it's a barrier to entry for web site/application developers as well as content producers (potentially *everyone*).

      No, that's bullshit. All you've done is make this claim that it has a huge barrier to entry, it doesn't appear you even know what it is you're claiming it to be.

    24. Re:All I'm hearing is... by omfgnosis · · Score: 1

      Merit is judged by the majority, pretty obvious.

      Complete claptrap. But even granting it, just for the sake of argument, when the hell did the leverage of a coordinated market-dominating force become "the majority"? How is "the majority" a response to "might-makes-right"?

      Cost is always a factor in determining merit, it's pretty simple.

      More claptrap. Cost might *outweigh* merit, but it doesn't contribute to it.

      One of the merits is that the major corporations support Microdata, so alternatives had better be able to counter that merit.

      More might-makes-right. The might of major corporations is not a merit, it's just power. Yes, the reality is that winning against a power consensus takes a great deal of leverage; that doesn't mean that failing to win is any kind of a statement of merit.

      How is that a negative for end users?

      Increased cost every step of the way, increased restrictions every step of the way, increased exposure to litigation every step of the way, increased likelihood of abuse of IP protection every step of the way.

      It might be news to you but the *vast* majority of people don't give a fuck about openness, and they don't see lack of it as a negative. Yes some of the geek minority screams about the virtues of openness but most people don't care, the proof is all around you.

      Whether or not people are harmed isn't determined by whether they "give a fuck" or "see it as a negative". The *vast* majority of people are also unaware that they are paying a premium for h.264, that the services they use are also paying a premium that could otherwise be used to improve those services, that there are enormous legal restrictions on their use of that codec, and that they are potentially targets of litigation if any component of that is either untoward in their use of IP or is a convenient or useful target. Being unaware of things doesn't make the things you're unaware of nonexistent. It just makes them more dangerous.

      Again with your 'massive barrier to entry' bullshit, there is no barrier to entry for WebM, it's free

      There's a massive barrier to entry. Most video content on the web is in h.264 or VP6. 73% of users (see below) can't use it. Getting web site/application developers to support it is a tough sell, not because they wouldn't love the reduced cost and liability, but because the traffic has to be there to justify the cost. Traffic != merit.

      and the most popular browsers support it.

      More claptrap. IE (around 55% of web users) does not support it at all, no version of Firefox before 4.0 (about 11%), no version of Safari (7%) and no version of Opera before 10.60 (negligible %). 73% of browsers in use don't support it. (Source: marketshare.hitslink.com)

      No, 'the powerful' is a rubbish term you made up, what I said is the 'decision-makers'

      Explain how they differ.

      as in the people who make the decision to use the format

      Google, Microsoft and Yahoo are not people. They're powerful corporations.

      which is anyone doing content production/distribution.

      That's not who's making the choice.

      Because what i wrote in no way implies that

      I didn't say you implied that, I responded with it. It's a *relevant response*, which you can agree or disagree with, but it *has something to do with it*.

      just because it doesn't affect the decision-makers in a measurable way *does not* mean it affects everyone else in a negative way

      It doesn't *mean* that, it just *is the case*.

      your assumption just shows your desperation to support your idea with information that simply is not there.

      Assumption? It's an opinion. The information

    25. Re:All I'm hearing is... by exomondo · · Score: 1

      More claptrap. Cost might *outweigh* merit, but it doesn't contribute to it.

      Rubbish, if you have 2 options and the deciding factor is that one is cheaper than the other then obviously the cheaper will win. Do you not know the definition of 'merit'? cost *does* contribute, cost is a factor when deciding desirable traits!

      Increased cost every step of the way, increased restrictions every step of the way, increased exposure to litigation every step of the way, increased likelihood of abuse of IP protection every step of the way.

      The ramblings of an ignorant idiot, clearly have no idea what you're talking about and you've just bought into whatever the WebM advocates throw out, if you actually knew anything about the licensing you wouldn't be posting so much obvious rubbish.

      Whether or not people are harmed isn't determined by whether they "give a fuck" or "see it as a negative".

      It doesn't matter, as we see in the markets the benefit outweighs the 'harm', this 'harm' that you speak of is of no concern to the end users.

      The *vast* majority of people are also unaware that they are paying a premium for h.264

      That premium is so incredibly low that the people don't care about it.

      There's a massive barrier to entry. Most video content on the web is in h.264 or VP6. 73% of users (see below) can't use it.

      Absolute bullshit, 73% of users don't want to use it. It isn't that they can't, it's that they don't want to as they see no benefit in it, there is no advantage for them.

      More claptrap. IE (around 55% of web users) does not support it at all, no version of Firefox before 4.0 (about 11%), no version of Safari (7%) and no version of Opera before 10.60 (negligible %). 73% of browsers in use don't support it.

      No shit, old browsers don't support HTML5 either but we don't just throw away HTML5 as having 'too big of a barrier to entry'. We have new browsers, freely available to upgrade to that support these new features, welcome to reality.

      No, 'the powerful' is a rubbish term you made up, what I said is the 'decision-makers'

      Explain how they differ.

      You're that thick that you can't figure it out for yourself? Anyone choosing to use a format is the 'decision-maker'.

      Google, Microsoft and Yahoo are not people. They're powerful corporations.

      Then use 'entity' if you have so much trouble working that out.

      That's not who's making the choice.

      Oh ok my video magically encodes itself, of course i make the choice!

      just because it doesn't affect the decision-makers in a measurable way *does not* mean it affects everyone else in a negative way

      It doesn't *mean* that, it just *is the case*.

      Rubbish, you've got no facts yet you continue to spread this FUD. If it affected the user in a negative way that anyone actually cared about we would all be grabbing one of the many freely available web browsers or plugins that support WebM and everyone would bail on h.264, yet we aren't.

      The *cost* alone is a barrier to entry

      There is no cost barrier to entry, but if you weren't just making up this shit as you went along you would actually know this. Stop spreading FUD based on your own ignorance and actually *read the license*.

      While WebM doesn't address most of the IP litigation concerns, it does address the cost concerns

      1.2c per month per subscriber over 100,000, that's nothing when you have a subscriber-base that big, and that is certainly beyond the point of market entry, thus proving that your comment that cost is a barrier to entry is just a figment of your own ignorance and has no factual basis whatsoever.

    26. Re:All I'm hearing is... by omfgnosis · · Score: 1

      idiot

      Your argument has been building in this direction all along. Whatever the merits of your position, I don't have the time or energy for people whose argumentation depends on insult instead of substance. Take care.

    27. Re:All I'm hearing is... by exomondo · · Score: 1

      Your argument has been building in this direction all along. Whatever the merits of your position, I don't have the time or energy for people whose argumentation depends on insult instead of substance. Take care.

      Your entire position is based on your assumptions rather than any actual facts (like the details within the actual license) - as demonstrated by your ignorant comments - how can anyone taking that position *not* be an idiot.

    28. Re:All I'm hearing is... by thePuck77 · · Score: 1

      If it's to keep up with the hardware and software innovations at the speed they actually happen, then any standard needs reevaluation at a lot smaller intervals than five years. I would say three years, at most. "Real standards" last based on their context, which means the technology they govern. And most of those "standards" changed over and over again over their years of use. Unless you would like to go back to having to wait and hour for a film exposure to set, tell an operator who you're calling to make a connection (on a party-line, perhaps?), drive on packed oil-and-dirt roads, DC-based power only, whilst spaking olde Ainglish.

      --
      "We live as though the world were as it should be, to show it what it can be." - Joss Whedon via Angel
    29. Re:All I'm hearing is... by blue+trane · · Score: 1

      Note how poster attempts to divert attention from her (?) willful (arguably) mis-citation (to support her [?] larger point) by criticizing the correction's tone. Does political correctness trump facts?

    30. Re:All I'm hearing is... by Samantha+Wright · · Score: 1

      I guess we'll just go with "IHBT, I hope it makes you feel better about yourself" at this point. Unless you really want to go on a pedantic rampage.

      We could do that, you and I: picking through each others' entire comment history, drawing attention to typos and logical inconsistencies until the end of time. I don't know who would win. I don't really want to find out. But don't assume it would be you.

      However, it would not be very productive, and if Slashdot hadn't alerted me that your reply had been made, there would most likely be no one whatsoever to "note" your statement at all, excepting perhaps Qzukk, the only person to have replied to any of your journal posts in the past two months. And that's without consideration for your—frankly, quite enlightening—Tripod site, which does not appear to be written as a satire or a character study.

      Here's a hint: monkey say, monkey do. If you want to interact with others, don't do it by going out of your way to insinuate and accuse that their statements have been insufficiently rigorous. At the time you do it, it may feel like you're a hero, defending the coherence and validity of truth, but you'll quickly find that your would-be audience has little interest in the kind of pedantry that belongs in a thesis defence.

      As a small testament to that, I point out that my response to you received a "+1, Underrated" moderation, whereas yours was spared this minor honour. This suggests that someone climbed over your initial post, left it untouched, and gave the point to mine instead. Admittedly, this is circumstantial evidence, as I could be an army of sockpuppets manipulating the whole thing—and, hey, you seem like a pretty solipsist guy, so let's pretend I am—or merely have friends, but in general it appears that many of your more analytical comments (disclaimer: I only checked down to March 14th) have garnered a similar level of attention. While they do not exhibit the same degree of viciousness as your appearance in this thread, an unverified skim suggests that in context most of your other analytical posts have a moderately abrasive tone. Perhaps they were meant to be troll posts, but they certainly didn't get a rise out of any moderators. (I hope you find it sound reasoning when I tell you that Slashdot is in fact big enough that I did not personally oversee the decision to leave all of them unmoderated.)

      This is still circumstantial evidence, of course, but I feel it is a somewhat stronger defence of the point which I wish to make: your style of commenting gets you ignored more often than not. At this point, it seems like a lovely little day-trip into marquis1740.tripod.com is in order, to perhaps come up with an explanation as to why that might be the case, but I don't aim to be merely offensive. My thesis is that you should work on your social skills. It will make you a happier person.

      Not unrelatedly at all, arguing about gender on the internet is simultaneously very impolite and in violation of Occam's razor. If you can't handle (a) transgendered people or (b) the possibility that someone might present themselves online inconsistently with their physical person, and you're so upset about one or both of those that you're willing to "take it out" out on a random passerby in a fashion that compromises the tone of what was otherwise a perfectly respectable and level-headed piece of criticism, I strongly invite you to stop posting on Slashdot and take up permanent residence at 4chan, where such things are much more commonplace and even socially acceptable.

      But I will not be your self-esteem punching bag. If you feel like you really, really still need one, please forgo my suggestion that you move to 4chan and simply get a therapist. That's what they're for.

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  2. Not to worry... by SwedishChef · · Score: 5, Funny

    Microsoft will break this one, too.

    --
    No one ever had to evacuate a city because the solar panels broke!
    1. Re:Not to worry... by Anonymous Coward · · Score: 5, Insightful

      The proposal is itself breaking html. This time, Google and Yahoo are in with the "extending". The vague promise of better search positions will drive web developers to completely muck up their html output. There is no reason not to re-use the Dublin Core.

    2. Re:Not to worry... by Anonymous Coward · · Score: 0

      It's not broken, it's "html 5".

    3. Re:Not to worry... by Homburg · · Score: 2

      So they're breaking HTML by following the HTML5 specification?

    4. Re:Not to worry... by neokushan · · Score: 0

      Ahhh Slashdot, where bashing Microsoft for no good reason is always a good way to get modded up.

      Or shall I rephrase that...[citation needed]?

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    5. Re:Not to worry... by game+kid · · Score: 3, Insightful

      The latter implies the former. I say go right back to XHTML 1.0 Strict (the last standard that didn't have a broken DTD) and concentrate on finally getting all the browsers to better implement SGML. For example, all of the itemprop, itemscope, and itemtype crap could be done better with processing instructions (say, pop an <?itemscope ?> tag thing and poof, done), without fucking up the markup. schema.org is trying (among other things, I guess) to help search engines better understand the page,* and PIs were made to tell applications how to process data, so it's a matter of getting them to play The Dating Game and meet.

      Stop making HTML harder to validate and process, and start making browsers better conform--and developers more completely use--the many existing features in it and its underlying SGML or XML. That's Allstat^Wgame kid's stand.

      *"However, the HTML tag doesn't give any information about what that text string means—"Avatar" could refer to the a hugely successful 3D movie, or it could refer to a type of profile picture—and this can make it more difficult for search engines to intelligently display relevant content to a user."

      --
      You can hold down the "B" button for continuous firing.
    6. Re:Not to worry... by Anonymous Coward · · Score: 0

      A "Controversial Working Draft" is not a specification!

    7. Re:Not to worry... by shutdown+-p+now · · Score: 1

      Microdata is not part of the HTML5 specification. Right at the top of your linked document it says:

      Status: Controversial Working Draft. ISSUE-76 (Microdata/RDFa) blocks progress to Last Call

      and then if you click on the issue link, you see:

      There will be a forthcoming HTML5+RDFa proposal that may either be published along-side the Microdata specification or in place of the Microdata specification. RDFa is a alternate technology that is currently published as a Recommendation via the W3C . An additional alternative that is being proposed is the removal of Microdata and RDFa from the HTML5 specification and the placement of each section into a separate specification that is implemented on top of the HTML5 standard.

      In addition, the charter for the HTML WG mentions:

      "The HTML WG is encouraged to provide a mechanism to permit independently developed vocabularies such as Internationalization Tag Set (ITS), Ruby, and RDFa to be mixed into HTML documents. Whether this occurs through the extensibility mechanism of XML, whether it is also allowed in the classic HTML serialization, and whether it uses the DTD and Schema modularization techniques, is for the HTML WG to determine."

      The current microdata section precludes this Charter requirement.

    8. Re:Not to worry... by geminidomino · · Score: 2

      HTML 5 is a shining beacon of brilliance compared to some recent "standards" out there... Medica[re|id]'s "Meaningful Use" currently has me considering a lucrative career as an Amway salesman...

    9. Re:Not to worry... by aztracker1 · · Score: 1

      HTML5 itself started off with WhatWG documenting the "breaking" browser specific extensions to HTML by various browsers... XmlHttpRequest is based on a non-standard MS active-x control. All of HTML itself is a series of non-compliant extensions later ratified... at least this time there are three disparate third parties behind it. If google, ms and yahoo are for it, it's probably not a bad thing... besides they've already been using this metadata for a while. though I think meta-* attributes to counterpart data-* attributes may be better... I usually only need/use one data attribute (populated with json) when needed

      --
      Michael J. Ryan - tracker1.info
    10. Re:Not to worry... by grcumb · · Score: 1

      Ahhh Slashdot, where bashing Microsoft for no good reason is always a good way to get modded up.

      It's not that we have no reason to do so; it's that there are so many that we get tired of reciting them. 8^)

      This time, the development is newsworthy because we also get to beat up on Google and Yahoo! at the same time. The reasons may be found in the article, which, despite its angry, polemical tone, is pretty much on the money.

      Google, Microsoft et alia are basically saying, 'Speak my language on the web - win a prize!' That's all well and good, right up until you want to encapsulate your data in such a way that it expresses something they don't recognise, or don't support, or don't like. Obvious examples would be erotica and various alternative or subversive artistic media, political expression and fringe culture[*].

      RDFa is capable of performing exactly the same tasks as microdata, but it's open and extensible. This means that communities/cultures would be able to derive their own semantic ontologies using the same grammar and structure as the big guys, making it easier for groups big and small to make use of the data.

      ---------------
      [*] This potentially includes entire nations (such as the tiny South Pacific country I live in).

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    11. Re:Not to worry... by omfgnosis · · Score: 1

      Er, yes it is. You might not like it, but it specifies something. Albeit poorly in some areas.

    12. Re:Not to worry... by Anonymous Coward · · Score: 0

      That same issue states that it was closed in 2009. Microdata is listed as a working draft and, from my understanding, is the W3C's preferred method of encoding semantics into a web page.

      It's interesting that Google come up with this alternative when one of their own staff is the editor for the Microdata specification.

    13. Re:Not to worry... by shutdown+-p+now · · Score: 1

      It's interesting that Google come up with this alternative when one of their own staff is the editor for the Microdata specification.

      If you mean the subject of TFS, then it's not an alternative - it uses Microdata.

    14. Re:Not to worry... by vegiVamp · · Score: 1

      You can't provide citations on future events. You can only go on past behaviour.

      As the magic eight ball says: Outlook not so good.

      --
      What a depressingly stupid machine.
    15. Re:Not to worry... by GreatBunzinni · · Score: 1

      To be fair, whatwg's "HTML is a living standard" bullshit was the first successful attempt at breaking HTML, and is in essence the exact same thing that these companies are proposing. So, it appears that everyone is trying to break up HTML to their own benefit.

      --
      Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
    16. Re:Not to worry... by Anonymous Coward · · Score: 0

      FTFA: "Microdata is a set of tags, introduced with HTML5, that allows you to do this."

      It isn't breaking HTML, its part of the standard. However, this, and anything similar is a bad idea for search engines because it is something that ONLY spammers (aka, companies large enough to throw resources into making this happen) will effectively deploy it. The great thing about the internet is that any random Jane can throw information up, share it freely and then it sinks or floats on its own merit. (hyperbole, I know). SEO "experts" who game the search engines have already perverted the process enough, and this is deliberately putting another tool in their toolbox to keep the little guy out.

      If Google and MS are really backing this (which I doubt), it may be time to get into the search engine business, because this is going to make their results even worse.

    17. Re:Not to worry... by Anonymous Coward · · Score: 0

      Given that HTML5 is largely about giving control of the spec to MS & Google, the same issues apply.

    18. Re:Not to worry... by Anonymous Coward · · Score: 0

      MMM, good ol' MU. We just finished up our certification :)

    19. Re:Not to worry... by radtea · · Score: 1

      Stop making HTML harder to validate and process, and start making browsers better conform--and developers more completely use--the many existing features in it and its underlying SGML or XML.

      This has been the lament of markup nerds (I was one once, but I got better) since 1995, which tells us that it isn't going to happen. There has never been any incentive for companies to be validation-centric, because users aren't capable of creating validating code. Neither are tool-vendors.

      This has been the strength of HTML as a "standard": it's a consultant. You ask it to do something, it'll go ahead and do it, regardless of whether what you're asking for makes any sense.

      And because the consumers of HTML documents are humans who mostly aren't paying attention anyway, any processing that basically gets the text on the screen is adequate. So by being profoundly promiscuous and relaxed about standards compliance, HTML owns the Web, despite the (quite justifiable) howls of markup purists.

      --
      Blasphemy is a human right. Blasphemophobia kills.
    20. Re:Not to worry... by geminidomino · · Score: 1

      Congrats.

      I'm still trying to get my team through the twisty maze of requirements, all conflicting.

    21. Re:Not to worry... by olau · · Score: 1

      Sorry, been there, done that, didn't work.

    22. Re:Not to worry... by nagnamer · · Score: 1

      A "Controversial Working Draft" is not a specification!

      It's not a standard, but it is a spec.

      --
      Every harsh word you utter has the right address. It only sounds harsh because the one on the envelope is the wrong one.
  3. To get ahead, disregard this. by Anonymous Coward · · Score: 0

    Like always happens with standardization efforts, the only way to make your offering unique from the competitors' is to add custom functionality not found within said standard.

    1. Re:To get ahead, disregard this. by omfgnosis · · Score: 1

      The great thing about metadata is that it provides worlds of opportunity to differentiate featuresets while maintaining interoperability; that is, to offer your custom functionality beyond the scope of the standard, rather than contrary to it.

  4. Just Like HTML by Anonymous Coward · · Score: 0

    Maybe the W3C can come up with another form of HTML.

    They seem to enjoy coming up with poorly thought out half-standards that invite browser incompatability.

    They can top it off by excluding obviously necessary features, inviting companies to come up with various incompatible implementations of basic functionality, like flash movie and music players.

  5. not just Microsoft or Google or Yahoo. by John+Hasler · · Score: 2

    Right. You've got to include Facebook.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    1. Re:not just Microsoft or Google or Yahoo. by Anonymous Coward · · Score: 1

      Well both Yahoo and Facebook have large M$ influence$. So really this is Microsoft and pals plus Google. It was Google plus Apple but that kind of fell through.

  6. How is this different than the MetaData tag? by jader3rd · · Score: 5, Insightful

    One of the reasons why Google was able to tromp AltaVista was that AltaVista's search was based completley on the MetaData tag of the html page, and Google ignored the MetaData tag. The reason why? Website administrator were putting false information into the MetaData tag in hopes of generating more web crawler search hits. Google decided to go off of what was actually being presetned on the page, and we all found that to be more useful.

    1. Re:How is this different than the MetaData tag? by Ruke · · Score: 1

      I guess it remains to be seen whether content sites will actually implement this, or whether it'll just be another tool in the black-hat SEO bag. I can see how this may be useful on, say, Wikipedia, which is content-dense and could be rapidly renovated; however, I kind of get the feeling that Wikipedia doesn't really need the help getting to the top of Google's results list.

    2. Re:How is this different than the MetaData tag? by kevinmenzel · · Score: 3, Informative

      "More is better, except for hidden text" - I think this is the key difference between this and meta tags - the emphasis is on adding markup to text/content you provide to the user, in a way that makes it more quantifiable to search engines. Metatags weren't visable to the end user, and didn't particular concern specific content, but rather pages as a whole. I mean, that isn't to say that this system won't be scammed, but it does at least have a different focus of providing context for extant data, not additional data from which to help create a context.

    3. Re:How is this different than the MetaData tag? by icebraining · · Score: 2

      This isn't meant to replace the page's content, just to annotate it (point out the semantic structure). So that the page consumer can understand that "6/10" means a rating or that "John Smith" is a person's name.

    4. Re:How is this different than the MetaData tag? by RackNine · · Score: 1

      Agreed, Google also happily ignores meta keywords and of late even meta descriptions, focusing purely on the available content, so how is this going to be different is beyond me

      --
      We put you on the Internet map,
      www.racknine.com
    5. Re:How is this different than the MetaData tag? by icebraining · · Score: 1

      I don't know about this specific format, but for example e-commerce companies have been annotating their pages with semantic tags. Best Buy, for example, has annotated a huge amount of data with the Good Relations ontology.

      And I don't really see how could this be abused, except for the boost that Google gives to any semantically tagged pages - but that effect should wear off as most sites implement them too.

    6. Re:How is this different than the MetaData tag? by icebraining · · Score: 4, Informative

      Meta keywords and descriptions are used to replace content, which can be abused. This is used to annotate content, not replace it. It simply let's you say what the content is supposed to represent (a recipe, or a rating, or a person, etc).

    7. Re:How is this different than the MetaData tag? by itchythebear · · Score: 2

      Thats exactly what i was thinking. It just makes more sense that search results should be based off of what is actually on the page, not what the developer whats you to think is on the page. Another problem I have are things like this (taken from the documentation on schema.org)

      <time itemprop="startDate" datetime="2011-05-08T19:30">May 8, 7:30pm</time>

      Is that really necessary? Is it that hard to parse that string into a valid timestamp? The only reason I can think of would be if someone wanted to use some kinda of weird way to represent a date, and if thats the case then fooey on them for displaying a date in a way a human probably couldn't read anyways.

      do not want!

      --
      If what I just said sounded like a troll, it was probably just a failed attempt at humor.
    8. Re:How is this different than the MetaData tag? by Anonymous Coward · · Score: 0

      They give the explanation of the date thing right on the Getting Started page that introduces it: it's because date representations can be ambiguous. For example, if you saw "11/4/2011", could you definitively say whether it was Nov 4th or April 11th? Sure it's not hard for a machine to parse but it may hard to interpret.

      It's basically decoupling the date data itself (given in the rigidly-specified format) from the display of that date (given in whatever format the author fancies).

    9. Re:How is this different than the MetaData tag? by itchythebear · · Score: 1

      Yes, but thats exactly my point. A user of the site isn't going to be sure what that date is either, there are context clues elsewhere in the content. But then it's reasonable to assume that an algorithm could be written to find that same association.

      --
      If what I just said sounded like a troll, it was probably just a failed attempt at humor.
    10. Re:How is this different than the MetaData tag? by DerekLyons · · Score: 1

      Website administrator were putting false information into the MetaData tag in hopes of generating more web crawler search hits. Google decided to go off of what was actually being presetned on the page, and we all found that to be more useful.

      Yes, we found that to be more useful - until website administrators learned to put false information into what is actually being presented on the page.

    11. Re:How is this different than the MetaData tag? by Anonymous Coward · · Score: 0

      How would the search engine know the difference between the date the article was written and a date referred to in the article?
      Also, are these two dates the same:
      01/12/10
      12/01/10
      They could both be the 1st of dec 2010 or the 12th of jan, depending on the locale.
      What timezone is 7:30pm in too?
      Is whats displayed in the web servers locale, has it used the http request headers to find out the clients locale or has it stored a preference in a cookie/etc?
      Parsing human readable dates and times is fraught with errors.

    12. Re:How is this different than the MetaData tag? by aztracker1 · · Score: 1

      In Phoenix ... <time datetime="2011-05-18T02:00:00Z">Next Friday at 7PM</time>

      Might be a better example... also, it allows for a easier client-side reformatting in JS.

      --
      Michael J. Ryan - tracker1.info
    13. Re:How is this different than the MetaData tag? by Anonymous Coward · · Score: 0

      What I would like to see would be a way to differentiate between the publication date and a date talked about on the site (didn't read the schema.org docs so that may be in there).

    14. Re:How is this different than the MetaData tag? by Anonymous Coward · · Score: 0

      Same difference. Annotated text on hidden section of a page is no different to meta tags.

      And you can't have a semantic web when all the SEO "experts" will abuse it.

    15. Re:How is this different than the MetaData tag? by omfgnosis · · Score: 2

      Really? So, on a site like Slashdot, with a wide variety of locales represented, what would the algorithm do with "11/4/2011"? Would it surmise that, in the case of Slashdot, it may be m/d/y, it may be d/m/y, but it's probably just a bunch of nerds arguing and shouldn't be indexed at all? Metadata is made for having a standard way to describing loosely defined data; the example of an ambiguous date is such a great example because there are plenty of valid human-understandable date representations that will remain ambiguous in machine parsing, and ultimately deciding on one preferred representation is a bias, and ultimately a standard, and doesn't reflect the flexibility of data presentation that exists (and ought to exist). That is why it belongs in metadata.

    16. Re:How is this different than the MetaData tag? by Eivind · · Score: 1

      Yes it is, generally speaking, hard to parse strings into date and time.

      What date or time does "Tomorrow", "Next friday", "7/5/09", "6 o 'clock", or "directly after lunch" refer to ? Keep in mind that the document may not be current - and make sure to take into account different time-zones and different conventions for dates. (in particular, some odd countries like to print dates as M/D/Y where the least-significant part is in the *middle*)

      May 8, 7:30pm is better than average - but you're still left with the question of which year is meant, and 7:30pm in which timezone ?

    17. Re:How is this different than the MetaData tag? by obarthelemy · · Score: 1

      and most of the world outside the US uses 31/12/1990, which is fine until you get to 1/2/1992

      --
      The Cloud - because you don't care if your apps and data are up in the air.
    18. Re:How is this different than the MetaData tag? by Chatterton · · Score: 1


      <time itemprop="startDate" datetime="2011-05-08T19:30">May 8, 7:30pm</time>
      <time itemprop="startDate" datetime="2011-05-08T19:30">Mai 8, 19:30</time>
      <time itemprop="startDate" datetime="2011-05-08T19:30">Mei 8, 19:30</time>

      <time itemprop="startDate" datetime="2011-07-08T19:30">July 8, 7:30pm</time>
      <time itemprop="startDate" datetime="2011-07-08T19:30">Jul 8, 7:30pm</time>
      <time itemprop="startDate" datetime="2011-07-08T19:30">Juillet 8, 19:30</time>
      <time itemprop="startDate" datetime="2011-07-08T19:30">July 8, 19:30</time>

      Start to be fun to parse isn't it? And in some languages May is not written the same way if it is the 1st of May or the 2nd of May... Then welcome in parsing hell.

    19. Re:How is this different than the MetaData tag? by kbg · · Score: 1

      Are you serious? You do realize that people in different countries actually use different formats for dates?

    20. Re:How is this different than the MetaData tag? by dave420 · · Score: 1

      Nice try - Google's crawler detects whether text is hidden on a page, and doesn't index said content. You think they haven't thought of that?

    21. Re:How is this different than the MetaData tag? by TheRaven64 · · Score: 1

      It used to be very common for pages to have a few KB of point size 1, white-on-white text at the end, containing popular search terms. This didn't affect Google, because Google's algorithm placed more emphasis on the pages that linked to you than on the content of your page. The problem with this, is that it's also subject to gaming (lots of sites that do nothing but link to pages with popular search terms). Google had an early advantage because everyone was exploiting flaws in their competitors' algorithms that didn't apply to theirs.

      --
      I am TheRaven on Soylent News
    22. Re:How is this different than the MetaData tag? by Eivind · · Score: 1

      Yeah. Though arguably even 31/12/1990 is suboptimal, it -does- have the advantage of not having the least-significant-part in the *middle*, but it still, for example, sorts wrong regardless of if you sort numerically or alphabetically.

      Generally, the most significant part should be -first-

      1990-05-30 is superior for this reason, it sorts correctly both numerically and alphabetically, and follows the general convention we have of having the most significant part come FIRST.

      URLs suffer from the same problem, with the most significant part being in the middle of the URL. It would really be a lot more logical to have:

      http://org.slashdot/folder/file

    23. Re:How is this different than the MetaData tag? by PybusJ · · Score: 1

      Really. Do you have a reliable parser for common date formats that works in all languages and scripts? If so I'd be keen for a reference.

      Or is this a comment by someone with the typical ASCII-is-all-we-need view of the world?

    24. Re:How is this different than the MetaData tag? by WuphonsReach · · Score: 1

      I guess it remains to be seen whether content sites will actually implement this, or whether it'll just be another tool in the black-hat SEO bag. I can see how this may be useful on, say, Wikipedia, which is content-dense and could be rapidly renovated; however, I kind of get the feeling that Wikipedia doesn't really need the help getting to the top of Google's results list.

      The problem with the concept of a semantic lies at the feet of human nature.

      The people who would benefit the most are not those that are publishing the information. The publishers receive little, if any, gain by making their information available in such a manner. Many, if not most, people are lazy by nature which means they will only expend effort on what benefits them personally. And because these tags will generally not be visible to the end-user or the web designer's boss, there's no "in your face" way of telling whether or not the web team has done their job. "Out of sight, out of mind" will be the order of the day and making sure the tags are correct will end up on the bottom of the pile.

      On the flip side, the black-hat SEO operatives, phishers, and other black hats have a big incentive to mark-up their content in a fraudulent manner. Either to drive more traffic their way, to confuse the search engines, or to commit fraud in some other manner.

      About the only exception to the first issue is if applying semantic tags to your content results in increased sales by being listed when someone wants to buy something. And the temptation there will be to not play fair unless forced to (hidden transaction fees, hidden S&H fees, fake rebates to drive the listed price down, etc.).

      --
      Wolde you bothe eate your cake, and have your cake?
    25. Re:How is this different than the MetaData tag? by Chelloveck · · Score: 1

      Yes, it is that hard to parse a timestamp. People are inconsistent. You might see "7:00" (unadorned), "7:00a", "7:00 AM", "7AM", "07:00", and "7 o'clock" all in the same document. And dates are nearly impossible. When is 1/2/11? January 2nd or February 1st? 2011 or 1911?

      Of course, I don't think this proposal is going to make things any better. If the display data was generated directly from the metadata, maybe. But as soon as someone touches it by hand you're going to see the two get out of sync. I go back to change the time; it's been moved to 8:30pm. Now the human-readable version says 8:30 but the machine-readable version still says 19:30. Which is it, really?

      Don't think it'll happen? Ha! The majority of people just don't grok semantics. If it looks okay to them, then what's the problem? I've done a lot of format conversions, mostly converting HTML and Word docs to something an ebook reader can handle. Even people who should know how to apply styles to at least give semantic meaning to parts of documents don't bother. Why change to a header style when a normal paragraph with a large, bold font ends up looking the same? Why use a different style for a quoted paragraph when you can just adjust the font and indentation on a regular paragraph?

      The majority of people just aren't going to bother with semantic markup, even if they understand what it's for. Especially if it's more work. Gee, I have to specify here that Hannah Montana is a person, and here that Hannah Montana is a city? That's too much work. People will know what I mean by context.

      A noble goal, but one that's doomed to failure.

      --
      Chelloveck
      I give up on debugging. From now on, SIGSEGV is a feature.
    26. Re:How is this different than the MetaData tag? by SEE · · Score: 1

      When is 1/2/11? January 2nd or February 1st? 2011 or 1911?

      Silly. It's clearly February 11th, the year 1. Or 1901. Or 2001.

    27. Re:How is this different than the MetaData tag? by RackNine · · Score: 1

      Meta keywords and descriptions are used to replace content, which can be abused. This is used to annotate content, not replace it. It simply let's you say what the content is supposed to represent (a recipe, or a rating, or a person, etc).

      meta keywords and meta descriptions are not used to replace any type of content, they are (were) used to define what the content of a page is about. In that sense, this scheme is exactly the same thing, and if it's open to abuse, it will be abused. The conclusion is that we shouldn't even try to make websites designed for Search Engines and instead focus on real human visitors. As someone once told me, we shouldn't be engaging in any SEO at all, because it is Google's job to find and properly index that content, not ours. And they get handsomely rewarded for it.

      --
      We put you on the Internet map,
      www.racknine.com
    28. Re:How is this different than the MetaData tag? by Rizimar · · Score: 1

      Google also happily ignores meta keywords and of late even meta descriptions, focusing purely on the available content

      They only ignore meta descriptions if they feel that they aren't relevant to your page (e.g. if you use the same description for every page on your site or if it doesn't make sense in the context of what your site is about). Meta descriptions probably won't be disappearing from Google's usage in the near future because they can be helpful and are not used to rank pages.

      Basically, the new schema should help to clarify the data that search engines find on a site. It's incredibly difficult for machines to categorize pages and information based on text, especially when there are no predefined categories to really start from. This project will hopefully help to take the guesswork out of the more ambiguous pages and keep everyone's search results more relevant, regardless of information.

      This is different from the meta keywords tag because those tags were never really descriptive or focused to begin with. You could put anything you want in a meta keywords tag. With microdata, you have a set of datatypes which can be included to tell the search engines about some piece of information on the page.

      Even with just a few usages, the search engines should be able to infer that any subsequent appearances of the terms described in the microdata still have to do with that data (so Luke Skywalker shouldn't have to be redefined as the protagonist of Star Wars every time he's mentioned). I also wouldn't be surprised if search engines started to make global definitions based on some sites' usage of microdata (for instance, if Google finds microdata on Richard D. James and every instance of those microdata sets define him as being Aphex Twin, they might be likely to associate sites that don't even mention Aphex Twin with Richard D. James. But this is just speculation.

    29. Re:How is this different than the MetaData tag? by kevinmenzel · · Score: 1

      Sure, but if that became a problem then I'd imagine that a) It would show up to the user whenever Google, Bing or Yahoo presented a "RIch search result" from a page trying to game the system, and b) The search engines could look at the size of the text by analyzing the markup, and demote pages with a whole bunch of these tags surrounding really tiny text - bonus marks for detecting low contrast or unreadable text by analyzing the markup.

      There is also no suggestion that this markup will be the primary factor in ranking search results.

    30. Re:How is this different than the MetaData tag? by TheRaven64 · · Score: 1

      Sure, but if that became a problem then I'd imagine that a) It would show up to the user whenever Google, Bing or Yahoo presented a "RIch search result" from a page trying to game the system,

      Not if it isn't near the top of the page.

      and b) The search engines could look at the size of the text by analyzing the markup, and demote pages with a whole bunch of these tags surrounding really tiny text - bonus marks for detecting low contrast or unreadable text by analyzing the markup.

      Well, that was how it was done in the mid-'90s. These days, you'd put the text in a SEO div that you would then remove via JavaScript. For extra points, you could remove it in response to a mouse move event or similar, so that even if the search engine's crawler used a JavaScript engine it would still see the fake text.

      There is also no suggestion that this markup will be the primary factor in ranking search results.

      The problem with that, is that metadata is only useful if things make use of it. If search engines are going to use it, that makes it worth a lot of sites gaming it. If search engines aren't going to use it, that removes one of the biggest reasons to bother supporting it.

      --
      I am TheRaven on Soylent News
    31. Re:How is this different than the MetaData tag? by thetoadwarrior · · Score: 1

      Microdata format isn't meant to be meta data in the sense of html metadata tags. It's for marking names as a first name and a surname. It allows you to pull an address for example out of a site straight into your email client. I'm sure someone may try to abuse it for better search rankings but I don't think it would work that well.

    32. Re:How is this different than the MetaData tag? by thetoadwarrior · · Score: 1

      It's not meant for hidden data but to mark a name as a name. People have been using microdata (or microformats) for awhile. It's not really taken off because it needed to be standardised as it is now. If there was any benefit to abusing the format it has already existed. I don't see any real benefit in relation to SEO other than things like indexing addresses and names easier so search for a person may be easier.

    33. Re:How is this different than the MetaData tag? by Unequivocal · · Score: 1

      Let's not dredge up the bang path wars.

      And I'm not holding my breath for the world to switch to year first dates. US will go metric first.

    34. Re:How is this different than the MetaData tag? by icebraining · · Score: 1

      No, this does not define what the content of the page is about, so it's not the same thing.

      With the meta tags you could add your own text to describe the whole page. Obviously, this could be abused.
      With the new semantic schemas, you don't have anywhere to put your own text - they're predefined tags that you use to classify parts of the existing content (the one that is already used by search engines).

      The only thing you could do "wrong" is classify it wrongly, but that doesn't help you in any way, it'll just your page seem broken in the search results, if you have e.g. a poem classified as a recipe, or a post classified as a person's profile.

      Have you read the documentation? Can you provide any example of how can this be abused?

    35. Re:How is this different than the MetaData tag? by kevinmenzel · · Score: 1

      See, my guess is that it would help an already highly ranked result become more attractive because that highly ranked result would become a highly ranked RICH result, and therefore appear to be "special" somehow relative to the other results - so even if your page is ranked 3rd or 4th, if the result has more contextually helpful information presented to the searcher than the highly ranked page, it'll perhaps be more likely to get a click. So if you had a site that tried to game this system, because the content you are trying to game the system with would be presented to the user BEFORE they click through to your site, if you actually don't provide useful content to turn into a rich result, you won't get the click. I mean, it really depends on how the search engines actually implement both crawling and displaying this kind of data, but if they are using it to actually provide data to the user at the result page in some rich way, garbage data will be obvious. I agree that people will try to game the system, but gaming this will be DIFFERENT than gaming meta tags, even if only slightly.

  7. Hey... by Anonymous Coward · · Score: 0

    I'm actually ok with google deciding things. they have motives OTHER than profit sometimes. And generally do an ok job of things.

    microsoft on the other hand... hahahahahahahahahahaha.. they don't get to decide shit. we tried that before. they fuckup everything they touch.
    and yahoo? do they even exist anymore? why? are we supposed to still pretend that yahoo is relevant? They're not.

    1. Re:Hey... by DarwinSurvivor · · Score: 1

      I find it funny that yahoo even attended. They are no longer anything more than a front-end to byng with msn-style news (read: ignored) and an e-mail service that is quickly dying just as quickly.

    2. Re:Hey... by Raenex · · Score: 2

      I'm actually ok with google deciding things.

      I'm not. Don't trust any company any further than you can throw them. Google has already walked pretty far down the path of corporate evil.

    3. Re:Hey... by omfgnosis · · Score: 1

      Yahoo has been a pretty prominent contributor to developer tools for "web 2.0" and have probably had a great deal more impact than their market position would predict. That influence isn't going to vanish overnight.

    4. Re:Hey... by Anonymous Coward · · Score: 0

      So yahoo is to blame for this bloated web 2.0 buzzword shit that sprang up? Where simple damm text pages now take megs instead of a couple k?

      I hope yahoo dies a horrible violent death and everyone who works there ends up as soylent green.

      And even that's too nice.

    5. Re:Hey... by omfgnosis · · Score: 1

      So yahoo is to blame for this bloated web 2.0 buzzword shit that sprang up? Where simple damm text pages now take megs instead of a couple k?

      The tools can certainly be used that way, but don't dictate it. YUI is modular, so it can be pretty lightweight while still providing good library functionality over the standard DOM. That said, it probably isn't best suited for "text pages", and neither is most "web 2.0" type functionality. Blame the library collectors, not the library developers.

  8. And what does Mozilla think of this by Anonymous Coward · · Score: 1

    It really is of no use if the person browsing the site doesn't use it. Seems like browser developers should be an important part of this equation. Google = Chrome, MS = IE....so where does Mozilla stand?

    1. Re:And what does Mozilla think of this by icebraining · · Score: 2

      It really is of no use if the person browsing the site doesn't use it.

      Nope, it's useful even if you're browsing with IE6, since search engines and other aggregators can use it to improve their services. Try searching for something like "baked spagetthi recipe" on Google.

    2. Re:And what does Mozilla think of this by Anonymous Coward · · Score: 0

      Seems like browser developers should be an important part of this equation.

      While I'm sure browser makers have tons of talented and knowledgeable people when it comes to HTML, this topic isn't really in their court. Looking over some examples, it appears they're just doing a little more than what Microformats started. They're creating HTML elements without actually creating HTML elements by adding new element attributes to existing HTML elements. Depending on how you look at HTML you should be able to put any attribute on an element without breaking it. Unknown attributes should be ignored by browsers, but it can allow Search Engines to parse the page in a more knowledgeable way.

      You might run into W3C validation errors or warnings if you try to run their validator, but, like I said, that depends on how you really view HTML, if that matters or not.

    3. Re:And what does Mozilla think of this by Anonymous Coward · · Score: 0

      Firefox has their moments but right now they are 1) The fastest rendering browser on the market. 2) The most versatile browser, meaning it is available on just about all platforms you can think of. 3) For the most part when you develop for firefox it also works with chrome, opera, and in most cases safari. 4) It has amazing web developer tools unlike IE's dev tools or Chrome's. 5) It is currently the most secure browser.

      This does change from time to time and Firefox 3.x was a disaster. I will admit that pluginscontainer.exe is the worst part about firefox and most of the problems with the browser is java, just disable it (not to confuse it with javascript). I go from FF to Chrome back and forth and Opera is just a mess. IE doesn't like to make up its mind but like all other browsers I'm forced to use it as a seasoned web developer =/

      I won't ever give FF a bj, I'll leave that to the furry community.

    4. Re:And what does Mozilla think of this by Anonymous Coward · · Score: 0

      "its".

      If you're going to insult, please do it properly.

    5. Re:And what does Mozilla think of this by Anonymous Coward · · Score: 0

      1) The fastest rendering browser on the market.

      Only if you ignore Opera, Chrome, Safari, and IE 9.

      2) The most versatile browser, meaning it is available on just about all platforms you can think of.

      Only if you ignore Opera.

      3) For the most part when you develop for firefox it also works with chrome, opera, and in most cases safari.

      This also happens if you initially develop for one of Chrome, Safari, or Opera.

      4) It has amazing web developer tools unlike IE's dev tools or Chrome's.

      Have you ever used the built-in developer tools of Chrome and Safari? Unlike Firebug, they don't lock up the browser, they aren't horribly slow, and they offer much more useful functionality.

      5) It is currently the most secure browser.

      Only if you ignore Chrome, Opera and Safari.

    6. Re:And what does Mozilla think of this by Oligonicella · · Score: 1

      Don't get your point. I just got hundreds of baked spaghetti recipes.

    7. Re:And what does Mozilla think of this by Anonymous Coward · · Score: 0

      It really has nothing to do with the browser. Browsers ignore atributes in a HTML tag they don't understand. It is really just between the web developer and the search engine.

    8. Re:And what does Mozilla think of this by Anonymous Coward · · Score: 0

      To quote the GP, your comment is "so 200[8]." It completely ignores the last 2.5 years in non-FF browser advancements. "More secure" was LOL-worthy; even IE8/9 is inherently safer nowadays (ignoring plugins and non-Windows platforms).

    9. Re:And what does Mozilla think of this by icebraining · · Score: 1

      How do you think Google could show you those stars with the ratings, the number of calories, the time the recipe takes, etc? The pages are tagged with the hRecipe and hReview microformats.

      Sure, it's not a life changing effect, but it was just an example, there will be many others.

  9. Well.. by Smirker · · Score: 1

    I, for one, welcome our new mark-up vocabulary overlords.

    1. Re:Well.. by omfgnosis · · Score: 2

      I viewed the source:

      <div about="urn:ISBN:0967686563">I, for <span content="viagra">one</span>, welcome <span resource="http://www.goatse.bz/">our</span> new mark-up vocabulary overlords.</div>

  10. We managed to get 3 large corporations to agree? by Anonymous Coward · · Score: 0

    Microsoft or Google or Yahoo oh my!

  11. Dammit by Sloppy · · Score: 5, Interesting

    I am a whore and have to do whatever the big guys say, because I want their traffic. Ok, so I admit it.

    But dammit, did it have to be microdata? I already mark up with microformat classes and RDFa (both the sortof standardized namespaces and Google's) and Google was handling it pretty well, and every once in a while it looked like Yahoo grokked it too. Microdata was the ugly stepchild third choice, the least well-supported one, with the fewest number of parsers out there in the wild.. So I left that one out, because nobody cared. Now it's going to be The One?

    I have better things to do than add Yet Another fucking attribute to my generated HTML which is already bloated with otherwise unnecessary classes and properties and typeofs. Now I'm going to have itemscope and itemtype attributes too, huh? Just how many characters long can we make each element become, just so that everything can make sense of it? Fuck you guys. No seriously, fuck you. Yes, I'm going to do it anyway, but even so, fuck you.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    1. Re:Dammit by icebraining · · Score: 1

      I was really expecting for RDFa to win the competition, it had already a decent user base and it's much more flexible and useful.

    2. Re:Dammit by dakameleon · · Score: 1

      That there is what you call a "compromise candidate" - the one everyone objects to the least. Surprising though that Google, Microsoft & Yahoo got together on something like this outside the context of an industry group like W3C.

      As to your better things to do, go ahead and do them - I assume you're a working web developer, so this really can be viewed as a revenue-generating opportunity. Think of it as a chance to tack an extra "SEO structuring" charge on top. If you're not doing them, I know I will!

      --
      Man who leaps off cliff jumps to conclusion.
    3. Re:Dammit by johncandale · · Score: 1

      Do you really have better things to do?

    4. Re:Dammit by Sloppy · · Score: 1

      Ouch! Damn, that's cold.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    5. Re:Dammit by Kernel+Krumpit · · Score: 1

      Fuck you guys. No seriously, fuck you. Yes, I'm going to do it anyway, but even so, fuck you.

      That's the correct attitude - except for the "i'm going to do it anyway" part!

      1).. Why on earth would you work on putting anyone else's but your own webpages at the top of serps?
      2).. Fuck the suits and ties. Fuck 'em!
      3).. If you can do it for a playcheque then you can do it better for yourself. Have courage!
      4).. DON'T give the big search engine boy's what they want - they'll screw you over next year.
      5).. take the long term approach. As an example search for "best selling laptops 2011" and tell me who i am.

      Fuck Google, Fuck Bing. We have the power - Use IT!

      --
      May the lies we live by make us strong, healthy, happy and wise - Kurt Vonnegut.
    6. Re:Dammit by msclrhd · · Score: 1

      I'm ignoring everything except RDFa on my site. I took the decision of dropping the HTML5 markup for HTML+RDFa and getting the pages validating properly (still using CSS3, though).

      It would be great if Google had support for DOAP (Definition of a Project) for open source projects and read that through RDFa.

    7. Re:Dammit by c0lo · · Score: 1

      Fuck Google, Fuck Bing. We have the power - Use IT!

      The same type of power as the Brownian motion. And THEY are using it by having the appropriate containment cylinders and pistons to guide this motion - of course, in their interest.

      --
      Questions raise, answers kill. Raise questions to stay alive.
    8. Re:Dammit by omfgnosis · · Score: 1

      Even masturbating furiously over the standard we wish was adopted is a better thing to do than implement the standard we wish wasn't adopted.

    9. Re:Dammit by mhermans · · Score: 1

      I feel the same way. RDFa is the only standard and is the one seeing measurable adoption, with big names as Best Buy and the IPTC (Reuters, AP, AFP, etc.) recently announcing their adoption. Heck, even Google and Yahoo were already supporting RDFa for ecommerce through GoodRelations. This decision does seem more driven by politics then technical reasons. If it would be a truly innovative step, I'm more sympathetic to following actors instead/until a standard has been written, but in this case I seems a somewhat conscious effort to avoid a perfectly good W3C-standard...

    10. Re:Dammit by Anonymous Coward · · Score: 0

      Well of course that's often the case when big players come together and have to compromise. Company A says "I want RDFa, but my second vote is Microdata" (knowing that Microformat would give a head start to Company B who already prefer it). Company B says "I want Microformat, but my second vote is Microdata" (knowing that RDFa would give a head start to Company A who already prefer it). The votes are counted: RDFa 1, Microformat 1, Microdata 2. Welcome to compromise, where average is the new excellent.

    11. Re:Dammit by Unequivocal · · Score: 1

      Good comments - thanks. You sound like someone who could help me: what's the difference between microformats and microdata? I thought the two were synonymous until this recent announcement and now lots of people are talking about them as if they are different. I've been googling but the conversation still seems pretty confused. What I think I make out is that microdata is a specific implementation of using microformats, designed to handle many use-cases that RDFa handles for the web?

      Any help would be appreciated..

    12. Re:Dammit by Anonymous Coward · · Score: 0

      You gave up already? The race has just begun, let's see how it pans out.

    13. Re:Dammit by Sloppy · · Score: 1

      Microformats don't extend HTML or add any new attributes. With a few minor exceptions, all microformats do is say that your class names are not merely abstract symbols -- that the actual character strings that you use, convey meaning. Prior to just a few years ago, a browser or spider sees <span class="foo"> and <span class="review" > as being the same thing, because "foo" and "review" are just names. It's just like how it doesn't matter whether you name a variable i or x in a computer program (shut up, Fortran IV programmers, I'm not talking to you).

      Of course, when a human rather than a computer is reading things, suddenly class names (and variable names) do matter. Microformats come along and say let's let computers also infer meaning from the attribute values that we use.

      The advantage of this, is that you don't have to learn anything fancy; your 1990s HTML knowledge (and tools, maybe) is still all you need. And it's very simple.

      The disadvantage is that some things and relationships are hard to express by merely naming them. So RDFa and microdata came along and actually added some new attributes that HTML guys might not normally be very familiar with, and some rules for how to structure things. Microdata is more expressive than microformats, but also a little more complicated.

      My bitch isn't that microdata is stupid; it's that it doesn't really solve anything that RDFa didn't already solve just as well, and RDFa is already very widely deployed. Changing from microformats to microdata or RDFa isn't necessarily gratuitous (though in many cases it could be), but changing from RDFa to microdata (or vice-versa, I'll admit) is. This is purely wasteful, offering nothing. Thus, I hate.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    14. Re:Dammit by Unequivocal · · Score: 1

      Thanks - very helpful. If I can impose further, why do you think Goog/MSFT/Yhoo did this then? Seems like a total slap in the face to W3C and their RDFa working group - and presumably they did this in total secret without involving W3C or any public standards body at all.. What's the motivation/advantage for them to do this? (I can guess that once deciding to do it they did it in secret so as to not get shouted down half way through).

      I know a lot of people complain that RDFa is "too complicated" and I'll admit that when I've tried to read the docs I get confused b/c of lack of practical examples that I can just "monkey-see/monkey-do" with -- (at least last time I checked their docs). But could that be an actual reason for three giant corps to go their own way? Any thoughts on that or what else is driving this?

  12. Apple does it their way again by Anonymous Coward · · Score: 0

    So why's Apple not part of this?
    Bet they decided to go their own way, play solo as usual...

    The bad Apples get kicked out of the barrel anyway! (LOL Haha!! I can't believe I came up with this!)

    1. Re:Apple does it their way again by dakameleon · · Score: 2

      Because they're not a search engine?

      --
      Man who leaps off cliff jumps to conclusion.
    2. Re:Apple does it their way again by SanityInAnarchy · · Score: 1

      Since when is Apple a search engine?

      --
      Don't thank God, thank a doctor!
    3. Re:Apple does it their way again by Osgeld · · Score: 1

      Apple does not need a search engine, all information is pre approved for your consumption =)

    4. Re:Apple does it their way again by omfgnosis · · Score: 1

      Apple is heavily invested in metadata, is a browser vendor, and is almost comically reputed for their interfaces which marry power and ease-of-use. They *heavily* influence web standards. They have weight to throw around here.

    5. Re:Apple does it their way again by dave420 · · Score: 1

      Metadata like this is not intended for browsers. It's intended for webmasters to indicate to search engines what exactly is in their pages. Sure, you could write a plugin for a browser which used this data for some purpose, but the real purpose is improved indexing by search engines. And Apple doesn't have a search engine. Being "invested in metadata" is such a vague, pointless claim. Who the fuck cares? This metadata in particular is describing websites to search engines. Apple is entirely not invested in that, short of the markup on their own sites, which makes them a user just as much as anyone else with a website.

    6. Re:Apple does it their way again by SanityInAnarchy · · Score: 1

      To be entirely fair, it actually does make a lot of sense for browsers to consume stuff like this -- microformats would've been my first choice, but whatever. Consider: Right now, browsers can and do support discovering RSS feeds related to the current page. There's also a spec somewhere for a "universal edit button". Other things that might be relevant are hcalendar and hcard -- sure, search engines could consume these, but it'd also be cool to have my browser discover these things and communicate with my calendar or contact list.

      But I don't know of any browsers actually doing this, other than the RSS bit, without third-party extensions -- and this, in particular, was all about search engines, whether or not the standards involved would be relevant to browsers.

      --
      Don't thank God, thank a doctor!
    7. Re:Apple does it their way again by omfgnosis · · Score: 1

      Metadata like this is not intended for browsers. It's intended for webmasters to indicate to search engines what exactly is in their pages.

      Why the heck not? What law of nature determines that a "search engine" (whatever that is) is permitted to build powerful data-driven services, but that a "browser" (whatever that is) is not? RDFa specifies, in its abstract: "When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported into a user's desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo's creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing." Microdata uses, throughout its specification, the term "user agent", the same term the rest of the HTML specification uses to refer to browser et al.

      Sure, you could write a plugin for a browser which used this data for some purpose

      Or, you know, a browser which does so directly. Why not? Taking one of the examples from the RDFa abstract, I would imagine Apple has great interest in providing in-browser capabilities to interact between calendar web applications and iCal. This kind of metadata allows just that; why is it not the "real purpose"?

      Being "invested in metadata" is such a vague, pointless claim. Who the fuck cares?

      Let me clarify then: a huge, enormous part of their business model is driven by software and integration systems which leverage metadata. Their investment in the web is sure to reflect that.

      This metadata in particular is describing websites to search engines.

      Quite plainly it's not. It's describing structured data to machines.

  13. Not so remarkable.. by QuasiSteve · · Score: 4, Interesting

    The really remarkable part, though, is that they're making any progress at all with HTML5, so some kudos is in order.

    Not really all that remarkable. The main progress comes from the whole WhatWG efforts which in turn is basically the major browser makers saying "Screw you moving-like-molasses people and your incompatible XHTML 2.0, we'll just do things the way we agree to do them and everybody else can follow along or stay behind."

    Same story here, except now it's not the major browser makers, but the major search engine companies - who want to be able to more easily index information. Why wait for what webmasters and users want, when your search engine(s) pretty much control the market and the webmaster really has little choice but to either follow along or stay behind?

    This isn't necessarily a bad thing, as long as they all get along and the things introduced aren't wonderful in principle but a nightmare in practice (frames, anyone?)

    Note that the system used is very much in line with HTML5 veering well away from the XHTML 2.0 changes, in that rather than introducing new elements that a browser or other parser could easily choke on, it introduces new properties which are easily ignored.

  14. Be careful with Microsoft by bogaboga · · Score: 1

    I say 'be careful with Microsoft' because if my memory serves me well, Microsoft had some agreement with now defunct SUN Microsystems over Java and its use...that was until SUN realized that Microsoft had a hidden agenda.

    Nothing will prevent Microsoft from attempting to pull off what I will call a 'SUN moment.'

    1. Re:Be careful with Microsoft by Anonymous Coward · · Score: 1

      Nothing will prevent Microsoft from attempting to pull off what I will call a 'SUN moment.'

      Nothing... really...??? The fact that Microsoft has already been indicted for this behavior and is pretty much still on probation is a pretty good incentive. Oh, lets also not forget that it is Google with the monopoly on internet searches. Microsoft is not in the power position that it had with Sun.

  15. It'll work by Anonymous Coward · · Score: 0

    I'm sure the W3C format was useful in every way except the one that counted.

    If Google, Yahoo, and MS can agree on a format, it means it was a moneymaker.

  16. Wow this is just bad by Anonymous Coward · · Score: 0

    First and foremost, the problem with any such standard is its limited scope and dated features. For example, a breadcrumb may not be around in 1 year or 3 years because its use is not longer desirable or needed or better more efficient navigation models are created. So the spec, by default (just like HTML 5) is technically obsolete before it is ever even ratified.

    Second, holy micro management batman. Sure it will help search engines in theory. In reality I can use it to mold search results to an even greater degree. It just makes the nonsense that already is SEO even worse. Reviews get higher weight (as an example), so my blog now becomes full of "reviews" though they are really just rants. Or "offers" or anything else I can claim my content to be. Plus inlining the schemas is just plain annoying. And will any of this pass markup validation? To me this is just lazy by the search engines. Their results have been getting worse because they rely too much on social BS. Now you are going to rely on me telling you the truth? Fat chance of that if I can game the system for higher rankings. It is as bad as relying on what people voted to provide relevant results. It will not change the fact that searching for terms will have a blog that links to a blog that links to a blog that links to facebook that links to twitter that links to the actual article. But hey, that is not important right, let's add annotations and long more useless markup. Yay progress.

    Maybe just maybe if we killed HTML dead like it truly deserves and create a useful markup language from the ground up we can get useful results. Maybe if you allow and account for unique features on a browser by browser basis and have graceful degradation built into the browsers themselves. But you know that will never happen. So let's add more markup, semantics, annotations, and why not bibliographies?

    1. Re:Wow this is just bad by MightyMartian · · Score: 1

      Creating new versions of HTML has increasingly become the proverbial lipstick on the proverbial pig. But now they've made browsers into application platform and all the horrors and inadequacies are being magnified.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
  17. they didnt say OR by Anonymous Coward · · Score: 0

    Microsoft AND Google AND Yahoo.

  18. It's a Trap! by VortexCortex · · Score: 1
    FTTOS:

    Terms of service

    This is a contract between you and each of the sponsors of Schema.org: Google, Inc., Yahoo, Inc., and Microsoft Corporation (referred to collectively in this agreement as the "Sponsors", "we" or "us"). By using the Schema.org website (the "Website") you agree to be bound by the following terms and conditions (the "Terms of Service").

    Changes in Website and Terms and Conditions; Change in Schema

    We may modify or terminate the Website, for any reason, and without notice. We also reserve the right to modify these Terms of Service from time to time without notice, and you expressly agree to be bound by such modifications when posted on the Website.

    This legalese basically says: By using the schema.org website, (esp. their schemas) you agree to whatever we want forever. THE END.

    Even Facebook's horrid TOS agreement is better for you than this, at least you can terminate Facebook's agreement.

    I for one rebel against our Gigantic Corporate Lawyer-wielding privacy-and-competition-hating overlords. If I can't get past the TOS page, I'll just stick to RDFa. Just added "0.0.0.0 schema.org" to my hosts file just in case I get link-baited into agreeing to that evil evil evil TOS.

    1. Re:It's a Trap! by Anonymous Coward · · Score: 0

      You got so outraged that you apparently missed the next sentence: Notwithstanding the foregoing, the Sponsors agree that no change that we make to these Terms of Service will terminate or modify the license granted under paragraph 1 above with respect to any use or implementation of the Schema occurring prior to the date that the change is published.

    2. Re:It's a Trap! by Raenex · · Score: 4, Interesting

      You're right, it is a trap, but it gets worse:

      The short summary: The "Sponsors" (read: cartel) may have patents on this crap. You can, for now, use the crap royalty free for markup only if you follow the standard. Non-cartel search engines are not granted such rights. In addition, future versions may not be royalty free. Your existing markup is safe, but any new versions or pages won't be.

      The actual fine print:

      In addition, if the Sponsors have patent claims that are necessarily infringed by including markup of structured data in a webpage, where the markup is based on and strictly complies with the Schema, they grant an option to receive a license under reasonable and non-discriminatory terms without royalty, solely for the purpose of including markup of structured data in a webpage, where the markup is based on and strictly complies with the Schema. [..] Notwithstanding the foregoing, the Sponsors agree that no change that we make to these Terms of Service will terminate or modify the license granted under paragraph 1 above with respect to any use or implementation of the Schema occurring prior to the date that the change is published.

    3. Re:It's a Trap! by Anonymous Coward · · Score: 0

      Far too many terms of services require you to give up a limb and your first-born child for this to mean much. Common examples are the "no suing us, whatsoever!" and "we get all your future work" licenses. Sure, there have been a few cases where the latter has been enforced against the best interests of a site's users, but when it comes down in the end, for every thousand times you see a vague, overly-broad disclaimer, it's just meant to prevent ambiguities when litigating.

      And of course, consider that Microsoft, Google, and Yahoo to an extent are still competitors. They're not going to go cartel on all new search engines, and notice the "if" at the beginning of the clause.

      Less of the Chicken Little sky is falling, please!

    4. Re:It's a Trap! by VortexCortex · · Score: 1

      You got so outraged that you apparently missed the next sentence: Notwithstanding the foregoing, the Sponsors agree that no change that we make to these Terms of Service will terminate or modify the license granted under paragraph 1 above with respect to any use or implementation of the Schema occurring prior to the date that the change is published.

      No, I understood it perfectly to make no sense. Here, big words are used to confuse you... Let me translate: notwithstanding: in spite of. Irregardless
      foregoing: What we said prior to this point.
      paragraph 1: The first paragraph "This is a contract ... you agree to be bound [by the TOS]."

      Irregardless of [Us granting you CC copyright license, and possibly terminating your right to use the schema if we don't agree on a patent license (that we are allowed to assert and charge for) ] we agree that no future changes will nullify any of the rights granted to you in [ the contract between us that you currently agree to ] so long as your use or implementation happened before the changes we plan to make. Also, this means our future changes can screw you over if you keep using our schemas, but don't agree with our license or agree to pay/comply with our patent royalties.

      In short: You must agree to everything forever, and we reserve the right to sue you over patents even though we slapped a big happy "Copy Left" license on the deal to make dolts like you feel warm and fuzzy.

    5. Re:It's a Trap! by Raenex · · Score: 1

      Far too many terms of services require you to give up a limb and your first-born child for this to mean much.

      Oh, because other terms are abusive, we should just ignore this one? The only way things are going to be less abusive is when people refuse what is being offered because of them.

      And of course, consider that Microsoft, Google, and Yahoo to an extent are still competitors. They're not going to go cartel on all new search engines, and notice the "if" at the beginning of the clause.

      Even if they are competitors, they would happily lock out any new competitors. The fact that they have granted themselves this patent capability, and given all the abusive patent bullshit we've seen recently, there's no reason to trust them. They could easily just have given everybody a royalty free license on any patents related to this spec. If you let the lawyers and executives be corporate assholes, that's what they'll be.

      Less of the Chicken Little sky is falling, please!

      Less bending over, please.

    6. Re:It's a Trap! by Anonymous Coward · · Score: 0

      So now we can move from an unencumbered markup language - html, to an encumbered markup which is patented and owned by 3 of the largest IT companies.
      The whole concept of needing a TOS and license to use a markup whose aim is to make Google et al's lives easier, increase their advertising revenue and enhance shareholder value is anathema.

  19. Finally... by georgeMandis · · Score: 1

    At least now we'll have a consistent way of marking up dry cleaning and volcanoes.

  20. "webmasters" ? by Anonymous Coward · · Score: 0

    Is this term actually still being used?

  21. microsoft by patrickluwi · · Score: 0

    i'm sure microsoft will do! KVM Switch

  22. $ from Microsoft or Google or Yahoo. by Anonymous Coward · · Score: 0

    I wish that I had bought the domain name :/

  23. Better yet it's based on HTML5 by pavon · · Score: 1

    A big part of his complaint is that RDFa scales better than Microdata which is what Schema.org uses, so both should be supported. Microdata is part of HTML5, and is an extension of Microforms, created exactly because RDFa is considered too complex.

    This is exactly a case of WhatWG producing workable standards and W3C creating design by committee monstrosities.

  24. The entire Web community should decide? by Memroid · · Score: 1

    Brilliant idea, then quality decisions will be made, just like in our political system.

    1. Re:The entire Web community should decide? by Xest · · Score: 1

      To be fair I'd imagine he really just meant the W3C members.

      This makes sense because the membership is wide and varied representing pretty much every industry with an interest in the web and some consumer organisations too.

      I sympathise with his view, HTML5 was put together by a handful of vested interests- Apple, Google, Mozilla and frankly they've done a shite job. HTML5 has been put together in an atrocious way that can be made to work on the desktop (and phones, but they're just like desktop browsers now anyway) but isn't well designed for other applications and devices that may wish to interact the web, nor is it good for developers of large web systems that require a high degree of maintainability and so forth.

      The W3C was criticised for being slow, but it was slow for a reason- it made sure all relevant voices were heard and worked to resolve that before coming to a decision. In contrast WHATWG with HTML5 and now the companies mentioned in TFA for this have basically said "Look, what we say goes, you can give us your input but we really don't give a fuck and wont actually listen- it's our way or the highway". So whilst standards like the XHTML standards took a long time to come about at least they were fairly resilient to future change- HTML5 in contrast has some sections which are largely obsolete before the spec even went release candidate. I suspect this will be the same- an ever changing nightmare spec that will be impossible to continuously adhere to and which will break things for developers and end users alike.

      "Done properly" isn't really a principle of the PHP generation.

  25. Why? by pankajmay · · Score: 1

    Can someone explain to me why there is a need for a separate metadata vocabulary?
    Wasn't this the issue that XML, XSD, XSLT and XSLT-FO supposed to address? Document verbiage aside, don't these families adequately cover the issue of structure, and semantics?
    If the issue is to teach the browser/search engine, the document semantics -- can't they (MS,Yahoo,Google) actually parse XML for common dictionary words and build semantics themselves? Why make humans do all the tedious annotations? They can probably publish standard XSD for people to structure XMLs... no?

    1. Re:Why? by Homburg · · Score: 1

      XML, XSD, XSLT and XSLT-FO

      Which of those have anything to do with semantics?

    2. Re:Why? by pankajmay · · Score: 1

      XML, XSD, XSLT and XSLT-FO

      Which of those have anything to do with semantics?

      True, more to do with structure than semantics, but usually semantics can be derived from structure, if the structure is meaningful.

      For example: <Thing> <Place> <Volcano></Volcano></Place></Thing> . . .


      A meaningful structure in XML can itself lead to semantics. XSLT, XSL-FO can then just transform it to whatever flavor.

      What I am trying to understand here is that -- why do we have to micro-annotate everything? Can't search engines/browsers do lookup of commonly found words and figure out context on their own with their AI algorithms. Web designers can provide a little nudge or help where its needed to parse difficult structure.

      Leaving every semantic detail open to coding will further exacerbate the problem of verbosity, not to mention obfuscation for the human in order to enable it to be parsed by the machines. Shouldn't machines/algorithms do the heavy work here than the web designers?

    3. Re:Why? by Homburg · · Score: 1

      I don't think this is about web designers hand coding all these details - I mean, who manually writes HTML these days? The HTML is going to be written by the CMS running the site, and the CMS will usually know this kind of information already - currently, this information gets lost and then has to be guessed by search engines. Why not let the software that runs websites communicate more directly with the software that searches them?

    4. Re:Why? by Anonymous Coward · · Score: 0

      Because publishing XSD and applying that schema to billions and billions of XML files across the web would have unforeseeable side-effcts that would more than likely be disastrous for a search provider. The point of these vocabularies is to make sure we're all talking about the same thing. If someone has an XML node called "page" that represents a page on their website, and someone else has an XML node called "page" that represents a page in a book, how do you distinguish between the two? Yes, you have to annotate it according to the community's (MS, Yahoo, Google) schematics, but I'd rather annotate my output and maintain my own domain specific vocabulary than bend my domain vocabulary to fit theirs.

  26. volume is the only standard by Anonymous Coward · · Score: 0

    no matter what standards group or collection of companies agree on any given standard. volume wins in the end.

  27. Fascist by Anonymous Coward · · Score: 0

    sounds like a Fascist to me

  28. I get sex if I clean the dishes by wdhowellsr · · Score: 1

    I hate to say this but when you have Bing, Google, and Yahoo saying that if I clean the dishes, use microdata, I can get laid in a search engine sense, I'm sorry the dishes will be cleaned. I don't know if this is live but let's be honest, they have us by our proverbial search engine balls. The days of free and fair elections, I mean fair SEO are as dead as Rep. Weiner's political career. Do you realize that he never had sex with any of those women. I'm not sure about you but if I'm going to ruin my career and my marriage, I'm going to at the very least factor the equation, define PI until I pass out, prove that (a)ss + (b)reasts = c

    Couldn't get the superscripts to work.

    1. Re:I get sex if I clean the dishes by wdhowellsr · · Score: 1

      My wife said I couldn't use the c work.

    2. Re:I get sex if I clean the dishes by wdhowellsr · · Score: 1

      This is why I shouldn't post at 12:43 am. My wife said I couldn't us the c word. Although I think it is fair to say the c word does require a good deal of work.

    3. Re:I get sex if I clean the dishes by Anonymous Coward · · Score: 0

      Pff, clearly you need to show this to your wife (courtesy of The Oatmeal): The Terrible C-Word =)

    4. Re:I get sex if I clean the dishes by Anonymous Coward · · Score: 0

      ... said I couldn't us the c word. ...

      So... 12:44 am doesn't seem to be a much better time for you?

    5. Re:I get sex if I clean the dishes by Anonymous Coward · · Score: 0

      cupcakes?

    6. Re:I get sex if I clean the dishes by Anonymous Coward · · Score: 0

      DUDE... what did I just read? Did I just get laid?

    7. Re:I get sex if I clean the dishes by Anonymous Coward · · Score: 0

      ass + beasts = speed of light?

  29. No cigar, the answer you're looking for was... by jim_kaiser · · Score: 2
    Semantic Web....

    I hope the companies would just put their efforts in creating a semantic web, instead of trying to hack-patch html by adding random meta-data for the purpose of search. Seriously.. focus people!

    Focus!

    --
    The last person to mod me down is a rotten egg..... there.. that should do it..
  30. What happens when... by biodata · · Score: 1

    ...they change the schema? I can't see any version numbers in the tags so how do the search engines know which version of the schema you mean, or will they continue supporting every version of every schema forever? Or will we all have to edit all our webpages in vi every time they bring out a new schema version to keep all our tags up to date?

    --
    Korma: Good
  31. The analogy here... by voss · · Score: 1

    Is if amazon, walmart and ebay decided to come up with a common tagging system for shopping searches.

    This does not change how web page are displayed only how they are tagged for search engines.
    Having the top 3 search engines in the world come to a common agreement is not a bad thing.
    These three search engines have represented 95%+ of the search engine market for the last 5 years.

    When 95% of the market decides on a common standard that is THE standard regardless of any hand waving
    by the "de jure" standards body

    1. Re:The analogy here... by Unequivocal · · Score: 1

      Hear hear. I don't have to like it but I'm going to have to live with it. And if FB hops onto this bandwagon, it's totally finito.

  32. Admission of massive FAIL by Anonymous Coward · · Score: 0

    This is a blatant admission of the failure to indexing content. Reliance on the honest representation of the content by providers is doomed.

  33. Dear W3C, by Ant+P. · · Score: 1

    You are not the "entire web community". You seem to have not realised this last time, when everyone implemented the WHATWG's HTML standard instead of your XHTML 2.0 pet project. Please get relevant or get bent.

  34. Taking positive spin on this by ajainy · · Score: 1

    I just spent few mins looking at schema.org and their proposed schema. The way, I look at it, they are just extending existing HTML tags (in spirit of, everything is XML eventually), so that they can extract meaningful information from HTML tag. Of course, it will help their spiders and search processors, but in end, it will help average web user, who will get exact results.

    Take a example of typical e-commerce site. These days, those sites have jump through hoops on "regular" basis, to provide product feed to google/bing/yahoo or any shopping comparison site. And almost everyone wants to do it, to get more page hits, more visibility. Now, if under plan of schema.org proposed extensions, spiders can parse their actual html pages and index product information, along with "latest" price. Hence no need to feeds and consumer always see prices on google products, as it is actually on retailer website.

    This same concept can be applied on different scenarios like emergency updates, latest news as it happens, any kind of status updates.
    Google has already starting showing flight times on their search. (i guess, largely due to fact, they got ITA) but using schema.org, they can show more relevant information for other text.

    Theoretically, companies like google or any other one, can build whole new genre of webapps.

  35. Adding meaning to HTML is almost exactly backward by TheLoneGundam · · Score: 1

    HTML and CSS are used as a presentation markup language. Adding "meaning" to those is approaching it backward. First, mark up the document / data, using XML or RDF (for this argument the preference doesn't necessarily matter). Then, use XSLT to provide a transform into the presentation language of your choice. I guess we could argue that XHTML _is_ XML at its core, though, so adding attributes to add "meaning" might be doing what I said, anyway. As far as 'why are the big companies agreeing to this, why isn't everyone consulted?' argument - hey, at least we're making progress. If one large group of pages is marked up in a standard way, then that's a lot of "meaning" that can suddenly be extracted and used in our apps / widgets / mashups / things-to-be-named-later-when-someone-thinks-them-up. In that sense, I'm all for it; let's get started! There's also a mechanical precedent for this: think back to when the auto industry in the US decided to standardize the "markup" of wheels with a 5-bolt lug nut pattern, spaced the same way - suddenly wheels were interchangeable, and making special chromed add-ons for people was economically more feasible too. They didn't consult a body of international automobile enthusiasts - Ford, GM, and Chrysler pretty much drove that one.

  36. Embrace and Extend by Anonymous Coward · · Score: 0

    Perhaps the entire community should embrace and extend the schema ;-) Would look good on M$

    1. Re:Embrace and Extend by HiThere · · Score: 1

      Except that they appear to believe that they have some patents on this "standard" which they aren't making available to non-conforming use. They're probably obvious and trivial patents, and thus invalid if you have enough money and care to fight them through the courts for seven years, but this doesn't entice me to have anything to do with their proposal.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  37. Who is the entire web community ? by mrthoughtful · · Score: 2

    Manu Sporny, [...] (said), "The entire Web community should decide which features should be supported – not just Microsoft or Google or Yahoo."

    So just who is the entire Web community? It certainly isn't W3C, who effectively bar individuals and SME's with their $8000 annual membership fees.
    The corporations are only interested in establishing or brokering leverage.
    The IETF isn't the easiest means of establishing support for a feature, and not many of us have read all 6000 odd RFCs anyhow.

    So, basically, who cares what schema org says, or Manu Sporny for that matter?
    Since when has anyone been able to make a change to the status quo?

    --
    This comment was written with the intention to opt out of advertising.
    1. Re:Who is the entire web community ? by msporny · · Score: 1

      Hi, I'm Manu Sporny - the person that authored that article. You ask good questions, but your answers to your own questions do not come from knowledge or understanding of how W3C and IETF work. You seem jaded by the world, let me try and convince you that things are not as awful as you believe them to be. Let me start by answering your most important question:

      Since when has anyone been able to make a change to the status quo?

      Many people do this at W3C, IETF, WHATWG and many other online communities every day. They help make the world a better place. They lead the Web to its full potential. At W3C, they're called Invited Experts and they are just like you and me. They don't come from large companies or people with deep pockets, they do amazing work and are then asked to participate in standards work at no cost to them.

      You are often asked to join W3C because you have a particular expertise in an area. I am an Invited Expert - I've never paid a dime to W3C, but hope to some day because the work they do is so important. In my case, I was working on Microformats, music markup, online payments and structured data in HTML. I approached the RDFa Working Group chair at the time and asked to be a part of the discussion at W3C about RDFa. The chair of the RDFa Working Group at that time was Ben Adida, and he said that he would love to have the Microformats community's input. I was invited to join. I was required to pay absolutely nothing. I've never had to pay anything to W3C and this is because they value expert input on their standards.

      It currently costs $0 to join the HTML Working Group at W3C. You could easily have an effect on HTML5 if you would put in the time to read the spec and comment on it. W3C is legally obligated to respond to you - anyone can make a difference, you just have to try. Here's how you can do it: become an expert in something Web related - invent something new or do lots of implementations and gain more knowledge than your peers. Work hard. When I say "Work Hard", I mean really, really hard. You have to write specs, you have to do implementations, you have to be familiar with at least 20-50 IETF RFCs and you have to be passionate about the future of the Web as a tool to help make humanity better.

      You don't have to care about what schema.org or I say, but don't belittle the great technical work that all Invited Experts (and paid participants) do at the world standards bodies. The Internet and the Web wouldn't be what they are today without these organizations researching, creating and publishing open, patent and royalty free specifications.

      If you contribute to the Web, you are a part of the entire Web community. It's important that you understand that - if you speak, your voice will be heard. As for questioning if the status quo can be changed - it happens every day. I was able to go from relative obscurity in the standards world all the way to chairing a Working Group at an International Standards body based purely on the hard work that I did to get here. It's fine if you want to be jaded about the world, but there is no $8000 fee required to make a difference (just join the mailing list - it's free). Those of us that are not jaded and believe that the Internet and the Web can make all societies better are working as hard as we can to do just that.

      --
      Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
      Founder/CEO - Digital Bazaar, Inc.
    2. Re:Who is the entire web community ? by mrthoughtful · · Score: 1

      Hi there Manu Sporny,

      You gave me a very thorough response and you treated my 'gripe' seriously. I thank you for that. Regardless, I have found plenty of closed doors when attempting to make contributions to the Internet community.

      I (with help from the team) have been working (very hard!) on an opensource xml syntax programming language (called Obyx) over the last nine years (since 2003), which is used as a cgi to serve thousands of public pages. Uptake has been nearly zero. Interest has been nearly zero. W3C are stuck with their own (very similar - but IMO poorly designed) XProc; the project leaders of XProc are not only uninterested in my experience or expertise, they are disinterested in it.

      I believe that the work done on Obyx is remarkable and useful, most especially the -gap() extensions to XPath (see eg http://www.obyx.org/media/images/gaps_227.gif , part of a tutorial on iterations (http://www.obyx.org/tutiteration.html) ) which (more or less) make FLWOR expressions redundant. (Choosing to extend XPath in Obyx was not a decision taken lightly. The only standards-based alternative would be to use FLWOR or XSLT syntaxes, but both of these don't have access to memory stored variables, environment, system parameters, http parameters, cookies, sql fields, functional parameters etc. (just 'file' and 'url') used in Obyx. Likewise, the concept of insertion-points or 'holes' is not new to tree-based data structures, and it allows for us to easily insert elements repeatedly into an object without needing placeholders). Moreover, the design principles behind Obyx (separation of concerns, simplicity, and parsimony) have made it a language that is easy to learn and to use. W3C hasn't been interested in discussing any of this.

      This has been my experience with W3C.
      (I am not alone; just now I see a comment on Jira from one of the guys who author xercesc:- "Good luck in trying to convince W3C.")

      The company that funds the Obyx work is small - I am it's technical director, and have a team of 10 or so under me, but our annual revenue is less than $1M, though we have been around as a web agency since 1996. Every technical individual at the company uses Obyx and loves it once they get used to it, but it takes time to understand the benefits. We cannot afford the entry-price onto W3C, and in the eyes of W3C I am not expert enough to have an opinion.

      I have no relevant academic path; I've been coding for 30 years or so, and come from a generation where computing was done in the field, not at the campus. I am familiar with about 30 RFCs (mainly covering 1945/2616, 822, 959, 854, 707 and all of their affiliated RFCs, as well as many encoder documents eg 2045 etc., and of course I am familiar with 2119 etc., As stated, I've been the technical director of an internet agency for fifteen years, Obyx is the fifth or sixth language that I've written, though it's the only one that I have been proud enough to bring to the public eye, albeit quietly.

      So, I haven't had your experience with 'the community'. Instead I've found it pretty self-obsessed and at least some of it is run by power-players (individuals, organisations) who often have their own agendas, which probably accounts for some of my bitterness in my original comment at /.

      --
      This comment was written with the intention to opt out of advertising.
  38. Blaaaaaaah!!! by transami · · Score: 1

    This is their next big idea? Seriously, do these guys just sit around all day and think "how can we make the life of the developer even more complicated and confusing?".

    --
    :T:R:A:N:S:
  39. Poor Poor Video Games by Splitterside · · Score: 1

    Why is it that Video Games are still not considered as a major source of media? Looking at the full list schema page there is no mention of a video game, even though the industry is larger than the music industry when it comes to revenue and sales. Yet music has many different new tags. Curse you evil big corps!

  40. Mizuno MX-950 Irons -Mizuno Irons Sets -Newgolfdis by wandawei · · Score: 1

    Mizuno MX-950 Irons Multiple technologies and three distinct head designs deliver seamless game improvement performance.
    Lie and Loft adjustable #3 and #4 hybrids feature internal high density tungsten weights to create massive MOI values that deliver high, straight and ultra forgiving shots.


    Mizuno MX-950 IronsExclusive Grain Flow Forged 4135 high strength steel #5 through #7 Hollow Technology hybrid irons also feature internal high density tungsten weights that are located at the lowest and deepest area of the cavity to deliver solid, forgiving and consistent shots.

    MX-950 IronsExclusive Grain Flow Forged 1025E Pure Select mild carbon steel #8 through LW for pin seeking accuracy with soft, solid and consistent feel in your one-piece scoring irons.

    MX-950Irons Seamless custom fitting integration so that your set flows perfectly from #3 to LW to deliver maximum playability.

    Mizuno MX-950 IronsH.E.M.I. COG design philosophy in each iron for maximum energy transfer from club head to ball.

    Durable Double Nickel Chrome plating or with mirror satin finish, on the #5 through LW, provides durability and eliminates glare.

    Mizuno MX-950 IronsModified U-grooves produce the ideal spin rate, for maximum playability in all conditions.

    Extreme wide sole design for forgiveness and consistent playability from all types of lies.


    Fitted with a top quality True Temper Dynalite Gold SuperLite steel shaft. This lightweight steel shaft gives more clubhead speed for a higher, longer ball flight.


    Mizuno MX-950 Irons at http://www.newgolfdiscount.com/goods-632-Mizuno+MX-950+Irons.html
    @import url(http://www.golflink.com/community/js/rte/);@import url(http://www.golflink.com/community/js/rte/);

    --
    we focus on golf clubs online.