Skip to content

Commit c05e413

Browse files
authored
Merge pull request #81 from bact/update-schema-3.1
Update schema link to 3.1
2 parents 3cb9de8 + f8414e1 commit c05e413

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
@@ -86,10 +86,10 @@ Tools will be created that assist in the generation of CodeMeta documents. For e
8686

8787
## Extending the CodeMeta Context
8888

89-
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:
89+
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:
9090

9191
```json
92-
"@context": ["https://w3id.org/codemeta/3.0", "http://schema.org/"]
92+
"@context": ["https://w3id.org/codemeta/3.1", "http://schema.org/"]
9393
```
9494

9595
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
@@ -10,10 +10,11 @@ JSON-LD lead developer Manu Sporny explains how JSON-LD works in this short clip
1010

1111
## The JSON-LD Context File
1212

13-
[![W3IDCodeMeta v3](https://img.shields.io/badge/W3ID-CodeMeta_v3-blue)](https://w3id.org/codemeta/3.0)
13+
[![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)
1414

1515
Context file of released versions:
1616

17+
- CodeMeta 3.1: <https://w3id.org/codemeta/3.1>
1718
- CodeMeta 3.0: <https://w3id.org/codemeta/3.0>
1819
- CodeMeta 2.0: <https://doi.org/10.5063/schema/codemeta-2.0>
1920
- 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
@@ -16,7 +16,7 @@ Here is an example of a basic `codemeta.json` that you can put at the root of a
1616

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

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

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

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

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

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

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

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

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

@@ -191,7 +191,7 @@ For example, the above code is not equivalent to:
191191

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

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

221221
```json
222-
"@context": "https://w3id.org/codemeta/3.0"
222+
"@context": "https://w3id.org/codemeta/3.1"
223223
```
224224

225225
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)