Update metadata reference #162
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for open-terms-archive-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
MattiSG
reviewed
Feb 22, 2025
There was a problem hiding this comment.
How does relate to OpenTermsArchive/engine#1139? Is it generated from it?
| type="array of entity objects" | ||
| description="Entity object, see [Entity](#entity) section." | ||
| type="object" | ||
| description="Map of organizations involved in the collection's governance, with organization names as keys governance object, see [Governance](#governance) section." |
There was a problem hiding this comment.
Some words seem to be missing here 🙂
There was a problem hiding this comment.
Sorry for not having been more explicit. I don't understand this part:
with organization names as keys governance object
| {{< configOption | ||
| name="i18n" | ||
| type="object" | ||
| description="Internationalization of any of the Metadata properties (except i18n itself) for different language codes" |
There was a problem hiding this comment.
This works but is not very clear. Maybe an example would help? 🙂
| @@ -17,174 +17,187 @@ As an example, see the [complete metadata file](https://github.com/OpenTermsArch | |||
| name="id" | |||
| type="string" | |||
| description="Unique identifier derived from name (acronyms, dash-separated)." | |||
| example="`pga`" | |||
| example="pga" | |||
There was a problem hiding this comment.
Why do we take pga as an example, which is a third-party that we don't control, instead of demo that is here to that end?
| allowedValues="`host`, `administrator`, `curator`, `maintainer`, `sponsor`" | ||
| required=true | ||
| example="[host, administrator]" | ||
| required=false |
Ndpnt
force-pushed
the
update-metadata-specs
branch
from
10c54a5 to
a3b4401
Compare
MattiSG
approved these changes
Mar 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.