search

schemaorg / suggestions-questions-brainstorming

Suggestions, questions, and brainstorming
19 stars 15 forks source link

blogPost and BlogPosting #5

Open SchemaMarkApp opened 4 years ago

SchemaMarkApp commented 4 years ago

I have an issue with BlogPosting and blogPost, 1.BlogPosting is a sub category for SocialMediaPosting, so what would one do if it is just a blog post? 2.when using blogPost, it cannot be a "mainEntityOfPage" which makes no sense, if an article is posted within a blog, its blogPost right? but Google's validator is giving errors saying "blogPost" cannot be a mainEntityOfPage. which doesnt make sense, yes at top level its a "WebPage" but, its also a blogPost

chrisspradling1980 commented 4 years ago

noticed an "altered ego" container personality type on Covalent Logic and never seen it on Schema.

This is getting interesting.

On Sun, May 24, 2020, 11:11 AM SchemaMarkApp notifications@github.com wrote:

I have an issue with BlogPosting and blogPost, 1.BlogPosting is a sub category for SocialMediaPosting, so what would one do if it is just a blog post? 2.when using blogPost, it cannot be a "mainEntityOfPage" which makes no sense, if an article is posted within a blog, its blogPost right? but Google's validator is giving errors saying "blogPost" cannot be a mainEntityOfPage. which doesnt make sense, yes at top level its a "WebPage" but, its also a blogPost

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/schemaorg/schemaorg/issues/2582, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADFVNUV2G3UKKYKJ2ETXSXDRTFBKNANCNFSM4NI6JAAQ .

jvandriel commented 4 years ago

I think you're confusing the 2. BlogPosting is a type whereas blogPost is a property. And only types can have properties (like mainEntityOfPage), properties don't have properties of their own.

A markup example of this is:

{
  "@type":"Blog",
  "url":"https://example.com",
  "blogPost":
  {
     "@type":"BlogPosting",
     "mainEntityOfPage":"https://example.com/some-title"
  }
}
danbri commented 4 years ago

I think @jvandriel is right here. There is a big difference in schema.org between types (aka classes) and properties. We never name types with an initial lowercase letter; they are always named with an initial capital. So "foo" is a property, you can tell from its name, while "Bar" would be a type. Instances of types are described by, and linked via, properties. We don't normally talk about instances of properties. The value of "mainEntityOfPage" will be some particular thing, possibly described using a schema.org type.

There is a subtle question to ask here, which is whether it is better to consider a BlogPost to ever be the the mainEntityOfPage for pages it appears in, rather than the thing that the BlogPost is about (e.g. some Person, Recipe, Event, Country or whatever). Schema.org is currently agnostic about this; I could see value in both approaches under different conditions, so it is best to look at what specific applications you care about are doing.

danbri commented 4 years ago

I've moved this over from the schema.org main repository to allow conversations to continue freely. The new approach (using suggestions-questions-brainstorming for questions and brainstorming/suggestions) is because over the years the project has accumulated a huge number of open issues where reasonable things are being discussed but which are unlikely to result in immediate changes to Schema.org.

See also https://github.com/schemaorg/schemaorg/issues/2573