On the spec page for "Resource", the section "Scope and Usage" currently (and in the latest build) says that a resource "is an entity that [...] has a known identity (a URL) by which it can be addressed" (my emphasis). However, further down, in the section "Logical ID", it is made clear that a logical ID may be missing, in which case no standard URL can be constructed:

In some contexts, resources are not associated with location on a RESTful server, either because they are only created transiently for transfer between systems, or the systems are not using RESTful servers. In these cases, resources may be assigned some kind of location anyway, for purposes of consistency, or they might not have an assigned logical id, and they are identified based on other kinds of identifiers.

(BTW, in the first sentence in the quote, "associated with location" seems to lack an article).

By comparison, the section "Boundaries and Relationships" on this page simply says that a a resource has "[a]n identity" (with no mention of URL) which also makes sense in a non-RESTful/business-ID-based setting. The request here is therefore that "(a URL)" be struck from the first bullet point in the section "Scope and Usage", so that it simply reads "has a known identity by which it can be addressed".