From df4400a8a8b16b7ba7d8007b65a952c6deac5301 Mon Sep 17 00:00:00 2001 From: Melissa Draper Date: Mon, 31 Aug 2026 21:25:06 -0700 Subject: [PATCH] Tidy context section of user guide (fix #128 3) Mention Crosswalks Also http->https where previously overlooked in this section. --- content/user-guide.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/content/user-guide.md b/content/user-guide.md index bcb9724..476784f 100644 --- a/content/user-guide.md +++ b/content/user-guide.md @@ -290,18 +290,24 @@ Every CodeMeta document must refer to the context file `codemeta.jsonld`, for example via a URL. This indicates that all terms in the document should be interpreted in the "context" of CodeMeta. -Most terms are chosen to match the equivalent terms in , -but CodeMeta provides a few additional terms not found in +Most terms are chosen to match the equivalent terms in , +but CodeMeta provides a few additional terms not found in which may be helpful for software projects. -CodeMeta also restricts the context to use only those +CodeMeta also restricts the context to use only those terms that are explicitly listed on the [terms](/terms) page. Users wanting to include additional terms may: -* Use the `schema:` prefix to define them as terms, (such +* Use the `schema:` prefix to define them as terms, (such as `"schema:releaseNotes"` [in this example](https://github.com/SciCodes/somef-core/blob/f0481b6f28166e1c5a95919d2767f1aaa5b3fa87/codemeta.json#L85)), or * Extend the context (see [the developer guide](/developer-guide)). +If you are migrating to CodeMeta from another metadata standard, refer to the +[Crosswalks page](/crosswalks) to see if a desired term has an equivalent +mapped. There are maps for many existing vocabularies in the directory, +including various package manifests. +{.tip} + The context file may be modified and updated in the future, if new JSON properties are added or existing ones modified.