Skip to content

Commit f8414e1

Browse files
committed
Update schema link to 3.1
Signed-off-by: Arthit Suriyawongkul <[email protected]>
1 parent b59c969 commit f8414e1

File tree

3 files changed

+12
-11
lines changed

3 files changed

+12
-11
lines changed

content/developer-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,10 +85,10 @@ Tools will be created that assist in the generation of CodeMeta documents. For e
8585

8686
## Extending the CodeMeta Context
8787

88-
CodeMeta explicitly defines the terms it uses from <http://schema.org>, rather than merely extending <http://schema.org> with a few additional terms. To use additional terms from <http://schema.org> not listed on the [terms page](/terms/) (or terms from any other context), you must extend your context appropriately. For instance, to combine CodeMeta (v3.0) with all terms available in schema.org, you would do:
88+
CodeMeta explicitly defines the terms it uses from <http://schema.org>, rather than merely extending <http://schema.org> with a few additional terms. To use additional terms from <http://schema.org> not listed on the [terms page](/terms/) (or terms from any other context), you must extend your context appropriately. For instance, to combine CodeMeta (v3.1) with all terms available in schema.org, you would do:
8989

9090
```json
91-
"@context": ["https://w3id.org/codemeta/3.0", "http://schema.org/"]
91+
"@context": ["https://w3id.org/codemeta/3.1", "http://schema.org/"]
9292
```
9393

9494
Note the default context should be listed last.

content/jsonld.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,11 @@ JSON-LD lead developer Manu Sporny explains how JSON-LD works in this short clip
99

1010
## The JSON-LD Context File
1111

12-
[![W3IDCodeMeta v3](https://img.shields.io/badge/W3ID-CodeMeta_v3-blue)](https://w3id.org/codemeta/3.0)
12+
[![Permanent Identifier](https://img.shields.io/badge/perma--id-https%3A%2F%2Fw3id.org%2Fcodemeta%2F3.1-blue.svg)](https://w3id.org/codemeta/3.1)
1313

1414
Context file of released versions:
1515

16+
- CodeMeta 3.1: <https://w3id.org/codemeta/3.1>
1617
- CodeMeta 3.0: <https://w3id.org/codemeta/3.0>
1718
- CodeMeta 2.0: <https://doi.org/10.5063/schema/codemeta-2.0>
1819
- CodeMeta 1.0: <https://doi.org/10.5063/schema/codemeta-1.0>

content/user-guide.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Here is an example of a basic `codemeta.json` that you can put at the root of a
1515

1616
```json
1717
{
18-
"@context": "https://w3id.org/codemeta/3.0",
18+
"@context": "https://w3id.org/codemeta/3.1",
1919
"type": "SoftwareSourceCode",
2020
"applicationCategory": "Biology",
2121
"codeRepository": "https://github.com/gem-pasteur/macsyfinder",
@@ -97,7 +97,7 @@ This should be added at the top level of the document, indicating that this indi
9797

9898
```json
9999
{
100-
"@context": "https://w3id.org/codemeta/3.0",
100+
"@context": "https://w3id.org/codemeta/3.1",
101101
"@type": "SoftwareSourceCode",
102102
"name": "CodemetaR",
103103

@@ -116,7 +116,7 @@ JSON-LD operations can later *expand* this reference and *embed* the full inform
116116

117117
```json
118118
{
119-
"@context": "https://w3id.org/codemeta/3.0",
119+
"@context": "https://w3id.org/codemeta/3.1",
120120
"@type": "SoftwareSourceCode",
121121
"name": "CodemetaR",
122122

@@ -143,7 +143,7 @@ We saw before a simple (root) SoftwareSourceCode object:
143143

144144
```json
145145
{
146-
"@context": "https://w3id.org/codemeta/3.0",
146+
"@context": "https://w3id.org/codemeta/3.1",
147147
"@type": "SoftwareSourceCode",
148148
"name": "CodemetaR"
149149
}
@@ -153,7 +153,7 @@ and this root object can refer to other objects, for example recommend a Softwar
153153

154154
```json
155155
{
156-
"@context": "https://w3id.org/codemeta/3.0",
156+
"@context": "https://w3id.org/codemeta/3.1",
157157
"@type": "SoftwareSourceCode",
158158
"name": "CodemetaR",
159159

@@ -168,7 +168,7 @@ And you may in turn want to add attributes to this application:
168168

169169
```json
170170
{
171-
"@context": "https://w3id.org/codemeta/3.0",
171+
"@context": "https://w3id.org/codemeta/3.1",
172172
"@type": "SoftwareSourceCode",
173173
"name": "CodemetaR",
174174

@@ -190,7 +190,7 @@ For example, the above code is not equivalent to:
190190

191191
```json
192192
{
193-
"@context": "https://w3id.org/codemeta/3.0",
193+
"@context": "https://w3id.org/codemeta/3.1",
194194
"@type": "SoftwareSourceCode",
195195
"name": "CodemetaR",
196196

@@ -218,7 +218,7 @@ The CodeMeta GitHub repository defines tags to allow specific versions of a file
218218
appropriate context file, e.g.
219219

220220
```json
221-
"@context": "https://w3id.org/codemeta/3.0"
221+
"@context": "https://w3id.org/codemeta/3.1"
222222
```
223223

224224
Release candidate versions may be referred to consistently using their [git tag](https://github.com/codemeta/codemeta/tags) for the raw version, e.g. <https://raw.githubusercontent.com/codemeta/codemeta/2.0-rc/codemeta.jsonld>. *Please do not refer to the raw GitHub URL for the master branch*, as this is subject to change and will not guarantee a stable metadata file.

0 commit comments

Comments
 (0)