Validation and filter feature

There have been a number of issues reported (linked in #882) where it seems that user's data files have been corrupted. Some of these things should be fixed on the frontend, so that it makes sure invalid data is not sent. However, the backend should also check, e.g. by doing a RDF validation as suggested in #882, but we could also imagine SHACL validation, etc. If Inrupt becomes a large POD provider, it may also come with legal requirements.

Also, validation may not only be a boolean accept or error, but possibly also filtering to accept valid parts. For v.next, we need to have an architectural element that does this, but we may need to address parts of this problem already for 5.0.0.

Consider this a super-issue for discussing what should be in 5.0.0, and if we should try to make that reusable in v.next. Also, we may discuss if we do not attempt to solve it on the backend and refer to frontends to do it.

まず、#882 にリンクされているレポートと、RDF および SHACL のバリデーションに関する議論を読みます。バリデーションを frontend、backend、またはその両方のどこで行うべきかを明確にし、5.0.0 と v.next のそれぞれのスコープを定義します。再利用可能なアーキテクチャについて合意し、無効なデータを拒否またはフィルタリングするための要件が明確になれば完了です。