Thanks for describing this combination of JSON-LD and Markdown!
The JSON-LD Working Group at the W3C is currently rechartering in order to bring the YAML-LD specification onto the "recommendations" standardization track:
https://json-ld.github.io/yaml-ld/spec/
It would be interesting to see how implementing YAML-LD here might expand the horizons and reduce transformation steps.
As an example, instead of...
---
type: Article
schema: https://schema.org
...
---
One could use...
---
"@context": https://schema.org
type: Article
...
---
where the value of @context would support the full expression of JSON-LD's @context. It would also mean, that the YAML-LD in that front matter could be transformed into JSON and then immediately parsed as JSON-LD--without any additional reworking. That also means that the front matter could be converted to JSON and added as the value of an HTML data block (i.e. <script type="application/ld+json">{...}</script>) which simplifies feeding the output into search engines, NLWeb, etc.
Thanks again for exploring this combination!
Cheers,
🎩
Thanks for describing this combination of JSON-LD and Markdown!
The JSON-LD Working Group at the W3C is currently rechartering in order to bring the YAML-LD specification onto the "recommendations" standardization track:
https://json-ld.github.io/yaml-ld/spec/
It would be interesting to see how implementing YAML-LD here might expand the horizons and reduce transformation steps.
As an example, instead of...
One could use...
where the value of
@contextwould support the full expression of JSON-LD's@context. It would also mean, that the YAML-LD in that front matter could be transformed into JSON and then immediately parsed as JSON-LD--without any additional reworking. That also means that the front matter could be converted to JSON and added as the value of an HTML data block (i.e.<script type="application/ld+json">{...}</script>) which simplifies feeding the output into search engines, NLWeb, etc.Thanks again for exploring this combination!
Cheers,
🎩