Date
Call-in Information
Time: 10:00 am, Eastern Time (New York, GMT-04:00)
To join the online meeting:
https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09
Meeting ID: 843 7861 5572
Passcode: 556561
One tap mobile
+16699006833,,84378615572#,,,,*556561# US (San Jose)
+19292056099,,84378615572#,,,,*556561# US (New York)Dial by your location
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
+1 253 215 8782 US (Tacoma)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 346 248 7799 US (Houston)
877 853 5257 US Toll-free
888 475 4499 US Toll-free
Meeting ID: 843 7861 5572
Passcode: 556561
Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4
Slack
- https://vivo-project.slack.com
- Self-register at: http://bit.ly/vivo-slack
Attendees
Resources
Agenda
- Organization improvements
- Tickets - https://github.com/orgs/vivo-project/projects/2/views/1
- Ontology
- REST endpoint
- Action execution
- Testing strategy
- Blockers
- PRs - https://github.com/vivo-project/Vitro/pulls
- Documentation - VIVO Dynamic API
Notes
A short discussion about the issue with ContextPath, ServletPath and PathInfo. Action: William Welling will fix the issue and create a PR.
How and where should API documentation be published? Dragan Ivanovic : storing of YAML files in GitHub repository? YAML file for generic API specification might be there, but not sure anymore that other resource specific API documentation should be there. Kevin Day explained a solution to preserve those YAML files at Wiki. William Welling thinks that YAML files might be a specification for machines, and we should think about the format for human readable specification. Swagger is also a UI for experimenting with API. Can we use markdown files generated from YAML as a human readable specification? William Welling found an open source project dealing with this approach. Markdown files should be versioned in GitHub, YAML files probably not. Dragan Ivanovic: how to link markdown files with published VIVO releases? We need more investigation and discussion on this topic. Conclusion: let’s try to make generators for YAML files from RDF description of resource APIs in this sprint, and think about human readable specification after that. Action: William Welling will work on a generator for YAML files. Dragan Ivanovic ’s task for updating the ontology is a blocker for this task, William Welling will wait at least Monday (March 7th) to start with his task.
RCPEndpointTestIT is not executing if it is not explicitly stated in the maven command. William Welling explained that problem is suffix of the name (it is not ending with Test), and can be resolved by using the maven plugin, which means we should slightly change the pom file. Kevin Day suggested to change naming notation for integration test for resolving this issue, and the group accepted this solution. Action: Kevin Day will rename this file to RCPEndpointITest and create a PR.
Kevin Day noticed more compact notation for the ontology prefix use in Vitro ontologies, and suggested adoption of this notation to dynamic ontology. Dragan Ivanovic agreed, no objections from others. Dragan Ivanovic will try to update the ontology file in accordance with this suggestion and create a PR.
Veljko Maksimovic started implementation of N3Template operation, it should be used for triple update, creation and deletion. Different syntax for those three operations and probably different parameters are needed. Dragan Ivanovic was wondering whether we should sub-classing N3 Template to three separated classes (N3TemplateUpdate, N3TemplateCreation, N3TemplateDeletion) to make it easier and more intuitive for maintainers of dynamic actions’ RDFs. Conclusion: we need more expertise in the group for this decision, Veljko Maksimovic will investigate this in more detail and make consultation about this with Brian Lowe, before we decide which approach to use.
Status of the implementation. The most critical part is track 3 (executing of a dynamic action). The goal is to have fully functional execution of simple dynamic actions with one step at the end of the sprint. At the moment, there is no support for N3 templates, and SPARQL queries and Solr queries are not handling input/output data as expected. Veljko Maksimovic , Dragan Ivanovic and Georgy Litvinov will work on this track in the last week of the sprint.
Matthias Lühr is working on specification of a real use case defined as a dynamic action RDF. Not likely it will be executable at the end of this sprint, but will give us directions for making a specification for the next sprint.
