Repository navigation
Validation of LD-files #882
Description
When posting triples as TTL, RDF+XML, JSON-LD, etc, I think we should do validation on the server. I don't think this should be to hard to implement, but the devils probably in the detail, so want to have a good discussion on this.
Also, I'm uncertain if this should be part of 5.0.0. or v.next. Any thoughts?
Activity
kjetilk commentedon Oct 23, 2018
I think it is clearly a part of the v.next architecture, but it seems to touch all the handlers in the current architecture.
akuckartz commentedon Oct 23, 2018
What happens when there is no validation?
kjetilk commentedon Oct 23, 2018
The server would respond with a
400. It is no replacement for client-side validation, but it is a last stand against breaking stuff.megoth commentedon Oct 24, 2018
I also think this would limit some of the issues that people have experienced (solid/solid#165, solid/solid#206, #826)
megoth commentedon Nov 14, 2018
I'm discontinuing my work on this until we have a broader consensus on validation in general (currently discussed in Validation and filter feature and Discourse).
I've pushed my work on the branch feature/simple-validation, in case it's interesting to continue at some point.
megoth commentedon Nov 14, 2018
After a discussion with @timbl, @kjetilk, and @rubensworks on this earlier today it seems that validation (i.e. to make sure that the Turtle syntax is valid) on the ACL-files might be a good compromise. If noone objects to this, I'll continue working on that tomorrow (it's should be almost done in that regard).
megoth commentedon Feb 4, 2019
This issue has been fixed, we implemented syntax validation for ACL files in #937