You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instructions for [using the CodeMeta Generator](create) are available.
24
+
Instructions for [using the CodeMeta Generator](/create) are available.
25
25
26
-
A _*beta*_ version of an automatic generator is also linked on that page.
26
+
[A _*beta*_ version of an automatic generator](https://autocodemeta.linkeddata.es/)
27
+
is also available.
27
28
28
29
Other utilities that can help with generating `codemeta.json` files are
29
-
listed on the [tools page](tools).
30
+
listed on the [tools page](/tools).
30
31
31
32
### Testing a CodeMeta instance file
32
33
@@ -131,7 +132,7 @@ The JSON-LD `@type` keyword associates a JSON value or object with a well
131
132
known type. In the previous example, the statement `"@type":"Person"`
132
133
associates the `author` object with `http://schema.org/Person`. The
133
134
`@type` for any property which specifies a node (JSON object) should be
134
-
provided. The `Type` column of [the terms page](/terms/) indicates the
135
+
provided. The `Type` column of [the terms page](/terms) indicates the
135
136
options appropriate for each term.
136
137
137
138
The `author` JSON object illustrates the use of the JSON-LD keyword `@id`,
@@ -294,12 +295,12 @@ but CodeMeta provides a few additional terms not found in <http://schema.org>
294
295
which may be helpful for software projects.
295
296
296
297
CodeMeta also restricts the context to use only those <http://schema.org>
297
-
terms that are explicitly listed on the [terms](/terms/) page. Users wanting
298
+
terms that are explicitly listed on the [terms](/terms) page. Users wanting
298
299
to include additional terms may:
299
300
300
301
* Use the `schema:` prefix to define them as <http://schema.org> terms, (such
301
302
as `"schema:releaseNotes"`[in this example](https://github.com/SciCodes/somef-core/blob/f0481b6f28166e1c5a95919d2767f1aaa5b3fa87/codemeta.json#L85)), or
302
-
* Extend the context (see [the developer guide](/developer-guide/)).
303
+
* Extend the context (see [the developer guide](/developer-guide)).
303
304
304
305
The context file may be modified and updated in the future, if new JSON
305
306
properties are added or existing ones modified.
@@ -463,7 +464,7 @@ providing this link.
463
464
464
465
### Organizations
465
466
466
-
The properties listed in the [terms](terms) tables with a type `Organization`
467
+
The properties listed in the [terms](/terms) tables with a type `Organization`
467
468
can list one or more organizations. They have the `type` value of
468
469
`Organization`.
469
470
@@ -473,7 +474,7 @@ has with various organizations. Like the `author` property, the properties
473
474
can contain values, or an array of objects with those same values for multiple
474
475
affiliations.
475
476
476
-
The [second example in the "People" section](#people) contains a
477
+
The [second example in the "People" section](/user-guide#people) contains a
477
478
use of the affiliation property, with `Organization` as its type.
478
479
479
480
## Describing the Software
@@ -487,7 +488,7 @@ representing dynamic information such as `version` and `authors` should be
487
488
updated as the software changes for the document to be most useful.
488
489
489
490
Useful properties include the ones in the example in the next section. Refer
490
-
to the [terms](terms) page for all CodeMeta properties.
491
+
to the [terms](/terms) page for all CodeMeta properties.
0 commit comments