Add Schema Support to WordPress Gallery shortcode

[bhubbard]

It would be nice to see the WordPress gallery shortcode support schema.

​https://schema.org/ImageGallery

[Compute]

+1 - I was not aware of that schema.

[jnylen0]

Why? (What are the benefits of supporting this?)

How? (What changes would need to be made? Are there BC implications?)

Are there reasons not to do this? For example:

• I suspect it would mean that the gallery shortcode has these extra features that aren't really supported in other shortcodes, which isn't great (something something xkcd something standards). It might be better to consider schema or programmatic support as part of a larger project (for example, editor blocks), but the benefits would have to be pretty clearly explained and ideally proven.

• Would we be adding (more) duplicate ways of doing the same thing, which is potentially confusing?

I don't have answers to these, just trying to ask questions that can help move the ticket forward.

[jnylen0]

Adding reporter-feedback to indicate that the ticket needs more info.

Also, the version field of a ticket should be set to the WP version where a feature or bug was first introduced. You can think of it as "version relevant since", and we should probably document this better. Going with 3.5 as the first version of the "modern" gallery shortcode ( ​ref).

[JakePT]

My reading of ​https://schema.org/ImageGallery is that it's used to mark up the page, not the gallery. Note that it doesn't have any useful properties for marking up individual images, or captions, or anything that a service could use for parsing the gallery in a meaningful way, and is a subtype of WebPage. I don't think marking up the output of the gallery shortcode with this item type would be the correct usage of it.

[bhubbard]

After reading the schema more closely, I believe you are right, it shouldn't be used.