Dan Brickley

@jvandriel - to elaborate - I argued for this having "AMP" in the name, on the basis that the only possible implementation work I'm aware of is the (AMP-based) thing....

Schema (unlike the underlying RDF graph) has a notion for being explicit about URIs/URLs as strings, i.e. https://schema.org/URL (HTML5 / whatwg pushed everyone to go back to URL instead of...

An update on this. Firstly, I appreciate and share the desire for migration towards https everywhere. During the v12 launch we did initially switch the entire context to use a...

@jaygray0919 et al., can I suggest a different framing of the situation? Schema.org has long expressed a few things that made sense in 2011, when optimizing for ease of adoption...

To contextualize this proposal more explicitly, it is a proposal from Google based on our experience with existing product features that consume /VideoObject and [/Action markup](https://webschemas.org/docs/actions.html) for media content. As...

This is a reasonable question. Frankly it is a bit of a hack currently. JSON-LD forces schema.org to make claims about its properties that are a bit alien to our...

My sense is that the adoption of these schemas in *consuming applications* (search or other) has been disappointing. I would encourage you to be guided by the documentation from search...

Ok it seems we can't control issue creation besides turning it off entirely, since this is a publicly visible repository. I am looking into setting up issue templates and setting...

@smrgeoinfo actually that route didn't work well for us; we tried this with the notion of named extensions (bib, auto, etc.) but we found time and time over that all...

I have created https://github.com/schemaorg/suggestions-questions-brainstorming and will transfer issues there, leaving this repo for things that are expected to get addressed. The mailing list is also not a great forum for...