Issue using creator property with http://www.schema.org/Review about linter HOT 3 CLOSED

Yes, this is confusing. The RDF to Microdata spec uses a registry to determine if values should be in a list or not; as it ends up, Google doesn't actually make use of this, but it creates an RDF signature that looks like the following:

@prefix md: <http://www.w3.org/ns/md#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfa: <http://www.w3.org/ns/rdfa#> .
@prefix schema: <http://schema.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<> md:item (<AllCareCorp>);
   rdfa:usesVocabulary schema: .

<AllCareCorp> a schema:Corporation;
   schema:review [
     a schema:Review;
     schema:creator ([
         a schema:Person;
         schema:name "John Doe";
         schema:worksFor [
           a schema:Organization;
           schema:name "A Company"
         ]
       ]);
     schema:reviewBody "\"We get everything on time.\""
   ],  [
     a schema:Review;
     schema:creator ([
         a schema:Person;
         schema:name "Jane Doe";
         schema:worksFor [
           a schema:Organization;
           schema:name "Another Company"
         ]
       ]);
     schema:reviewBody "\"Amazing Team.\""
   ] .

As a result, the value is an rdf:List, which contains a single schema:Person, so the linter is complaining that rdf:List (and superclass rdfs:Resource) are not in the range of schema:creator, which they aren't.

Arguably, the schema.org data model should allow a list to be in range if every member of that list is in range. This is not without precedent, as similar logic is used to validate schema:Role.

Also, a future version of the Microdata to RDF spec may change the registry to use the published schema.org JSON-LD context instead, in which case we would be consistent with how schema.org actually defines properties such as schema:creator.

I'll make this a feature request to change the schema.org content model to allow this, although the change will go in another library.

from linter.

Thank you for your detailed explanation. Everytime I think I have a good handle on structured web data, a new layer of the onion if revealed :-) As these are textual reviews, I'll switch over to author for now as that appears to carry the same semantic meaning in this context.

from linter.

Released in version 1.1.2 now live.

from linter.