Scope of the Use Cases & Requirements document

Hi all,

I started reviewing the Use Cases & Requirements (UCR) draft [1] more 
carefully and, while I'm impressed by the work Steve Battle put into it 
and can only thank him again for that, I have to say that I've got the 
feeling that it is going too far.

What I see in the UCR is not only a description of the problems to be 
solved but also a detailed description of what the solution should look 
like along with an analysis of what the spec provides and doesn't provide 
today. I don't think all of this belongs to the UCR.

This is NOT to say that I think we should throw away some of this stuff. I 
really think it is very helpful to have all this but I'm starting to think 
that we may want to move some of the content to a different document, like 
a primer or something like that. It also seems to me that the scenarios 
provide a good basis for developing our test suite which we need to talk 
about that at the F2F.

Steve, feel free to yell at me for not having brought this up earlier but 
I'd like us to discuss on Monday's call whether we need to rescope the 
document somehow.

Best regards.

[1] http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements
--
Arnaud  Le Hors - Software Standards Architect - IBM Software Group