ERROR: Unexpected error at publish route: Unsupported JSON-LD version: 1.1

[CosmiCloud]

trafficstars

Issue description

The node will not lot me publish a json-ld dataset that has @version specified in the @context. I must delete the version from the context before publishing: delete latest_station_observations.data["@context"][1]["@version"]

Bumping the version to 1.0 still produces the error but it calls out version 1.0 instead.

Expected behavior

I publish the dataset from weather.gov with version included and the node does not error.

Actual behavior

I publish the dataset from weather.gov with version included and the node errors.

Steps to reproduce the problem

1. Run a fresh node and sqldb

2. Publish this file: weatherdata.zip

3. Node will error:

4. Publish this file (which is the same as the above but without the version included): weatherdata.zip

5. Node will NOT error, and the data set s published:

Specifications

• Node version: 6.0.0-beta.1.19
• Platform: Ubuntu 20.04
• Node wallet: 0xC3edFfF56E2BBf0B6439576938E0d8c213e0bEf6
• Node libp2p identity: QmPoKaAowLLS6cRrBUiB783hv9uqPzNhhU6TV5uJWnHwXT

Contact details

• Email:

Error logs

1. node.log

Disclaimer

Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].

[kotlarmilos]

Hi @CosmiCloud, good catch! We haven't test it with different versions. We will definitely investigate further and enable versions to be used in json-ld format

[CosmiCloud]

@kotlarmilos Still seeing this in phase 2 :)

[NZT48]

This issue is being closed as inactive due to the date of the last activity on it. If you believe this is still a problem, please create a new issue and confirm that it is reproducible in the current ot-node release version. We are working towards closing open issues that meet specific criteria and ask you to create a new one for those that that are truly bugs in current release. We'll be monitoring those issues so that they are properly managed.

Thank you, OriginTrail Team