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
@@ -86,10 +86,10 @@ Tools will be created that assist in the generation of CodeMeta documents. For e
86
86
87
87
## Extending the CodeMeta Context
88
88
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:
@@ -98,7 +98,7 @@ This should be added at the top level of the document, indicating that this indi
98
98
99
99
```json
100
100
{
101
-
"@context": "https://w3id.org/codemeta/3.0",
101
+
"@context": "https://w3id.org/codemeta/3.1",
102
102
"@type": "SoftwareSourceCode",
103
103
"name": "CodemetaR",
104
104
@@ -117,7 +117,7 @@ JSON-LD operations can later *expand* this reference and *embed* the full inform
117
117
118
118
```json
119
119
{
120
-
"@context": "https://w3id.org/codemeta/3.0",
120
+
"@context": "https://w3id.org/codemeta/3.1",
121
121
"@type": "SoftwareSourceCode",
122
122
"name": "CodemetaR",
123
123
@@ -144,7 +144,7 @@ We saw before a simple (root) SoftwareSourceCode object:
144
144
145
145
```json
146
146
{
147
-
"@context": "https://w3id.org/codemeta/3.0",
147
+
"@context": "https://w3id.org/codemeta/3.1",
148
148
"@type": "SoftwareSourceCode",
149
149
"name": "CodemetaR"
150
150
}
@@ -154,7 +154,7 @@ and this root object can refer to other objects, for example recommend a Softwar
154
154
155
155
```json
156
156
{
157
-
"@context": "https://w3id.org/codemeta/3.0",
157
+
"@context": "https://w3id.org/codemeta/3.1",
158
158
"@type": "SoftwareSourceCode",
159
159
"name": "CodemetaR",
160
160
@@ -169,7 +169,7 @@ And you may in turn want to add attributes to this application:
169
169
170
170
```json
171
171
{
172
-
"@context": "https://w3id.org/codemeta/3.0",
172
+
"@context": "https://w3id.org/codemeta/3.1",
173
173
"@type": "SoftwareSourceCode",
174
174
"name": "CodemetaR",
175
175
@@ -191,7 +191,7 @@ For example, the above code is not equivalent to:
191
191
192
192
```json
193
193
{
194
-
"@context": "https://w3id.org/codemeta/3.0",
194
+
"@context": "https://w3id.org/codemeta/3.1",
195
195
"@type": "SoftwareSourceCode",
196
196
"name": "CodemetaR",
197
197
@@ -219,7 +219,7 @@ The CodeMeta GitHub repository defines tags to allow specific versions of a file
219
219
appropriate context file, e.g.
220
220
221
221
```json
222
-
"@context": "https://w3id.org/codemeta/3.0"
222
+
"@context": "https://w3id.org/codemeta/3.1"
223
223
```
224
224
225
225
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