The assumption here is that a dashlist shape makes more sense for us, because BreadcrumbList seems to be intended for rendering in a webpage. It also is a more complicated structure than what we introduced for the C03 project metadata, and I think we are seeking some simplicity in our json-ld structures (while maintaining valid RDF).
This task is to convert our BreadcrumbList's to dashlist's, which probably makes sense in most places we've used it so far.
As part of https://github.com/regen-network/regen-registry-standards/pull/32 we added the following for the
approvedMethodologies
in the C03 project metadata:https://github.com/regen-network/regen-registry-standards/blob/kyle/add-toucan-metadata/ops/C03/project-metadata/C03-project-full-example.jsonld#L30-L38
This is slightly different than the other places we've used the
approvedMethodologies
field. I.e. see how we use aBreadcrumbList
here:https://github.com/regen-network/regen-registry-standards/blob/kyle/add-toucan-metadata/ops/C02/credit-class-metadata/C02-city-forest-credits-credit-class.jsonld#L48-L83
The assumption here is that a dashlist shape makes more sense for us, because BreadcrumbList seems to be intended for rendering in a webpage. It also is a more complicated structure than what we introduced for the C03 project metadata, and I think we are seeking some simplicity in our json-ld structures (while maintaining valid RDF).
This task is to convert our BreadcrumbList's to dashlist's, which probably makes sense in most places we've used it so far.