Dear Nandana and Sergio, I'm grateful to your explanations.
I'll focus on implementing the LdpSrvice interface using SPARQL. The implementation can be developed incrementally during the GSoC 2014 summer, if anything would be changed for LdpService. I can also promise to maintain the implementation after the GSoC program. As a student, it's great to get involved into an open source community with long time contributions. I believe I can learn a lot from the project experience. According to your replies, the testing work contains 2 parts: 1) unit tests (junit) of the SPARQL implementation itself; 2) RESTful service tests (rest-assured). It seems the later one is service oriented, not for the concrete implementations. Shall we test the RESTful services for different LdpService implementations (i.e. different test cases/suits for different implementations)? I'm clear about the project scopes now: the SPARQL implementation and the tests. The approaches are lucid in my mind as well. Anything else to be considered/discussed for the project scopes/approaches/etc? If not, I'd like to prepare a project proposal draft. Best, Qihong Lin On Sun, Mar 2, 2014 at 7:18 PM, Sergio Fernández <[email protected]> wrote: > Hi, > > > On 01/03/14 10:38, Qihong Lin wrote: > >> It seems the api and implementation are still in progress. >> Is LdpService.java supposed to conform to the W3C working draft in 2013-07 >> [1] or the latest one here [2]? When will Linked Data Platform become a >> W3C >> recommendation? >> > > Nandana already did a great summary of the following steps of LDP at W3C. > I expect the timing would fit quite well with GSoC's timeline, and by the > end of April everything should be stable enough. > > But I'd say for your project the uncertainty is even smaller: MARMOTTA-440 > is defining the stubs for the rest web services, which pushes requirements > to fully define the LdpService interface. Therefore your project would > target a concrete implementation of that interface. You should not care > about other details around; although, of course, any feedback would be > always welcomed to improve the whole stack. > > > Now, I can totally understand the source code of Sesame-native >> implementation. I have good knowledge of SPARQL 1.1. With Sesame, I can >> write codes of SPARQL Query for LdpService.exists() and getStatements(), >> while SPARQL Update [3] for LdpService.addResource() and deleteResource(). >> As to LdpService.exportResource() and generateETag(), it's just required >> to >> translate the inline getStatement() codes into SPARQL queries. Am I right >> about the above approaches? >> > > Complete right: SPARQL 1.1 implementation of those methods. For the moment > are few, but it'll still evolving and the list will grow for sure. > > > We use industry standards: git for code control, maven as build tool, >>> junit and rest-assured for testing, Weld for CDI, etc. But don worry if >>> your are not some familiar with any, because in case your proposal gets >>> granted, a mentor will be assigned to help during the project execution. >>> >> >> Thanks for telling me about these. I'm familiar with maven and junit. As >> to >> git and Weld, I've just started to learn their documents. Is rest-assured >> the one here [4]? >> > > Exactly that. It provides a very nice DSL for REST testing. See for > instance this test: > > https://git-wip-us.apache.org/repos/asf?p=marmotta.git;a= > blob;f=platform/marmotta-ldp/src/test/java/org/apache/ > marmotta/platform/ldp/webservices/LdpWebServiceTest.java;h= > 4883e8bee28a16978ec82ac88dc06caf5c50bd1d;hb=refs/heads/ldp#l90 > > Although not included in the description, testing is very important for > us. Therefore it is expected you would also help extending that test suite, > in order to improve the validation of your implementation. > > Thanks for your interest. Please, let us know if you may need anything > else for the proposal preparation. > > > Cheers, > > -- > Sergio Fernández > Senior Researcher > Knowledge and Media Technologies > Salzburg Research Forschungsgesellschaft mbH > Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria > T: +43 662 2288 318 | M: +43 660 2747 925 > [email protected] > http://www.salzburgresearch.at >
