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
Copy file name to clipboardExpand all lines: content/developer-guide.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,10 +85,10 @@ Tools will be created that assist in the generation of CodeMeta documents. For e
85
85
86
86
## Extending the CodeMeta Context
87
87
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:
@@ -97,7 +97,7 @@ This should be added at the top level of the document, indicating that this indi
97
97
98
98
```json
99
99
{
100
-
"@context": "https://w3id.org/codemeta/3.0",
100
+
"@context": "https://w3id.org/codemeta/3.1",
101
101
"@type": "SoftwareSourceCode",
102
102
"name": "CodemetaR",
103
103
@@ -116,7 +116,7 @@ JSON-LD operations can later *expand* this reference and *embed* the full inform
116
116
117
117
```json
118
118
{
119
-
"@context": "https://w3id.org/codemeta/3.0",
119
+
"@context": "https://w3id.org/codemeta/3.1",
120
120
"@type": "SoftwareSourceCode",
121
121
"name": "CodemetaR",
122
122
@@ -143,7 +143,7 @@ We saw before a simple (root) SoftwareSourceCode object:
143
143
144
144
```json
145
145
{
146
-
"@context": "https://w3id.org/codemeta/3.0",
146
+
"@context": "https://w3id.org/codemeta/3.1",
147
147
"@type": "SoftwareSourceCode",
148
148
"name": "CodemetaR"
149
149
}
@@ -153,7 +153,7 @@ and this root object can refer to other objects, for example recommend a Softwar
153
153
154
154
```json
155
155
{
156
-
"@context": "https://w3id.org/codemeta/3.0",
156
+
"@context": "https://w3id.org/codemeta/3.1",
157
157
"@type": "SoftwareSourceCode",
158
158
"name": "CodemetaR",
159
159
@@ -168,7 +168,7 @@ And you may in turn want to add attributes to this application:
168
168
169
169
```json
170
170
{
171
-
"@context": "https://w3id.org/codemeta/3.0",
171
+
"@context": "https://w3id.org/codemeta/3.1",
172
172
"@type": "SoftwareSourceCode",
173
173
"name": "CodemetaR",
174
174
@@ -190,7 +190,7 @@ For example, the above code is not equivalent to:
190
190
191
191
```json
192
192
{
193
-
"@context": "https://w3id.org/codemeta/3.0",
193
+
"@context": "https://w3id.org/codemeta/3.1",
194
194
"@type": "SoftwareSourceCode",
195
195
"name": "CodemetaR",
196
196
@@ -218,7 +218,7 @@ The CodeMeta GitHub repository defines tags to allow specific versions of a file
218
218
appropriate context file, e.g.
219
219
220
220
```json
221
-
"@context": "https://w3id.org/codemeta/3.0"
221
+
"@context": "https://w3id.org/codemeta/3.1"
222
222
```
223
223
224
224
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