How should "weak" resources be handled in a RESTful website?

In RESTful websites, each resource should be identified by an URI. But how should I handle what are called "weak entities" in relational databases, aka, ressources that only make sense when related to another resource? Should these have specific URIs pointing to them too?

To give an example: Say I have a website for showing events going on in a city. Each event can have comments posted by users.

An event is a resource, with corresponding uri (/events/:id). But should each comment have an uri, too? Like /events/:eventid/comments/:commentid ? Comments only make sense when they're associated with the corresponding event, so having a page just to represent one message seems weird/unnecessary. I only want the comments to appear on the page of the event.

I guess the /events/:eventid/comments/:commentid uri could be used for a DELETE request, but what should it return to a GET request?