170 karma · joined January 8, 2010
Socials: - github.com/cafca
---
The problem is that this line of thought automatically devalues everything not from your own country if it can be compared to something from your own country. Since everything from your country has an intrinsic value to you, everything not from your country lacks this value and is therefore less valuable to you. This would be OK if it was limited to manufactured products but sadly it includes people as well as whole cultures.
So being proud of your country makes you devalue everything from other countries before even considering its real value.
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 contain the following child elements: servingSize, calories, fat, saturatedFat, unsaturatedFat, carbohydrates, sugar, fiber, protein, cholesterol"
Every company that serves recipes on the web and decides not to offer this information because it deems other properties of recipes more important is now at a disadvantage. Google will show more information about the recipes of their competitors and presumably also rank them higher because they have included 'valuable' markup information in their recipe.
This approach favors shallow information ressources over complex ones as the former can be more easily parsed by metadata-crawlers.
Reminds me of Ken Follett's 'On Wings of Eagles' - definitely a recommendation if you're into thrillers! It's about a team of coders from EDS (now part of HP I think) who get sent to Iran to work for the government and are then refused to leave the country.
At least I remember them talking about a plan to allow users plugging their own S3 instance in (that was years ago).
* Generate a random price in the acceptable range (but don't tell the user about it)
* Let the user know that you made up a price and let him enter what he would pay
* If the user entered a higher price than the random one he gets the product, otherwise he doesn't
Of course this only works if you keep the user from trying to do this multiple times, for example by offering an invite-only system and giving every invitee only one chance.