[jira] [Commented] (CLEREZZA-1026) Refactoring: api and api.impl

[Hasan (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLEREZZA-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476918#comment-16476918
 ] 

Hasan commented on CLEREZZA-1026:
-

[~reto], all

Should we keep current api classes as they are now or do you think it is better 
to move event and related classes out of this module and place them elsewhere, 
e.g., a top level module called event ? I tend to place them in a new top level 
module to make the api slim and contains the least needed for the 
implementation of a very simple rdf application.

> Refactoring: api and api.impl
> -
>
> Key: CLEREZZA-1026
> URL: https://issues.apache.org/jira/browse/CLEREZZA-1026
> Project: Clerezza
>  Issue Type: Improvement
>Reporter: Hasan
>Assignee: Hasan
>Priority: Major
> Fix For: 8
>
>
> api: modelling triples and graph
> api.impl: implementation of the model
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (CLEREZZA-1026) Refactoring: api and api.impl

[Hasan (JIRA)]

Hasan created CLEREZZA-1026:
---

 Summary: Refactoring: api and api.impl
 Key: CLEREZZA-1026
 URL: https://issues.apache.org/jira/browse/CLEREZZA-1026
 Project: Clerezza
  Issue Type: Improvement
Reporter: Hasan
Assignee: Hasan
 Fix For: 8


api: modelling triples and graph

api.impl: implementation of the model

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Refactoring clerezza

[Hasan]

There is another thing we can discuss, that I forgot to mention: the
TcProvier currently in core/access.
We have the following alternatives
1. A new module called dataset
2. As part of the api and api.impl

I tend to choose 1. If no objections, I'll continue with 1.

The search module might go as well into dataset, I think.

Cheers
Hasan

On Wed, May 16, 2018 at 8:05 AM, Hasan Hasan  wrote:

> Hi Reto, all
>
> Just to update:
> Current rdf/core is a single module that I would like to restructure and
> make the whole Clerezza flatter.
> Clerezza is about rdf, so I would like to remove the top level hierarchy
> rdf from the structure.
> Core stuffs will be moved to top level hierarchy and if not needed, we
> don't differentiate between core and not.
> Thus, this will result in the following modules:
> - api
> - api.impl (perhaps you can suggest a better name for this specific impl
> of the api)
> - sparql
> - representation: contains parser and serializer
> - search
> - ontologies
> - schemagen
> - jaxrs.rdf.providers
> - utils
>
> Thx for feedback
> Hasan
>
> On Sun, May 13, 2018 at 9:39 PM, Hasan Hasan 
> wrote:
>
>> 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  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
>>>
>>
>>
>

Re: Refactoring clerezza

[Hasan Hasan]

Hi Reto, all

Just to update:
Current rdf/core is a single module that I would like to restructure and
make the whole Clerezza flatter.
Clerezza is about rdf, so I would like to remove the top level hierarchy
rdf from the structure.
Core stuffs will be moved to top level hierarchy and if not needed, we
don't differentiate between core and not.
Thus, this will result in the following modules:
- api
- api.impl (perhaps you can suggest a better name for this specific impl of
the api)
- sparql
- representation: contains parser and serializer
- search
- ontologies
- schemagen
- jaxrs.rdf.providers
- utils

Thx for feedback
Hasan

On Sun, May 13, 2018 at 9:39 PM, Hasan Hasan  wrote:

> 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  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
>>
>
>