'services' and LDP (was: Interaction model vs data model)

> 
> In practice, I think there are two general categories of use cases. 1. generic/vanilla server that simply stores triples and regurgitates them without doing anything special with them. 2. application specific server - this is a bug tracking system for instance - which translates the triples into an actual application specific object. 

Thanks for mentioning these two categories Arnaud. 

It does seem that most people here are looking at category 1 type applications. 

As covered in the conversation on Monday call, some of us are interested in category 2. we would like to have an issue so that we can monitor the parts needed for category 2, track what we won't cover in LDP, etc.

Then how do we cover the missing parts ? Some options ::
 
* wait and see what others in the community (or this community do with it) 
* encourage an existing group (i.e. Networked Data [1]) to take this on 
* put some documentation on the wiki 
* have another top-level specification inside LDP 
* combination of above 
* ? 

thanks, 
Roger


[1] http://www.w3.org/community/networked-data/