<div>Hi,</div>
<div> </div>
<div>In one of our recent study we analyzed the current implemented instance data, marked with GR Ontology and will be available shortly. </div>
<div> </div>
<div>Regarding "What Part" of ontology terms recognized (or indexed) by search engines (Google and Yahoo!) follows:</div>
<div> </div>
<div><span style="FONT-FAMILY: 'Times','serif'; FONT-SIZE: 9pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-IE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA" lang="EN-IE">"Our investigation found that Yahoo and Google currently includes price, availability (Google only), description and product pictures drawn from GRO annotated structured data as part of their enhanced search results"</span></div>
<div><span style="FONT-FAMILY: 'Times','serif'; FONT-SIZE: 9pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-IE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA" lang="EN-IE"></span> </div>
<div><span style="FONT-FAMILY: 'Times','serif'; FONT-SIZE: 9pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-IE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA" lang="EN-IE">The above data elements are what get displayed to user but to what extend search engines extract and store in their database is not know yet. Best guess is that they extract maximum set of structured data from webpages and will use in future when, relevent information is helpful to improve search result such as Product ontology </span></div>
<div><span style="FONT-FAMILY: 'Times','serif'; FONT-SIZE: 9pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-IE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA" lang="EN-IE"></span> </div>
<div><span style="FONT-FAMILY: 'Times','serif'; FONT-SIZE: 9pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-IE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA" lang="EN-IE">Regards</span></div>
<div><span style="FONT-FAMILY: 'Times','serif'; FONT-SIZE: 9pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-IE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA" lang="EN-IE">jamshaid</span></div>
<div><span style="FONT-FAMILY: 'Times','serif'; FONT-SIZE: 9pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-IE; mso-fareast-language: EN-US; mso-bidi-language: AR-SA" lang="EN-IE"></span> </div>
<div><br> </div>
<div class="gmail_quote">On Tue, Mar 8, 2011 at 10:59 PM, Aaron Bradley <span dir="ltr"><<a href="mailto:aaranged@yahoo.com">aaranged@yahoo.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div style="FONT-FAMILY: tahoma, new york, times, serif; FONT-SIZE: 10pt">GoodRelations is one of the markup formats supported by Google to produce rich snippets in search engine results pages.<br><br>Rich snippets are described in broad terms here:<br>
<span><a href="http://googlewebmastercentral.blogspot.com/2010/11/rich-snippets-for-shopping-sites.html" target="_blank">http://googlewebmastercentral.blogspot.com/2010/11/rich-snippets-for-shopping-sites.html</a></span><br>
And by this suite of Google reference pages:<br><span><a href="http://www.google.com/support/webmasters/bin/topic.py?topic=21997" target="_blank">http://www.google.com/support/webmasters/bin/topic.py?topic=21997</a></span><br>
<br>This related Google page contains a product properties table comparing hProduct, GoodRelations, Google Product format and Google Merchant Center feed properties :<br><span><a href="http://www.google.com/support/webmasters/bin/answer.py?answer=186036" target="_blank">http://www.google.com/support/webmasters/bin/answer.py?answer=186036</a></span><br>
<br>That sort of answers "what part" of GoodRelations is currently supported by Google, insofar as I understand that question. Namely product-related information that appears in rich snippets. To the best of my knowledge the gr:BusinessEntity is not used, say, to produce localized geo-targeted listings (e.g., Google Map pins), but I could be wrong and would welcome any evidence to the contrary (as I think it would be a sensible use of these data by Google).<br>
<br>Bing has yet to formally support any structured product data, but I would be very surprised if this continues indefinitely. As Yahoo results are now powered by Bing, Yahoo's legacy support of GoodRelations may mean that enhanced product information appears there:<br>
<span><a href="http://ebusiness-unibw.org/pipermail/goodrelations/2010-August/000245.html" target="_blank">http://ebusiness-unibw.org/pipermail/goodrelations/2010-August/000245.html</a></span><br><br>More generally in terms of ROI, I'd offer the opinion that structured product markup to better inform the search engines and enhance search results is here to stay - so I think an investment in GoodRelations is a safe one. And for any merchant that sells products online, there's not a lot of additional technical overhead involved in producing GoodRelations markup for those already producing a Google Merchant Center feed (where the investment for the latter is, perhaps, easier to justify, as it is required to turn up in Google shopping results).<br>
<br>As an aside, have you ever considered a forum Martin?<br><br><br> 1. What parts of Goodrelations are implemented by major search<br>
<div style="FONT-FAMILY: tahoma, new york, times, serif; FONT-SIZE: 10pt">
<div style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 13px"> engines? (L?szl? T?r?k)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 8 Mar 2011 11:12:10 +0100<br>
From: L?szl? T?r?k <<a href="mailto:ltorokjr@gmail.com" target="_blank">ltorokjr@gmail.com</a>><br>Subject: [goodrelations] What parts of Goodrelations are implemented<br> by major search engines?<br>To: <a href="mailto:goodrelations@ebusiness-unibw.org" target="_blank">goodrelations@ebusiness-unibw.org</a><br>
Message-ID:<br> <AANLkTimcSymtmok_AGdEUbkm+R3qYZ=<a href="mailto:AtToaej-OsEQG@mail.gmail.com" target="_blank">AtToaej-OsEQG@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"
<div>
<div></div>
<div class="h5"><br><br>Hi,<br><br>I was going over the GoodRelations wiki in the last too days, a very<br>comprehensive work even if some of it is still WIP.<br>The wiki is well formulated, I did not have any issues with understanding<br>
the concepts and methods described there.<br><br>However, there is one important missing page that is essential for adopters<br>on the data provider side IMHO.<br>Considering the compelling use case of semantic SEO and increased visibility<br>
via marking up the products and services with GoodRelations, I cannot<br>currently tell, what part of the GoodRelations vocabulary is supported by<br>major search engines (Yahoo, Google). I found the links to Google Rich<br>
Snippets and Yahoo Searchmonkey, however, I am still missing something like<br><a href="http://en.wikipedia.org/wiki/Comparison_of_layout_engines_" target="_blank">http://en.wikipedia.org/wiki/Comparison_of_layout_engines_</a>(HTML_5).<br>
<br>It is clear that there is a chicken-and-egg problem with respect to who<br>should implement support first. (data providers or data consumers).<br>Therefore, I am sure there will be arguments, that the more data providers<br>
implement, the higher the incentive for search engines to support it.<br><br>However, if I am running an e-commerce site even as small as simple web shop<br>running on a shared server, I want to be able to assess the return on<br>
investment that goes into the semantic markup.<br><br>Has this concern been raised previously?<br><br>Many thanks,<br><br></div></div>Laszlo T?r?k<br><br></div></div></div><br></div><br>_______________________________________________<br>
goodrelations mailing list<br><a href="mailto:goodrelations@ebusiness-unibw.org">goodrelations@ebusiness-unibw.org</a><br><a href="http://ebusiness-unibw.org/cgi-bin/mailman/listinfo/goodrelations" target="_blank">http://ebusiness-unibw.org/cgi-bin/mailman/listinfo/goodrelations</a><br>
<br></blockquote></div><br>