Schemaorg: Collect usability, clarity and technical debt issues for attention

Created on 2 Jun 2021 · 5Comments · Source: schemaorg/schemaorg

/cc #2884

We have a lot of issues here, many don't have easy answers but we need to make better progress in prioritizing and addressing what we can. I'm going to poll the mailing list and Twitter for input on priorities - addressing frustrations of the folk who work with schema.org daily, using this issue to track and triage.

Next Release Editing Queue cleanup + clarity

Source

danbri

Most helpful comment

+1 for better schema examples.

Regards,

Stephen Hamilton
@.*

Sent from mobile device

On 3 Jun 2021, at 11:29 am, Jarno van Driel @.*> wrote:

Well, since you asked:

2891 is an issue I'd like to see resolved since I find it problematic publishers have to keep repeating the same entity info on many pages just to satisfy Google's rich result requirements. Although this most likely is more an issue of how 1 markup consumer handles things as opposed to there not being a technical solution (we can refer to entities elsewhere by using (fragment) identifiers after all).

If we resolve this I'm pretty sure we'll make a lot of folks happy as it means a lot less work (= resource) to get markup implemented and checked for validity.

Beyond that I regularly hear people complain about schema.org's markup examples. More specifically the lack of these for many types as well the fact that many examples don't represent everyday things people are trying to create markup for.

And lastly it'd be wonderful if there would be a page showing a full list of properties (and their subproperties) pretty much like: https://schema.org/docs/full.html. Personally I've been using http://htmlpreview.github.io/?https://github.com/schemaorg/schemaorg/blob/main/data/releases/12.0/schema-all.html though it's a bit mweh and cumbersome to use when looking for properties.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

stephenhamiltonau on 3 Jun 2021

👍2

All 5 comments

IMHO Twitter is very cluttered. Recently completed a Stackoverflow survey - went well. Using a similar survey technique/service from the schema.org site might work well.

jaygray0919 on 2 Jun 2021

I've started a mail thread for now - a lot of folks (I think especially in the SEO world) join the list, and aren't generally Github users.

https://lists.w3.org/Archives/Public/public-schemaorg/2021Jun/0001.html

Maybe a more structured survey once we start to get a feel for the likely structure?

danbri on 2 Jun 2021

👍1

Well, since you asked:

2891 is an issue I'd like to see resolved since I find it problematic publishers have to keep repeating the same entity info on many pages just to satisfy Google's rich result requirements. Although this most likely is more an issue of how 1 consumer of markup handles things as opposed to there not being a technical solution (we can refer to entities elsewhere by using (fragment) identifiers after all).

If we resolve this I'm pretty sure we'll make a lot of folks happy as it means a lot less work (= resources) to get markup implemented and checked for validity.
Beyond that I regularly hear people complain about schema.org's markup examples. More specifically the lack of these for many types as well the fact that many examples don't represent everyday things people are trying to create markup for.
And lastly it'd be wonderful if there would be a page showing a full list of properties (and their subproperties) pretty much like: https://schema.org/docs/full.html. Personally I've been using http://htmlpreview.github.io/?https://github.com/schemaorg/schemaorg/blob/main/data/releases/12.0/schema-all.html#propaz though it's a bit mweh and cumbersome to use when looking for properties.

jvandriel on 3 Jun 2021

👍1

+1 for better schema examples.

Regards,

Stephen Hamilton
@.*

Sent from mobile device

On 3 Jun 2021, at 11:29 am, Jarno van Driel @.*> wrote:

Well, since you asked:

2891 is an issue I'd like to see resolved since I find it problematic publishers have to keep repeating the same entity info on many pages just to satisfy Google's rich result requirements. Although this most likely is more an issue of how 1 markup consumer handles things as opposed to there not being a technical solution (we can refer to entities elsewhere by using (fragment) identifiers after all).

If we resolve this I'm pretty sure we'll make a lot of folks happy as it means a lot less work (= resource) to get markup implemented and checked for validity.

Beyond that I regularly hear people complain about schema.org's markup examples. More specifically the lack of these for many types as well the fact that many examples don't represent everyday things people are trying to create markup for.

And lastly it'd be wonderful if there would be a page showing a full list of properties (and their subproperties) pretty much like: https://schema.org/docs/full.html. Personally I've been using http://htmlpreview.github.io/?https://github.com/schemaorg/schemaorg/blob/main/data/releases/12.0/schema-all.html though it's a bit mweh and cumbersome to use when looking for properties.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

stephenhamiltonau on 3 Jun 2021

👍2

An area where we have seen repeated confusion in Bioschemas is the use of publication to point to a PublicationEvent rather than a publication about the resource; the correct property to use is citation but in the research community this is often used as a term to point to someone else's paper on which you have built rather than your own paper about the work.

Perhaps some clear examples (and perhaps explanations of how not to use it) would help clear this up.