- From: Elias Kaerle <elias.kaerle@sti2.at>
- Date: Tue, 7 Jun 2016 12:44:56 +0200
- To: Bäck, Gerald <gerald@baeck.at>
- Cc: "schema.org Mailing List" <public-schemaorg@w3.org>
Hi Gerald, I agree. Another solution could be to simply accept schema:Person and schema:Organization as publisher. Maybe one of the people maintaining schema.org can comment on that issue!? Best, Elias On 07.06.2016 10:59, Bäck, Gerald wrote: > Hi Elias, > > the interesting thing is, if you put a logo field into the person entity, > google validator claims that a logo field is not valid within the person > entity:) The conclusion is that persons cannot be publishers, which is > simply wrong. > > My proposal is to get rid of the publisher entity as a requirement, because > blogposts and websites still need an author which should be enough for > private run blogs. > > best wishes, Gerald > > > > > ---- > DI Gerald Bäck | fb <https://facebook.com/geraldbaeck> | blog > <http://www.baeck.at/> | devblog <http://dev.baeck.at> | fitblog > <http://fitness.baeck.at> | +43 664 5107761 <+436645107761> > > On Tue, Jun 7, 2016 at 9:44 AM, Elias Kaerle <elias.kaerle@sti2.at> wrote: > >> Hi Gerald, >> >> this is indeed a strange behaviour. I would blame it on the way Google's >> structured data testing tool works: it does, as far as i know, not >> necessarily validate/verify annotations strictly the way schema.org >> defines them, but more in a way they need the annotations for feeding >> their Rich Snippets and Rich Cards. >> >> So I would assume Google doesn't care about having a schema:Person as a >> publisher, but requires a logo (or some kind of picture) to process a >> beautiful Rich Snippet/Rich Card out of it. >> >> Best, Elias >> >> On 07.06.2016 08:36, Bäck, Gerald wrote: >>> Hi, >>> >>> I am currently doing my first steps with JSON-LD and try it on my private >>> blog. As far as I understand Blogposts do require a publisher field, >> which >>> can only be an organisation. But I think it should be possible for >> persons >>> to be publishers too, but I also would like to question, that blogposts >> or >>> even Websites do need a publisher field at all. >>> >>> I tested my blog with Google's Structured Data Testing Tool. >> Interestingly >>> enough the tool did not complain about the publisher being a Person, but >>> that the publisher entitiy had no logo, which on the other hand is not >>> allowed as a field for a person. >>> >>> >> https://search.google.com/structured-data/testing-tool#url=http%3A%2F%2Fwww.baeck.at%2Fblog%2F2016%2F05%2F30%2FWahlmanipulationen%2F >>> >>> I also tested the root of my blog, which is defined as website, also with >>> myself as a publisher person. This time the tool was fine with it. >>> >>> >> https://search.google.com/structured-data/testing-tool#url=http%3A%2F%2Fwww.baeck.at%2F >>> >>> thx, Gerald >>> >>> >>> >>> ---- >>> DI Gerald Bäck | fb <https://facebook.com/geraldbaeck> | blog >>> <http://www.baeck.at/> | devblog <http://dev.baeck.at> | fitblog >>> <http://fitness.baeck.at> | +43 664 5107761 <+436645107761> >>> >> >> -- >> Elias Kärle, MSc >> Semantic Technology Institute >> University of Innsbruck >> >> ICT - Technologie Park Innsbruck >> 2nd Floor, Room 3S02 >> Technikerstrasse, 21a >> 6020 Innsbruck >> Austria >> >> Tel.: (+43) 512 507 53738 >> Skype: elias.kaerle >> >> > -- Elias Kärle, MSc Semantic Technology Institute University of Innsbruck ICT - Technologie Park Innsbruck 2nd Floor, Room 3S02 Technikerstrasse, 21a 6020 Innsbruck Austria Tel.: (+43) 512 507 53738 Skype: elias.kaerle
Received on Tuesday, 7 June 2016 10:45:29 UTC