Add toucan metadata for project and credit batch

[wgwz]

Description

These additions are based on this spec.

The most important files to review are:

• ops/C03/project-metadata/C03-project-minimal-example.jsonld
  • the bare minimum that we'd expect to receive for a toucan created project
• ops/C03/project-metadata/C03-project-full-example.jsonld
  • an example of a fully-complete touch project metadata
• ops/C03/credit-batch-metadata/C03-batch-minimal-example.jsonld
  • what we expect the touch credit batch metadata to be. (at present we only have a minimal version of this)

If you know of more realistic data values for any of the examples above, please comment on those and let me know what they should be.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.

I have...

• [x] provided a link to the relevant issue or specification
• [x] reviewed "Files changed" and left comments if necessary

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

I have...

• [ ] confirmed all author checklist items have been addressed
• [ ] reviewed code correctness and readability
• [ ] reviewed documentation is accurate
• [ ] manually tested (if applicable)

[wgwz]

@clevinson @ryanchristo i know we've had some discussion about a versioning scheme for registry-standards. should we decide on a lightweight versioning scheme before going live with this toucan metadata?

[ryanchristo]

@clevinson @ryanchristo i know we've had some https://github.com/regen-network/regen-registry-standards/issues/20. should we decide on a lightweight versioning scheme before going live with this toucan metadata?

We can probably address this separately. :+1:

[wgwz]

@clevinson @ryanchristo i know we've had some #20. should we decide on a lightweight versioning scheme before going live with this toucan metadata?

We can probably address this separately. 👍

the reason i ask is because if we anticipate changes, and assuming there is a lot of metadata that gets created, and that later on we do want to add a version scheme for all the metadata, it could be a lot of work to go back and retroactively tag C03 metadata with the extra version field. but if we don't anticipate a lot of changes, or it's somehow easier than i realize to go back and fix this, maybe it's nbd (or maybe it's nbd for other reasons :-)