Re: [GSoC] LDP based on SPARQL, mid-term checkpoint

[Qihong Lin <co...@gmail.com>]

Dear Sergio,

I've just translated all of the methods into SPARQL implementations,
and committed the code. I'll watch the upstream, in case new methods
or modifications are coming. It's actually ahead of the original plan.

Thanks for sharing your opinions of my current work. In the next
weeks, I'll resolve the problems you pointed out (i.e. tests,
documentations, code abstractions and evaluations). Basically, I think
everything is going on well until now. I'll turn to you for help, if
there's any further question. Thanks a lot!

Cheers,
Qihong Lin


On Tue, Jun 24, 2014 at 8:32 PM, Sergio Fernández <wi...@apache.org> wrote:
> Hi Qihong Lin,
>
> it's the mid-point of the GSoC programme, so it's a good time to assess the
> state of the project. It looks close to the plan and I'd like you to
> (briefly) write-up how the project is going. Check you are getting what you
> want out of the project as well. It is not just code production. Is the rest
> of the plan looking right still?
>
> Looking on at the repository forked at github:
>
>   https://github.com/confidencesun/marmotta/tree/MARMOTTA-444
>
> besides the few comments I did on your commits, there are a few things I'd
> like to discuss:
>
> * Working plan: concrete details about how your work is actually following
> (or not) the proposed working plan.
>
> * Implementation feedback: which in the end may revert to the overall
> quality of the project. For instance, looking to the current status of your
> implementation http://s.apache.org/7mn I could expect that you should be
> able to propose the usage of an abstract base implementation with some
> commons things.
>
> * Method documentation: document how you translate the Sesame native call to
> SPARQL queries will help to maintain the alternative implementation
>
> * User documentation: how to launch Marmotta using your implementation,
> example requests, etc.
>
> * More testing: I know you are moving on a very unknown area, but the more
> tests you write the best for discovering issues (specially lateral effect of
> related code). The official LDP Test Suite would be a helpful resource.
>
> * Evaluation: for example, regarding performance: on the typical scenarios,
> do you have some figure in the deviation in comparison with the main
> implementation?
>
> And I think that's all...
>
> Remember that you can use the github wiki to write down whatever stuff you
> need. Documentation is always good.
>
> But so far my overall impression for this checkpoint is that you are in the
> right path.
>
> Thanks.
>
> Cheers,
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 660 2747 925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co

Re: [GSoC] less 1 month left

[Sergio Fernández <wi...@apache.org>]

Hi Qihong Lin,

On 31/07/14 12:18, Qihong Lin wrote:
> I'm sorry I can't understand you questions. It's appreciated if you
> can help me clarify these:

I just pretend to make you stater to think about the conclusions of the 
project now that the closing date is coming.

> 1) If what changes in the new alternative CDI service is just the
> invocations to the RepositoryConnection (I'd need to check the diff to
> really assert that), would it still make sense to you to provide an
> alternative CDIservice?
> What do you mean by the "new alternative CDI service", and "an
> alternative CDIservice"? I'm now translating the CDI service
> (LdpServiceImpl) into SPARQL implementation. If anything changes, I
> can translate it accordingly. Is that enough?

Yes, for the project is enough, that was the goal.

The question is I'd like to evaluate not only what you did, but what you 
have learned too. So for the conclusions you could write something 
discussing such aspects: that "was the right approach because...", "not 
sure because both CDI service duplicate too much business code", etc.

> 2)  Or would be more maintainable to move the translation into an
> RepositoryConnection wrapper or something like that?
> What's "an RepositoryConnection wrapper"? Why do we need that (i.e.
> why more maintainable )? Can you show me an example? Thanks!

I'm not saying that's valid. Probably not. Just trying to trigger your 
inquisitiveness ;-)

Not sure if you follow me. If you want, we can have a spype call 
(sergio.fernandez.lopez) before Tuesday to talk about that.

Thanks!

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co

Re: [GSoC] less 1 month left

[Qihong Lin <co...@gmail.com>]

Dear Sergio,

I'm sorry I can't understand you questions. It's appreciated if you
can help me clarify these:

1) If what changes in the new alternative CDI service is just the
invocations to the RepositoryConnection (I'd need to check the diff to
really assert that), would it still make sense to you to provide an
alternative CDIservice?
What do you mean by the "new alternative CDI service", and "an
alternative CDIservice"? I'm now translating the CDI service
(LdpServiceImpl) into SPARQL implementation. If anything changes, I
can translate it accordingly. Is that enough?

2)  Or would be more maintainable to move the translation into an
RepositoryConnection wrapper or something like that?
What's "an RepositoryConnection wrapper"? Why do we need that (i.e.
why more maintainable )? Can you show me an example? Thanks!

Best regards,
Qihong Lin


On Mon, Jul 28, 2014 at 9:00 PM, Sergio Fernández <wi...@apache.org> wrote:
> Dear Qihong Lin,
>
>
> On 27/07/14 12:41, Qihong Lin wrote:
>>
>> I'm making documentation in git wiki:
>> [1]
>> https://github.com/confidencesun/marmotta/wiki/GSoC-2014-Project-(MARMOTTA-444)
>> [2] https://github.com/confidencesun/marmotta/wiki/Developer-Documentation
>> [3] https://github.com/confidencesun/marmotta/wiki/User-Documentation
>
>
> Perfect. Try to evolve as much as possible that documentation to start to
> prepare the final report.
>
> A conclusions chapter from your since would be nice. Think about what
> aspects are interesting to discuss.
>
> Taking a quick look to dev documentation, there is one aspect I'd like to
> hear from you about the mapping of method. If what changes in the new
> alternative CDI service is just the invocations to the RepositoryConnection
> (I'd need to check the diff to really assert that), would it still make
> sense to you to provide an alternative CDIservice? Or would be more
> maintainable to move the translation into an RepositoryConnection wrapper or
> something like that? Think about that, write down your conclusions, and
> ideally provide a proof-of-concept implementation.
>
>
>> Currently, the SPARQL implementation is up to date to the ldp and
>> develop branches. I'll make the translations soon after any new
>> changes from upstreams, and report to you in time.
>
>
> Probably we'll finally do it early next week. I'll keep you informed.
>
>
> Cheers,
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 660 2747 925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co

Re: [GSoC] less 1 month left

[Sergio Fernández <wi...@apache.org>]

Dear Qihong Lin,

On 27/07/14 12:41, Qihong Lin wrote:
> I'm making documentation in git wiki:
> [1] https://github.com/confidencesun/marmotta/wiki/GSoC-2014-Project-(MARMOTTA-444)
> [2] https://github.com/confidencesun/marmotta/wiki/Developer-Documentation
> [3] https://github.com/confidencesun/marmotta/wiki/User-Documentation

Perfect. Try to evolve as much as possible that documentation to start 
to prepare the final report.

A conclusions chapter from your since would be nice. Think about what 
aspects are interesting to discuss.

Taking a quick look to dev documentation, there is one aspect I'd like 
to hear from you about the mapping of method. If what changes in the new 
alternative CDI service is just the invocations to the 
RepositoryConnection (I'd need to check the diff to really assert that), 
would it still make sense to you to provide an alternative CDIservice? 
Or would be more maintainable to move the translation into an 
RepositoryConnection wrapper or something like that? Think about that, 
write down your conclusions, and ideally provide a proof-of-concept 
implementation.

> Currently, the SPARQL implementation is up to date to the ldp and
> develop branches. I'll make the translations soon after any new
> changes from upstreams, and report to you in time.

Probably we'll finally do it early next week. I'll keep you informed.

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co

Re: [GSoC] less 1 month left

[Qihong Lin <co...@gmail.com>]

Dear Sergio,

I'm making documentation in git wiki:
[1] https://github.com/confidencesun/marmotta/wiki/GSoC-2014-Project-(MARMOTTA-444)
[2] https://github.com/confidencesun/marmotta/wiki/Developer-Documentation
[3] https://github.com/confidencesun/marmotta/wiki/User-Documentation

Currently, the SPARQL implementation is up to date to the ldp and
develop branches. I'll make the translations soon after any new
changes from upstreams, and report to you in time.

Best regards,
Qihong Lin


On Thu, Jul 24, 2014 at 9:59 PM, Sergio Fernández <wi...@apache.org> wrote:
> Dear Qihong Lin,
>
>
> On 24/07/14 14:06, Qihong Lin wrote:
>>
>> Thanks for your reminder! I've been watching the marmotta's branch
>> refs/heads/develop (not much changes related to ldp service these
>> days). As you pointed out, I just checked the ldp branch and updated
>> my LdpServiceSPARQLImpl accordingly [1]. Now both LdpServiceSPARQLImpl
>> and LdpServiceImpl passed my unit tests as expected.
>
>
> It'd be great if you can report the current status of the SPARQL
> implementation, as well as periodically report your progress.
>
>
>> I'll keep a close eye on both the develop and ldp branches in the
>> coming weeks. With previous experience in the first half part of the
>> project, I think it's not difficult to translate the remaining changes
>> to the SPARQL implementations. I'll check and translate the changes
>> everyday. After the GSoC project, I can also offer contribution
>> related to this work.
>
>
> That'd be great! That's one of the goals of GSoC is not always explored by
> the student. Hope you can continue collaborating with us after the program
> ends.
>
>
>> In the meanwhile, I'll work on the documentations and the tests
>> (performance, w3c test suite, etc), as you mentioned in the mid-term
>> evaluation. I've been studying JMeter, TestNG and Rest-Assured. I'll
>> have a try in the next week and keep you posted.
>
>
> Where are you documenting all your stuff? As I explained you, I'd appreciate
> to have access to it in advance.
>
>
> Cheers,
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 660 2747 925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co

Re: [GSoC] less 1 month left

[Sergio Fernández <wi...@apache.org>]

Dear Qihong Lin,

On 24/07/14 14:06, Qihong Lin wrote:
> Thanks for your reminder! I've been watching the marmotta's branch
> refs/heads/develop (not much changes related to ldp service these
> days). As you pointed out, I just checked the ldp branch and updated
> my LdpServiceSPARQLImpl accordingly [1]. Now both LdpServiceSPARQLImpl
> and LdpServiceImpl passed my unit tests as expected.

It'd be great if you can report the current status of the SPARQL 
implementation, as well as periodically report your progress.

> I'll keep a close eye on both the develop and ldp branches in the
> coming weeks. With previous experience in the first half part of the
> project, I think it's not difficult to translate the remaining changes
> to the SPARQL implementations. I'll check and translate the changes
> everyday. After the GSoC project, I can also offer contribution
> related to this work.

That'd be great! That's one of the goals of GSoC is not always explored 
by the student. Hope you can continue collaborating with us after the 
program ends.

> In the meanwhile, I'll work on the documentations and the tests
> (performance, w3c test suite, etc), as you mentioned in the mid-term
> evaluation. I've been studying JMeter, TestNG and Rest-Assured. I'll
> have a try in the next week and keep you posted.

Where are you documenting all your stuff? As I explained you, I'd 
appreciate to have access to it in advance.

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co

Re: [GSoC] less 1 month left

[Qihong Lin <co...@gmail.com>]

Dear Sergio,

Thanks for your reminder! I've been watching the marmotta's branch
refs/heads/develop (not much changes related to ldp service these
days). As you pointed out, I just checked the ldp branch and updated
my LdpServiceSPARQLImpl accordingly [1]. Now both LdpServiceSPARQLImpl
and LdpServiceImpl passed my unit tests as expected.

I'll keep a close eye on both the develop and ldp branches in the
coming weeks. With previous experience in the first half part of the
project, I think it's not difficult to translate the remaining changes
to the SPARQL implementations. I'll check and translate the changes
everyday. After the GSoC project, I can also offer contribution
related to this work.

In the meanwhile, I'll work on the documentations and the tests
(performance, w3c test suite, etc), as you mentioned in the mid-term
evaluation. I've been studying JMeter, TestNG and Rest-Assured. I'll
have a try in the next week and keep you posted.


Best,
Qihong Lin

[1] https://github.com/confidencesun/marmotta/commit/cff11e06c0c13bd8d8a10fea5e9eccf8d31f86ba

On Wed, Jul 23, 2014 at 3:45 PM, Sergio Fernández <wi...@apache.org> wrote:
> According the official time-line:
>
> http://www.google-melange.com/gsoc/events/google/gsoc2014
>
> August 18th is the official 'pencils down' date for GSoC this year.
>
> Please, Qihong Lin, remember to continue pushing hard. I did not see some
> much activity or reporting in the last weeks, and you still have so much to
> do for achieving the goals of the project.
>
> We had been working at the ldp branch, fixing details discovered by the W3C
> test suite. They mainly affect the web service layer, but I think we
> extended the service api with some new methods. Next week Jakob and myself
> we plan to continue working on that, with the idea of merging stable changes
> back to develop during the week. Please, stay tune to the changes, and
> decide whether you can afford or not to adopt them at this stage.
>
> Personally I'll offline 6th to 20th, so everything that you deliver before
> would make my final evaluation much easier.
>
> Thanks for your contribution to the Apache Marmotta project.
>
> Cheers,
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 660 2747 925
> e: sergio.fernandez@redlink.co
> w: http://redlink.co

[GSoC] less 1 month left

[Sergio Fernández <wi...@apache.org>]

According the official time-line:

http://www.google-melange.com/gsoc/events/google/gsoc2014

August 18th is the official 'pencils down' date for GSoC this year.

Please, Qihong Lin, remember to continue pushing hard. I did not see 
some much activity or reporting in the last weeks, and you still have so 
much to do for achieving the goals of the project.

We had been working at the ldp branch, fixing details discovered by the 
W3C test suite. They mainly affect the web service layer, but I think we 
extended the service api with some new methods. Next week Jakob and 
myself we plan to continue working on that, with the idea of merging 
stable changes back to develop during the week. Please, stay tune to the 
changes, and decide whether you can afford or not to adopt them at this 
stage.

Personally I'll offline 6th to 20th, so everything that you deliver 
before would make my final evaluation much easier.

Thanks for your contribution to the Apache Marmotta project.

Cheers,

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co

Re: [GSoC] LDP based on SPARQL, mid-term checkpoint

[Sergio Fernández <wi...@apache.org>]

Dear Qihong Lin,

continue working hard towards achieving the goals of the project. The 
sooner the better for testing and commenting your work, even implement 
missing features.

Thank so much.

Cheers,

On 02/07/14 13:15, Qihong Lin wrote:
> Dear Sergio,
>
> I've just translated all of the methods into SPARQL implementations,
> and committed the code. I'll watch the upstream, in case new methods
> or modifications are coming. It's actually ahead of the original plan.
>
> Thanks for sharing your opinions of my current work. In the next
> weeks, I'll resolve the problems you pointed out (i.e. tests,
> documentations, code abstractions and evaluations). Basically, I think
> everything is going on well until now. I'll turn to you for help, if
> there's any further question. Thanks a lot!
>
> Cheers,
> Qihong Lin
>
>
> On Tue, Jun 24, 2014 at 8:32 PM, Sergio Fernández <wi...@apache.org> wrote:
>> Hi Qihong Lin,
>>
>> it's the mid-point of the GSoC programme, so it's a good time to assess the
>> state of the project. It looks close to the plan and I'd like you to
>> (briefly) write-up how the project is going. Check you are getting what you
>> want out of the project as well. It is not just code production. Is the rest
>> of the plan looking right still?
>>
>> Looking on at the repository forked at github:
>>
>>    https://github.com/confidencesun/marmotta/tree/MARMOTTA-444
>>
>> besides the few comments I did on your commits, there are a few things I'd
>> like to discuss:
>>
>> * Working plan: concrete details about how your work is actually following
>> (or not) the proposed working plan.
>>
>> * Implementation feedback: which in the end may revert to the overall
>> quality of the project. For instance, looking to the current status of your
>> implementation http://s.apache.org/7mn I could expect that you should be
>> able to propose the usage of an abstract base implementation with some
>> commons things.
>>
>> * Method documentation: document how you translate the Sesame native call to
>> SPARQL queries will help to maintain the alternative implementation
>>
>> * User documentation: how to launch Marmotta using your implementation,
>> example requests, etc.
>>
>> * More testing: I know you are moving on a very unknown area, but the more
>> tests you write the best for discovering issues (specially lateral effect of
>> related code). The official LDP Test Suite would be a helpful resource.
>>
>> * Evaluation: for example, regarding performance: on the typical scenarios,
>> do you have some figure in the deviation in comparison with the main
>> implementation?
>>
>> And I think that's all...
>>
>> Remember that you can use the github wiki to write down whatever stuff you
>> need. Documentation is always good.
>>
>> But so far my overall impression for this checkpoint is that you are in the
>> right path.
>>
>> Thanks.
>>
>> Cheers,
>>
>> --
>> Sergio Fernández
>> Partner Technology Manager
>> Redlink GmbH
>> m: +43 660 2747 925
>> e: sergio.fernandez@redlink.co
>> w: http://redlink.co

-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 660 2747 925
e: sergio.fernandez@redlink.co
w: http://redlink.co