CSL-JSON as JSON-LD

1

Greetings,

Somewhere, (unfortunately I can’t remember where it was, maybe github, maye here) I read a CSL team discussion about the need to indicate in a CSL-JSON file which version of CSL the JSON file was representing. I’m wondering if anyone has suggested using JSON-LD “dialect” for the JSON file. If this were used then the @context could point to the name space of the version of the CSL spec used in the file. Also the @language syntax might be useful in expressing the language of a field without requiring an array or a second field. (I was in a discussion on this point with @bwiernik on github. Maybe there are other reasons to not go with JSON-LD but I thought maybe it might be worth a mention if it had not been mentioned before.

see: JSON-LD 1.1
see also: https://json-ld.org/

1 Like
2

This would be my suggestion. Zotero doesn’t yet have a JSON-LD translator, but it’s in the works.

2 Likes
3

That is really encouraging — that people are thinking about JSON-LD. I note that schema.org metadata is also in JSON-LD, will it be simple to convert the translator to also read schema.org metadata, or will this necessary be a second translator?

4

On the Zotero end the goal is to base the JSON-LD on schema to the maximum degree possible

5

Zotero doesn’t yet have a JSON-LD translator, but it’s in the works.

As a way of outputting Zotero data with a specific schema or a more general way of mapping LD ontologies?

Also, I just wanted to link this because it seems relevant though perhaps outdated:

6

Has that cross-schema analysis (Schema.org/csl-JSON) already been done?

7

Wow Lars that is a really interesting conversation.

8

Looking through my files, it looks like I made a start doing almost 2.5 years ago though it is missing a lot of things. I would be interested in working on this since I was planning to anyway.