...
- Effective model writing
- SHACL based validation
- Angular cookie issues?
- Load/reload/unload RPC, REST Endpoints
- What should be provided as a result?
- Actions permission check extension PR
- Dynamic api models PR
- Store user info and provide in ModelWriter PR
Meeting notes
- Approach used in model writings (rdf-utils) are not effective, because they add data triple-to-triple. Problem with the other approach (transaction/SHIM?) could be, if you want to have one transaction in add and remove model, but the performance should be increased. Even changing the rdf-service interface we might have serialization somewhere in behind.
- You can assign SHACL validation to different pools. Idea was to encapsulate rules, and then extend it to specific task. Now validation works like this, if data is valid it will be written in a pool and in a store, if data is invalid it will be only written in a triplestore, but not in the pool. Probably, ideal would be to check the model/action (?) before trying or uploading it to store.
- Probably question to William Welling is it not a problem to use http-only cookie (that we have now in VIVO) future with Angular?
Because of quote: "An
HttpOnlycookie means that it's not available to scripting languages like JavaScript. So in JavaScript, there's absolutely no API available to get/set theHttpOnlyattribute of the cookie, as that would otherwise defeat the meaning ofHttpOnly."