I promise this is the last post having the ‘useful dereferenceable URIs’ title.
I’m sorry for being still at this point but I didn’t manage to go faster and in this last week I made some refinements to the previously described REST API and to my plans in general, which have caused a little time delay. In fact I looked at my use case scenarios and refined my Api to ensure that all those scenarios would be realized. There were some resources which required to browse the whole sensor data set, without any filter, which, considered the great amount of SD should be preferably avoided. Then now every resource that’s referred to data distributed on a period of time longer than a single day, can include only data coming from Telemetry, while if distributed on a period of time of one day, can include only data coming from DPD. Data coming from SensorBase are used only when it’s possible to include at least one filter (such as the resource which generated the SD etc.) or when a specific timestamp is given.
I also added some considerations about authorization levels to access resources (always considering my scenarios), and as I wrote on the hackystat-dev ml:

this is how the privacy setting will work:

until the Sensorbase itself won’t allow no registered users to access part of its data, neither the LiSeD service will allow this. Then I specify that some information is not under privacy issues (accessible by ‘Any’) only for a documenting purpose, for those in future who might want to understand which data could become freely available; but “now” only registered users can access all the services (included mine).
The only changing to the currently privacy state-of-the-art regards the chance to make, being a Hackystat user, the owned user profile and/or user sensor data viewable by other ‘hackystat registered users’. The same should be possible for project profiles if a project owner decides it. Well, why. This is necessary to realize some use case scenarios of mine, in which a user can get advantage of Hackystat data to retrieve other developers expert in some kind of situations; and other scenarios in which a project is retrievable through its quality details.

On my REST Api wiki you can view

• the new Api;
• which resources have been implemented since now(I’m trying to write JUnit Tests as a new resource is provided, even if really approximatively);
• examples of responses for the main (most interesting) resources between the ones implemented.

Note that there aren’t yet links to external datasets and data describing resources constitutes just a base for future links.
The additional data that I’m supposing to retrieve in the Properties field of data stored in SensorBase, are listed officially at the AdditionalDataExpected wiki page.

During the next week:
I definitely must finish to implement all the necessary resources and start the hard linking phase for the next week.