Skip to content

Commit 281a2cb

Browse files
committed
SourgeForce -> SourceForce
Signed-off-by: Arthit Suriyawongkul <[email protected]>
1 parent b193d66 commit 281a2cb

File tree

2 files changed

+1
-3
lines changed

2 files changed

+1
-3
lines changed

content/crosswalk/trove.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,6 @@ title: "Crosswalk for Trove Software Map"
33
image: "/img/sourceforge.png"
44
---
55

6-
[Trove Software Map](https://sourceforge.net/p/easyhtml5/tracinst/Software%20Map%20and%20Trove/#what-is-trove). Trove is the system used by SourgeForce.net to classify software projects.
7-
6+
[Trove Software Map](https://sourceforge.net/p/easyhtml5/tracinst/Software%20Map%20and%20Trove/#what-is-trove). Trove is the system used by SourceForce.net to classify software projects.
87

98
{{< crosswalk name="Trove Software Map" >}}

content/developer-guide.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,6 @@ An example usage of the CodeMeta document is for the author of research software
4747

4848
The producer of an CodeMeta Document, i.e. the creators of the software, must use the JSON names from the CodeMeta context file. The consumer of the CodeMeta Document can use these same JSON names from the CodeMeta Document for any necessary processing tasks.
4949

50-
As an alternative to using the producer supplied JSON names, the consumer can use the [JSON-LD API](https://www.w3.org/TR/json-ld-api/) to translate the JSON names to their own local JSON names that may be in use by their local processing scripts. This is done by first using the JSON-LD *expand* function that replaces each JSON name in the CodeMeta Document with it's corresponding IRI from the CodeMeta context file. For example, the producer's CodeMeta Document may contain the following line:
5150
As an alternative to using the producer supplied JSON names, the consumer can use the [JSON-LD API](https://www.w3.org/TR/json-ld-api/) to translate the JSON names to their own local JSON names that may be in use by their local processing scripts. This is done by first using the JSON-LD *expand* function that replaces each JSON name in the CodeMeta Document with it's corresponding IRI from the CodeMeta context file. For example, the producer's CodeMeta Document may contain the following line:
5251

5352
```json

0 commit comments

Comments
 (0)