structured-data

I'm using some Microdata to describe a blog post, and I'm surprised by the value return for Schema.org’s BlogPosting by the Google Developers Testing Tool. I would have expected it to be the itemprop url , not a merge of the website URL and the item id . Am I doing something wrong, or is it only a Google display issue? <div itemscope="itemscope" itemprop="blogPost" itemtype="http://schema.org/BlogPosting" id="foobar"> <a itemprop="url" href="/realone">real</a> </div> Value returned by https://developers.google.com/structured-data/testing-tool/ : BlogPosting: http://www.example.com/foobar url:

When using SQL or MySQL (or any relational DB for that matter) - I understand that saving the data in regular columns is better for indexing sake and other purposes... The thing is loading and saving JSON data is sometimes a lot more simple. and makes the development easier. Are there any "golden rules" for saving raw JSON data in the DB? is it absolutely wrong practice to do so? SUMMARY Very nice answers were given, but no doubt the most well organized is the answer given by @Shnugo which deserves the bounty. Would also like to point out answers given by @Gordon Linoff and @Amresh Pandey for

There is this fancy infobox in <some Wikipedia article>. How do I get the value of <this field and that>? Tgr The wrong way: trying to parse HTML Use (cURL/jQuery/file_get_contents/requests/wget/ more jQuery ) to fetch the HTML article code of the article, then use a DOM parser to extract table.infobox tr[3] td / use a regex . This is actually a really bad idea most of the time. Wikipedia's HTML code is not particularly parsing-friendly (especially infoboxes which are a system of hand-written templates), the exact structure changes from infobox to infobox, and the structure of an infobox might