Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion content/jsonld.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,15 @@ CodeMeta uses JSON-LD to represent and translate between software metadata forma

## The JSON-LD Context File

The current codemeta context file can be found at [![DOI](https://img.shields.io/badge/doi%3A-10.5063%2FSCHEMA%2FCODEMETA--2.0-blue.svg)](https://doi.org/10.5063/schema/codemeta-2.0)
The current codemeta context file can be used from <https://w3id.org/codemeta/3.0> -- note that browsers will redirect using _content negotiation_ to a HTML page, while JSON-LD processors will get the JSON-LD context.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like content negotiation no longer works.

A browser also gets the context file.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @dgarijo

we're really cursed with these links -_-

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, it works for https://w3id.org/codemeta/ but not for the versions. I will look into this. Apologies.

I would also like the terms to resolve, which need a special redirection. Been trying to get to this for a while. I will assume the id will be something like https://w3id.org/codemeta/X.X/TERM

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw, this will not affect the release, but I will try to have it working this week


### Released versions

* <https://w3id.org/codemeta/3.0>
* <https://doi.org/10.5063/schema/codemeta-2.0>
* <https://doi.org/10.5063/schema/codemeta-1.0>

### CodeMeta terms

CodeMeta properties are built on and extend software properties from <https://schema.org>. A list of all properties provided by the current CodeMeta `context` file can be found on the [terms](/terms) page. Here's an example [codemeta.json file](https://github.com/codemeta/codemetar/blob/master/codemeta.json) for the `codemetar` R package.

Expand Down
6 changes: 6 additions & 0 deletions content/terms.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,9 @@ library("readr")
library("dplyr")
```

* Permalink: <https://w3id.org/codemeta/3.0>
* CodeMeta version: 3.0

## Terms from Schema.org

Recognized properties for CodeMeta `SoftwareSourceCode` and `SoftwareApplication` includes the following terms from <https://schema.org>. These terms are part of the CodeMeta specification and can be used without any prefix.
Expand All @@ -35,6 +38,9 @@ knitr::kable("html", table.attr="class=\"table table-striped\"")

The CodeMeta project also introduces the following additional properties, which lack clear equivalents in <https://schema.org> but can play an important role in software metadata records covered by the CodeMeta crosswalk.

* Namespace: <https://codemeta.github.io/terms/>
- **Warning**: This namespace will change to be w3id-based for CodeMeta 4.0

```{r}
cw %>%
filter(grepl("codemeta:", `Parent Type`)) %>%
Expand Down