Hi Reto, all As suggested by you, I'll work directly on the reunited branch instead of creating another branch. This would be the new structure:
- rdf.api: contains current zz commons rdf api (modelling triples and graphs, mostly interfaces with minimal implementations) - rdf.impl: contains implementation of rdf.api, not more - sparql: contains current sparql query and update interface specifications as well as the implementation - parser - serializer - search (using query engine and sparql) - ontologies (as it is now) - schemagen (as it is now) - jaxrs.rdf.providers (as it is now) - utils: contains all utilities and helper classes (written in java or scala) Feedback and comments are welcome. Cheers Hasan On Fri, May 11, 2018 at 12:58 PM, Hasan <[email protected]> wrote: > Dear devs > > Reto and I met some months ago and discussed about refactoring clerezza > codes. > > I suggest to restructure as follows: > > - rdf.model: contains current zz commons rdf api (modelling triples and > graphs, mostly interfaces with minimal implementations) > > - rdf.impl: contains implementation of rdf.model, not more > > - sparql.model: contains current sparql query and update interface > specifications > > - sparql.impl: contains implementation of sparql.model > > - parser > > - serializer > > - search (using query engine) > > - ontologies (as it is now) > > - schemagen (as it is now) > > - jaxrs.rdf.providers (as it is now) > > - utils: contains all utilities and helper classes (written in java or > scala) > > > I'll create a new branch called reunited-refactored which will in the end > merged to master when finished > > What do you think? > > Hasan >
