Hi, > My overall list of things to solve before the branch is ready to be merged > into develop: > > * Should be the GeoSPARQL support optional (configuration, independent > artifact, etc)? > * Solve the permissions' issue regarding CREATE EXTENSION usage by a > regular db user. > * Upgrade script does not look be automatically triggered at boot time on > existing databases. > > From my side, besides those issues that we'll solve later during the > integration phase, regarding the implementation itself the project is > ready, legally and technically speaking. >
I'll be incorporated in CS department of University of Cuenca and we are using marmotta like framework LDP for our projects. We want to still developing new features. Then absolutely we could solve that issues. I’ve done the pull request and attached the patch file. > > >> >>> The question is wherever we make the upgrade scrips run only if the >>> extension is installed, or we just move the geosparql support to a separate >>> maven artifact. >>> >>> What other people would prefer? I think that PostGIS must be a prerequisite. We could validate that the script must be run just PostGIS is installed. So if PostGIS is prerequisite we solved the problem of user privileges. Cheers, Xavier Sumba.
