Inverse property for author?

[Sergio Redondo]

Hi, all!

Is there any inverse property for 'author'? The thing is that, when we mark up someone's page, it could be useful to have something like 'creativeWork' (not the type, but a property instead). I can't find anything similar.

Thanks in advanced

[Richard Wallis]

Hi Sergio,

The simple answer is no.

As structured (semantic) data relationships are effectively bidirectional there should be no need.

If you describe the CreativeWork with an author or creator property that references the id of the person, the parsers utilised by the data consumers will infer the relationship you are looking for.

If the primary purpose of the page is to describe the Person, remember to use the mainEntityOfPage property (and/or the mainEntity property of the. WebPage) to point the consumers in the right direction.

~Richard. 

--
You received this message because you are subscribed to the Google Groups "Semantic Search Marketing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semantic-search-ma...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/semantic-search-marketing/600795a1-c66f-471d-8a3d-e65bd2766414n%40googlegroups.com.

--

Richard Wallis

Founder, Data Liberate

http://dataliberate.com

Linkedin: http://www.linkedin.com/in/richardwallis

Twitter: @dataliberate @rjw

[jarnovandriel]

There's no inverse like 'authorOf' if that's what you mean. Main reason there's not such an inverse (nor for properties like 'creator', 'contributor', etc.) is to prevent adding a reverse property for nearly everything - thus causing tons of vocabulary bloat. Instead of doing that we have alternative options for making such a relation via syntax instead:

1) Creating a triple like: Article > author > Person by using the object's fragment identifier:

{
  "@context": "https://schema.org",
  "@graph":
  [
    {
      "@id": "https://example.com/authors/wile-e-coyote/#Person",
      "@type": "Person",
      "name": "Wile E. Coyote"
    },{
      "@type":"Article",
      "name": "New explosive tennis balls are da bomb",
      "author": {"@id":"https://example.com/authors/wile-e-coyote/#Person"}
    }
  ]
}

2) Creating a triple like: Article > author > Person making the statement in reverse by using the subject's fragment identifier:
{
  "@context": "https://schema.org",
  "@graph":
  [
    {
      "@type": "Person",
      "name": "Wile E. Coyote",
      "@reverse":
      {
        "author": {"@id":"https://example.com/authors/wile-e-coyote/#Article"}
      }
    },{
      "@id": "https://example.com/authors/wile-e-coyote/#Article",
      "@type":"Article",
      "name": "New explosive tennis balls are da bomb"
    }
  ]
}

[Sergio Redondo]

Thank you very much, Richard.

[Sergio Redondo]

Thank you very much, Jarno. I didn't know about @reverse statement.

[jarnovandriel]

Just so you're aware, you can only make reverse statements in RDFa (rev="") and JSON-LD (@reverse), microdata doesn't have such an attribute. Some years back an attempt was made to add an 'itemprop-reverse' to the microdata specs but this didn't make it.

[Jarno van Driel]

That makes total sense Jason though whether search engines actually follow such references and use them is up for debate as there's no documentation stating they make use of cross page/website entity referencing. Google seems to mostly focus on the structured data about a page itself.

Op ma 20 mrt 2023 om 13:17 schreef Jason Barnard <ja...@kalicube.com>:

Hi Jarno

If I were to place this on my website to indicate that I wrote an article that appears on another site (Searchenginejournal, for example)

Does this make sense?

{
  "@context": "https://schema.org",
  "@graph":
  [
    {
      "@id": "https://example.com/authors/wile-e-coyote/#Person",
      "@type": "Person",
      "name": "Wile E. Coyote"
    },{
      "@type":"Article",

     "@id": "https://hugemediasite.com/articles/new-explosive-tennis-balls/#Article",

      "url": "https://hugemediasite.com/articles/new-explosive-tennis-balls/",

      "name": "New explosive tennis balls are da bomb",

      "author": {"@id":"https://example.com/authors/wile-e-coyote/#Person"}
    }
  ]
}

What is the logic of reverse?

Perhaos you can explain that on Wednesday.

Thanks!

Jason

--
You received this message because you are subscribed to the Google Groups "Semantic Search Marketing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semantic-search-ma...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/semantic-search-marketing/94d4ca49-fa5a-4bc1-9b68-b4c568bb5940n%40googlegroups.com.

[Jarno van Driel]

Your last example would be quite fine. To extend a bit on it, you can add multiple Articles if you need to:

{
  "@context": "https://schema.org",
  "@graph":
  [
    {
      "@type": "Person",  

      "@id": "https://example.com/authors/wile-e-coyote/#mainEntityOfPage",
      "mainEntityOfPage": {
        "@type": "ProfilePage",
        "@id": "https://example.com/authors/wile-e-coyote/"

      },
      "name": "Wile E. Coyote",

      "url": "https://example.com/authors/wile-e-coyote/",
      "@reverse":
      {
        "author":
        [

          {
            "@type":"Article",
            "@id": "https://hugemediasite.com/articles/new-explosive-tennis-balls/#Article",
            "url": "https://hugemediasite.com/articles/new-explosive-tennis-balls/",

            "headline": "New explosive tennis balls are da bomb"
          },{
            "@type":"Article",
            "@id": "https://hugemediasite.com/articles/diy-paint-tunnels-are-super-realistic/#Article",
            "url": "https://hugemediasite.com/articles/diy-paint-tunnels-are-super-realistic/",
            "headline": "DIY paint tunnels are super realistic"
          }
        ]
      }
    }
  ]
}

Op ma 20 mrt 2023 om 14:12 schreef Jason Barnard <ja...@kalicube.com>:

So, given your other explanation, the reverse would be better (if Google looks at the page in isolation).

{
  "@context": "https://schema.org",
  "@graph":
  [
    {
      "@type": "Person",
      "name": "Wile E. Coyote",
      "@reverse":
      {
        "author": {

"@type":"Article",

     "@id": "https://hugemediasite.com/articles/new-explosive-tennis-balls/#Article",

      "url": "https://hugemediasite.com/articles/new-explosive-tennis-balls/",
      "name": "New explosive tennis balls are da bomb",

      }

    },{
      "@id": "https://example.com/authors/wile-e-coyote/#Article",
      "@type":"Article",
      "name": "New explosive tennis balls are da bomb"
    }
  ]
}

OR simpler, this

{
  "@context": "https://schema.org",
  "@graph":
  [
    {
      "@type": "Person",
      "name": "Wile E. Coyote",
      "@reverse":
      {
        "author": {

"@type":"Article",
     "@id": "https://hugemediasite.com/articles/new-explosive-tennis-balls/#Article",
      "url": "https://hugemediasite.com/articles/new-explosive-tennis-balls/",
      "name": "New explosive tennis balls are da bomb"
      }
      }
    }

  ]
}

[Sergio Redondo]

Wow! That last use of @reverse is pretty amazing. Thank you!