First, the Repository module is a good thing and the folks working on it have done a great job.  There is one thing that's been troubling me about it though and it's related to the concern of the original poster - failure to support RESTful URLs.  Not having granular URLs which address individual documents in the repository makes it difficult for crawlers to do their thing.  It also makes it difficult (impossible?) to bookmark a document, e-mail a pointer to someone or link to it from another web page. 

E-mailing a pointer, bookmarking, linking and being crawl-able are very important attributes of a web application in my opinion.  The Blog module is an example of a module which is doing things in more of a RESTful fashion, that is individual Blog entries have unique URLs.  If I'm missing some design principals here (or some basic featuer!) please let me know, as anything that helps me apply this great module is much appreciated.

Thanks,

Bill

I second the comment. that I like the way the Blog handles indivual entries/articles. I would like to have a list of documents in the Repository that I can just point to one and be taked right to the item DETAIL. The Blog does that even from the RSS feed, which is very useful.

If there was a security concern, that item should return a "You are not worthy" message, or just not show up in a public RSS feed from the repository.