PyLD VS custom-elements-manifest

3) Things I would need to refresh: JSON-LD (This is actually really useful): https://json-ld.org/

Some documentation for you OP: - RDFa. - JSON-LD doesn't have to be in HTML. It's just a specification built on JSON to represent RDF data. Also, from experience, Turtle) is more popular - If you want to dig into what defining semantic vocabularies (ontologies) entails, read on RDF, RDFS, and OWL2.

Schema markup can be added to a web page using the JSON-LD format, which is a structured data format that is supported by Yoast SEO.

It's a big long, so the response is at the bottom in Appendix A. The format is JSON for Linking Data, or JSON-LD.

So it can be tedious to create all the entities needed for your project and then serialize / deserialize the data in JSON-LD format.

The Web Components Community Group is developing such a format to describe the types of components here: https://github.com/webcomponents/custom-elements-manifest

People have already built tools that generate wrappers based on it.

TL;DR: A Custom Elements Manifest is a JSON file that contains all metadata about the custom elements in your project. You can read all about it here.

Custom Elements Manifest is a file format that describes the custom elements in your project. This format will allow tooling and IDEs to give rich information about the custom elements in a given project. A custom-elements.json contains metadata about the custom elements in your project; their properties, methods, attributes, inheritance, slots, CSS Shadow Parts, CSS custom properties, and a modules exports. If you're interested in following the specification of the schema, or contributing to it, you can find the repository here: webcomponents/custom-elements-manifest.