The section "Framework" on the developer overview page currently states that one feature common of all resources is "[a] URL that identifies the resource". This formulation seems unfortunate in two respects:

1. Resource used outside a RESTful setting may not have a URL in any meaningful sense and, as pointed out in the spec here, may not even have a logical ID.
2. Even where a logical ID is present, the URL is implicit and not directly visible in the resource. While that is indeed discussed in the later section "URLs and Identities", it seems potentially confusing for a newcomer to read this and then be shown an example resource in which this identifier URL is (seemingly) absent (but other URLs are present).

Point (1) seems to reflect a similar issue on the "Resource" page, see this related ticket: FHIR-33978. In line with the suggestion in that ticket, the request here is that the first characteristic in the bullet list in the section "Framework" be reformulated to avoid referring to URLs, e.g. to "An identifier for the resource".