From martin.hepp at ebusiness-unibw.org Tue Aug 2 12:47:16 2011 From: martin.hepp at ebusiness-unibw.org (Martin Hepp) Date: Tue, 2 Aug 2011 12:47:16 +0200 Subject: [goodrelations] Google / prices in Euro - Bug & Work-around In-Reply-To: <884B7204-9A97-4E6B-B735-A1A450BF443C@ebusiness-unibw.org> References: <884B7204-9A97-4E6B-B735-A1A450BF443C@ebusiness-unibw.org> Message-ID: <6A8351D6-529E-4388-A568-F387F27D9ED7@ebusiness-unibw.org> Dear all: Google seems to have fixed this problem - see http://www.google.com/webmasters/tools/richsnippets?url=http%3A%2F%2Fwww.tradoria.de%2Fernaehrung%2Fpro-sana-l-glutamin-1-beutel-500g-21797.html&view= and the attached screenshot - the price is correctly shown as EUR 11.99. Best wishes Martin Hepp -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen shot 2011-08-02 at 12.44.15 PM.png Type: image/png Size: 58869 bytes Desc: not available URL: -------------- next part -------------- On Jun 21, 2011, at 9:07 AM, Martin Hepp wrote: > Dear all: > > There is a small bug in Google's Rich Snippet testing tool: > > If the currency is "EUR", then the price may be rendered incorrectly - in some cases, the digits following the delimiter (99.xx - the fractional part) are treated as if they were part of the main digits (i.e. the integer part). > > Example: > > foo:price a gr:UnitPriceSpecification ; > gr:hasCurrency "EUR"^^xsd:string ; > gr:hasCurrencyValue "99.00"^^xsd:float . > > can, in some cases, show up as > > EUR 9900.00 > > Google is working on the issue and we assume at this point that this is just a bug in the validator, not in the actual Google rendering component. > > Other currencies are not affected, as far as we know. > > As a work-around, we recommend that you remove the fractional part from currency values if it is ".00". > > So for those values, please use > > foo:price a gr:UnitPriceSpecification ; > gr:hasCurrency "EUR"^^xsd:string ; > gr:hasCurrencyValue "99.00"^^xsd:float . > > or in RDFa > >
>
>
>
>
> > instead of > >
>
>
>
>
> > This is just a precautionary measure. At this moment, we have not seen this bug in actual Google search results, just in the testing tool. > > > Best wishes > > Martin Hepp > > > _______________________________________________ > goodrelations mailing list > goodrelations at ebusiness-unibw.org > http://ebusiness-unibw.org/cgi-bin/mailman/listinfo/goodrelations From martin.hepp at ebusiness-unibw.org Wed Aug 3 10:17:51 2011 From: martin.hepp at ebusiness-unibw.org (Martin Hepp) Date: Wed, 3 Aug 2011 10:17:51 +0200 Subject: [goodrelations] Bookmarklet for the Google Rich Snippet Testing Tool Message-ID: <83CB60A3-824C-4EA4-AC46-E693F540C649@ebusiness-unibw.org> Dear all: Many of you frequently use the Google Rich Snippet Testing Tool at http://www.google.com/webmasters/tools/richsnippets to check that your markup validates with the Google parser. You can easily create a link in your browser's bookmark bar to send the current page to this tool: 1. Create a new bookmark. 2. Paste the following line into the address (URL) field of that bookmark: javascript:location.href = 'http://www.google.com/webmasters/tools/richsnippets?url=' + location.href; That's it. Best wishes Martin Hepp From martin.hepp at ebusiness-unibw.org Wed Aug 3 10:55:12 2011 From: martin.hepp at ebusiness-unibw.org (Martin Hepp) Date: Wed, 3 Aug 2011 10:55:12 +0200 Subject: [goodrelations] RDFa prefix definitions References: Message-ID: <65F4AFDC-B374-4D55-9406-A39264B74D8A@ebusiness-unibw.org> There was a discussion on the RDFa mailing list which may be relevant for users of GoodRelations, see below. In a nutshell, the RDFa prefix definitions are better put in the element than in the element of HTML markup. Best Martin Hepp Begin forwarded message: > >> Resent-From: public-rdfa-wg at w3.org >> From: Ivan Herman >> Date: August 2, 2011 1:51:41 PM GMT+02:00 >> To: Manu Sporny >> Cc: RDFa WG >> Subject: Re: PROPOSAL: Restrict @prefix declaration to the root element >> >> This proposal would lead to major issues with character encoding, see >> >> http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Apr/0107.html >> >> Executive summary of that mail: HTML5 works with content sniffing to find out the character encoding of the source (looking for a relevant element in the head). This is done by HTML parsers, too, not only browsers. Having lots of prefix declarations in the elements might lead to erroneous character encoding in the literal objects of the generated RDF; and there is no real defense against that (unless the HTTP return header provides a correct character encoding, but that is not always the case). >> >> Actually, the advise (currently in the Primer, too) is _not_ to put too many @prefix declaration in the element to avoid such issues, but put them into, say, the element. >> >> I do not think we should do this. >> >> Ivan >> >> On Jul 19, 2011, at 04:54 , Manu Sporny wrote: >> >>> This proposal was raised during the telecon last week[1]. Since document >>> authors can declare @prefix anywhere in the document, they could >>> introduce authoring mistakes due to copy-paste. That is, if they do not >>> pay attention to where the @prefix is declared, they may accidentally >>> attempt to express triples that do not have a CURIE prefix defined. >>> >>> While a number of people in the group feel that copy-paste issues are >>> not really that prevalent, limiting the use of @prefix to just the root >>> element of the document may decrease the possibility of copy-paste >>> errors. That is, copying from one place to another place in the document >>> would not be affected by @prefix declaration. >>> >>> The down-side to this is that all Web page authors do not have access to >>> the root element in a document, which is typically set by the content >>> management system. This would disallow people that know what they're >>> doing from expressing triples in their sub-sections of the document - >>> such as blog articles or comment posts. >>> >>> PROPOSAL: Limit @prefix declaration to the root element in the document. >>> >>> -- manu >>> >>> [1]http://www.w3.org/2010/02/rdfa/meetings/2011-07-14#ISSUE__2d_96__3a__Document_not_ready >>> >>> -- >>> Manu Sporny (skype: msporny, twitter: manusporny) >>> President/CEO - Digital Bazaar, Inc. >>> blog: PaySwarm Developer Tools and Demo Released >>> http://digitalbazaar.com/2011/05/05/payswarm-sandbox/ >>> >>> >> >> >> ---- >> Ivan Herman, W3C Semantic Web Activity Lead >> Home: http://www.w3.org/People/Ivan/ >> mobile: +31-641044153 >> PGP Key: http://www.ivan-herman.net/pgpkey.html >> FOAF: http://www.ivan-herman.net/foaf.rdf >> >> From martin.hepp at ebusiness-unibw.org Wed Aug 3 11:03:24 2011 From: martin.hepp at ebusiness-unibw.org (Martin Hepp) Date: Wed, 3 Aug 2011 11:03:24 +0200 Subject: [goodrelations] Maintenance downtime Message-ID: <7C8A289F-D318-4B81-84FF-C05CE66E691F@ebusiness-unibw.org> Dear all: Some GoodRelations services, including the Wiki and the mailing list, will be unavailable between 09/August/2011 11:00 pm and 10/August/2011 06:00 am CEST due to planned maintenance on the infrastructure of one of our data centers. The work on the low-voltage main distribution will require the shutdown of parts of the infrastructure to protect the technicians involved. The ontology itself in RDF/XML and HTML from http://purl.org/goodrelations/v1 and the ontology main page from http://purl.org/goodrelations/ will not be affected. Best wishes Martin Hepp -------------------------------------------------------- martin hepp e-business & web science research group universitaet der bundeswehr muenchen e-mail: hepp at ebusiness-unibw.org phone: +49-(0)89-6004-4217 fax: +49-(0)89-6004-4620 www: http://www.unibw.de/ebusiness/ (group) http://www.heppnetz.de/ (personal) skype: mfhepp twitter: mfhepp