Closed nissimsan closed 5 months ago
Tagging @colugo ^
Hey @nissimsan Are you saying it's hard to interpret the content of that page, or that it's difficult to link to anchors on that page?
Or something else ;)
Although now having read the issue title, I understand a little more ;)
I can manually add the YAML (although JSON would seem more natural, no?) now, and can look into having it automatically updated in the future.
I've manually added the schema as YAML. It will not automatically update, and so runs the risk of becoming stale. Still, take a look and see if it addresses your concerns, and I can look into having Jargon auto-populate the up-to-date schema as part of the standard readme functionality.
Great, @colugo, thanks a bunch! That's precisely what I was aiming for. This makes it much more tangible.
Ultimately we probably want to include that YAML on https://uncefact.github.io/spec-untp/docs/specification/DigitalProductPassport at some point. Maybe. But that's for later - let's focus on the data modelling for now.
Cheers!
Linking to https://jargon.sh/user/unece/ConformityCredential/v/working/artefacts/readme/render is difficult to interpret