All I could think while reading through the getting started was: that is an awful lot of added text. After a little more thought: that is an awful lot of added work. And while it won't be hard to have tools that make the process easier, the sort of work that goes into adding that data can never be completely automated (otherwise, we would have no need for it). Given that all the search engines will be using it, all m…
Introducing schema.org: Search engines come together for a richer web
11–20 of 80 posts
Re: Introducing schema.org: Search engines come together for a richer web
#12The question remains: Who needs this? I am still not really convinced that it is possible to integrate handcoded schemas for a wide range of use cases into search results in a meaningful way. The solution Google proposes here will also restrain the content of websites in a lot of ways if it becomes widely adopted. Look at the recipes-example, it defines markup for including nutrition information for recipes: "Can con…
Chicken recipe where calories<=350 and carbs<=20g
Re: Introducing schema.org: Search engines come together for a richer web
#13The question remains: Who needs this? I am still not really convinced that it is possible to integrate handcoded schemas for a wide range of use cases into search results in a meaningful way. The solution Google proposes here will also restrain the content of websites in a lot of ways if it becomes widely adopted. Look at the recipes-example, it defines markup for including nutrition information for recipes: "Can con…
I do, because I can get better search results: Chicken recipe where calories<=350 and carbs<=20g
Re: Introducing schema.org: Search engines come together for a richer web
#14So Google both ranks on page speed and encourages you to double your bits by adding a lot of cruft to your html. Wonderful.
Re: Introducing schema.org: Search engines come together for a richer web
#15Earlier quoted context omitted.
I'm torn as well. It's a lot of new information to remember and creates a lot of extra work but if the content is more accessible as a result then it might be worth it. I'm also a little wary of the fact that it just seems tacked on to the HTML but I can't think of any other way to handle it. I'm guessing this is like salt... a little dash'll do it.
I would say it's just more easy for them to parse/extract data, it shouldn't change much to the user (excerpt special cases in browsers).
Re: Introducing schema.org: Search engines come together for a richer web
#16Re: Introducing schema.org: Search engines come together for a richer web
#17Re: Introducing schema.org: Search engines come together for a richer web
#18Re: Introducing schema.org: Search engines come together for a richer web
#19All I could think while reading through the getting started was: that is an awful lot of added text. After a little more thought: that is an awful lot of added work. And while it won't be hard to have tools that make the process easier, the sort of work that goes into adding that data can never be completely automated (otherwise, we would have no need for it). Given that all the search engines will be using it, all m…
I was just thinking about how I could actually see this being really awesome with something like Django.
Re: Introducing schema.org: Search engines come together for a richer web
#20So Google both ranks on page speed and encourages you to double your bits by adding a lot of cruft to your html. Wonderful.