Sure, but how is that a helpful concept in any way? If I started calling my operating system an "ALLOCBAG" and made a dissertation talking about "The ALLOCBAG P

Sure, but how is that a helpful concept in any way? If I started calling my operating system an "ALLOCBAG" and made a dissertation talking about "The ALLOCBAG Principle" you can't really deny me that it's a thing that exists ("ALLOCBAGs are all around you! You're using one I'd right now", I'd say), but it's not really advancing the state of discussion here. Similarly, rebadging "a client/server system that does a thing when you interact with the client" as "REST" (yes, I know there's a bit more to the definition) doesn't seem useful or helpful. So out it goes, in favor of the one that's talking about a style of API design. Roy Fielding designed the Adobe Experience Manager API according to his idea of REST [0]. I don't think the resulting API was remarkably noteworthy. [1] [0] https://www.slideshare.net/AEMHub2014/rest-in-aem-by-roy-fielding https://www.slideshare.net/AEMHub2014/rest-in-aem-by-roy-fie... [1] https://experienceleague.adobe.com/docs/experience-manager-65/content/assets/extending/mac-api-assets.html https://experienceleague.adobe.com/docs/experience-manager-6...