Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing comma in dspace.jsonld #4217

Closed
eschrewe opened this issue May 27, 2024 · 4 comments · Fixed by #4292
Closed

Missing comma in dspace.jsonld #4217

eschrewe opened this issue May 27, 2024 · 4 comments · Fixed by #4292
Assignees

Comments

@eschrewe
Copy link

Bug Report

Describe the Bug

The file mentioned above misses a comma in line 58, which results in a faulty syntax.

Expected Behavior

The content of the file should have a valid syntax.

Observed Behavior

The current file caused failures when you try to use it.

Possible Implementation

Add a comma at the end of line 58

@github-actions github-actions bot added the triage all new issues awaiting classification label May 27, 2024
Copy link

Thanks for your contribution 🔥 We will take a look asap 🚀

@ndr-brt
Copy link
Member

ndr-brt commented May 27, 2024

there's already an issue on the IDS repository: International-Data-Spaces-Association/ids-specification#263

@ndr-brt ndr-brt removed the triage all new issues awaiting classification label Jun 5, 2024
Copy link

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale Open for x days with no activity label Jun 20, 2024
@ndr-brt
Copy link
Member

ndr-brt commented Jun 20, 2024

Now it has been fixed, so we can update the cached file accordingly:
https://w3id.org/dspace/2024/1/context.json

@ndr-brt ndr-brt removed the stale Open for x days with no activity label Jun 20, 2024
@ndr-brt ndr-brt self-assigned this Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants