...
- Questions/Issues/Pull requests/Announcements
- 6. German VIVO workshop - https://events.tib.eu/vivo-workshop-2022/programm/2022-06-15/
- VIVO 1.13.0 release candidate - Release Testing - 1.13.0
- The next sprint
- date
- May 30th - June 17th
- Registration
- link
- Six/Seven registered participants so far
- Infrastructure
- Wiki page - Sprint - Dynamic API based on an ontology 2
- Slack channel created
- Project board
- We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
- but extend it with new issues (features, bugs)
- We will continue using this Project board - https://github.com/orgs/vivo-project/projects/2
- Starting point
- backend
- https://github.com/vivo-project/Vitro/tree/sprint-dynapi-2022-feb-staging
- will be renamed to dynamic-api
- https://github.com/vivo-project/Vitro/tree/sprint-dynapi-2022-feb
- wouldn't be used
- https://github.com/vivo-project/Vitro/tree/sprint-dynapi-2022-feb-staging
- frontend
- https://github.com/vivo-project/Vitro-angular/tree/dynapi-2022
- https://github.com/vivo-project/Vitro-angular/tree/dynapi-2022-staging
- backend
- Cleaning up not completed work at previous sprint
- https://github.com/vivo-project/Vitro/pull/285
- GET all and GET one - two dynamic actions or one ?
- https://github.com/vivo-project/Vitro/pull/286
- deletion and modification
- https://github.com/vivo-project/Vitro/pull/287
- Transforming xml notation of Dynamic API ontology to turtle/n3 notation
- Introducing new jena model for dynamic actions
- Cleaning up issues at https://github.com/orgs/vivo-project/projects/2/views/1
- https://github.com/vivo-project/Vitro/pull/285
- Tracks
- Ontology
- RDF representation of dynamic actions and resourceAPIs
- Binding
- Binding to Java objects representation
- Execution
- Execution of a dynamic action
- RCP Endpoint
- REST Endpoint
- Security
- Definition of dynamic action roles
- Authentication (endpoint and UI)
- Authorization
- JWT
- Do we need OAuth2 or OpenID Connect ???
- The ontology - link
- Validation
- syntax,
- over the ontology,
- generic SHACL rules for all dynamic actions
- custom SHACL rules for specific dynamic actions ???
- UI for running a dynamic action
- Angular & Angular Material
Some notes regarding angular from William Welling .
- I would recommend against using a openapi specification generator
- it likely does not take into consideration angular universal for SEO, central state management, or i18n
- it is not likely to be a long lived dependency, popular, or actually work well with the dynamism of custom actions
- choose between the server side module (both express and angular universal)
- consider a central state management up front
- choose i18n library (important to know whether we want runtime or build time i18n)
- adopt a style guide and have it enforced using linting
- have github action check code styles
- protect main branch against style guide violations
- incorporate best practices and have test coverage in initial commit
- have github action that performs code coverage
- protect main branch for code coverage decrease
- I would recommend against using a openapi specification generator
- CRUD operations for custom actions
- UI for management of custom actions
- Exploitation
- Ontology
- date
...