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."

27 of 192 comments (clear)

  1. 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 Homburg · · Score: 2

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

    3. 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.
    4. 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...

  2. 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.
  3. 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 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.

    2. 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.

    3. 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).

    4. 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.
    5. 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.

  4. 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!
  5. 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.
  6. 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.

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

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

  8. 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.

  9. 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
  10. 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.
  11. 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.

  12. 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.

  13. 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.

  14. 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
  15. 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!
  16. 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..
  17. 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>

  18. 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.