Based on a modified version of I am creating permanent services for many database organizations. Some of these organizations are linked to lookup tables, as shown below: Lookup tables are associated with one and only one table. Additionally, lookup tables will be used to populate dropdown lists, previewviews, and comboboxes by the client application for editable areas of their respective unit tables. To see the values / table should get their own URR or do they "share" with their parents? What are the pros / cons of each? Option 1: / Entities / Space / Space credentials / Option 2: Lookup / Space credentials / In a rental system, the methods of building your URLs are not as important as identifying resources and the names you give them. From what you have shown, it seems that you have three resources: Space Spacequery Lookup The URI, which you give to these resources, is a matter of great taste. For example, someone in REST prevents you from ...