Merge and test of sprint-18n into master: week of Feb 8th
1.12 release candidate #1: Feb 15st
Two week RC-1 testing period
For each subsequent RC-2 (if required), adding another two weeks to the schedule
Do we want the `war` install in 1.12? - VIVO-1443 - Decouple VIVO build from installation REOPENED
Next steps?
Still interest in this?
William Welling is still potentially interested in taking it over the line.
William - question, should I prioritize this over i18n work? Andrew- Yes please
End result should still meet the needs of people that are customizing VIVO
Won’t automatically move into Tomcat
Home directory management - will require the VIVO webapp to deploy the home directory during startup
Michel: Does the delivery of 1.12 depend on finishing this ticket? Andrew: Maybe. There is a lot of interest. Benjamin - optimistic that it will get done, but wouldn’t want it to be a blocker for 1.12
Andrew: Planning on a wrap up meeting on Friday. 11am perhaps to give people a little time to wrap things up
Andrew q to Georgy: Are Russian translations of interest for VIVO? Georgy: I have started it two years ago, a year ago started this project and have been waiting for a release to continue working on the translation. Will there be translations in ontologies, as well? Andrew: Will be documented. Will be looking for input. Re: ontologies documentation should also include this. Since annotation properties are stored in RDF. Brian: All that must be altered are 1. Properties files 2. Set of RDF get loaded for language-specific labels for ontology entities 3. Some templates (.ftl)
Sprint - progress is being made, people are self--assigning tickets
Inference mechanism: how to activate the mechanisms to infer universal and existential restrictions
Michel - would like to see in abox, in the individual
Brian - That’s an unimplemented feature. Could repurpose the simple reasoner but may not be a trivial amount of work.
Michel - JFact can make inferences on instances. But not implemented within VIVO.
Brian - originally there were no good solutions because memory was too limited to perform reasoning on the entire abox, but the tbox can sit in memory just fine.
Michel - what’s the shortest path forward? Brian - suck your whole abox into JFact (in memory), maybe servers can support this now. Could even alter RDF service so it talks directly to JFact.
MIchel - is there documentation on the current reasoner?
Brian - nothing up to date
We allow people to edit the tbox… that can have huge consequences in running production VIVOs, i.e. result in millions of new triples depending on how the reasoner works
Brian - are the inferences in the tbox? Were you expecting to actual individuals to get properties?