- From: Dan Brickley <danbri@google.com>
- Date: Wed, 17 Feb 2021 09:12:59 +0000
- To: Richard Wallis <richard.wallis@dataliberate.com>
- Cc: Lulin Song <song@ldeo.columbia.edu>, "public-schemaorg@w3.org" <public-schemaorg@w3.org>
- Message-ID: <CAK-qy=7KO-yOaXpZGezN2gLj_0H7SLmr-MNnetrK8QViusgYeQ@mail.gmail.com>
Thinking about this specific case, where the only roleName in the article is "coauthor", I would simplify and express everything using a simple "creator" property. Dan On Wed, 17 Feb 2021 at 09:11, Richard Wallis < richard.wallis@dataliberate.com> wrote: > What Dan said... > > Plus: The Google Rich Results Test Tool is only testing for the attributes > that are significant to their [Google's] implementation of Rich Results in > their services. It is not a general Schema.org test tool such as the Structured > Data Linter <http://linter.structured-data.org/>, JSON-LD Playground > <https://json-ld.org/playground/>, etc. > > ~Richard. > > > Richard Wallis > Founder, Data Liberate > http://dataliberate.com > Linkedin: http://www.linkedin.com/in/richardwallis > Twitter: @rjw > > > > On Wed, 17 Feb 2021 at 09:02, Dan Brickley <danbri@google.com> wrote: > >> I believe this is because Google (alongside many others) hasn't much >> support for the Role construction. In retrospect I believe it was too >> general - providing a cross-domain modeling structure as well as vocabulary >> to describe contributor roles, it ended up not doing either very well. The >> markup probably looks OK for "author" because it isn't a property being >> checked for, since "creator" is generally the more widely adopted term. I >> started a thread on Twitter earlier this week exploring ways of improving >> our (Schema.org's) coverage of contributor roles, including connection to >> related initiatives like https://www.niso.org/standards-committees/credit >> and others. https://twitter.com/danbri/status/1361197025065320449 >> >> Dan >> >> On Wed, 17 Feb 2021 at 08:48, Lulin Song <song@ldeo.columbia.edu> wrote: >> >>> Hi schema.org, >>> >>> I am working on JSON-LD content for 'Dataset' type. The dataset has >>> multiple authors. I used Google Rich Results Test Tool. >>> https://search.google.com/test/rich-results?utm_campaign=sdtt&utm_medium=message >>> >>> The following 'author' syntax is correct according the test tool. But if >>> I replaced 'author' with 'creator', the tool said 'Invalid object type for >>> field "creator". I read through schema.org documents, it seems both >>> should work. Can someone explain why it failed on 'creator'? >>> "author": [ >>> { >>> "@type": "Role", "roleName": "Lead Author", >>> "author": [ >>> { >>> "@type": "Person", >>> "name": "C E Nehru", >>> "givenName": "C", >>> "familyName": "Nehru" >>> } >>> ] >>> }, >>> { >>> "@type": "Role", "roleName": "Coauthor", >>> "author": [ >>> { >>> "@type": "Person", >>> "name": "Martin Prinz", >>> "givenName": "Martin", >>> "familyName": "Prinz" >>> }, >>> { >>> "@type": "Person", >>> "name": "Eric Dowty", >>> "givenName": "Eric", >>> "familyName": "Dowty" >>> }, >>> { >>> "@type": "Person", >>> "name": "Klaus Keil", >>> "givenName": "Klaus", >>> "familyName": "Keil" >>> } >>> ] >>> } >>> ], >>> >>> Thanks, >>> Lulin Song >>> Geoinformatics >>> Lamont-Doherty Earth Observatory >>> Columbia University >>> >>> >>>
Received on Wednesday, 17 February 2021 09:13:49 UTC