Senior Principal Scientist @Adobe, co-founder @TheASF, author of REST architectural style and @IETF standards (HTTP, URI, and URI Templates). @[email protected]
@seeteegee@jshurmer@htmx_org Specifically, your concern about optional/required fields is a byproduct of using network protocols to perform remote data access. It's a different architectural style. It is not REST, in any way, shape, or form, even when it uses HTTP. That's okay. I get the same royalties.
@seeteegee@jshurmer@htmx_org In contrast, if we have a discussion about architectures based on the REST architectural style, we will spend most of our time hypertexting and none of it scheming. On purpose, because schemas are known to be brittle over time. That doesn't mean REST >> RDA for everything.
@seeteegee@jshurmer@htmx_org JSON is a data format. Schema is a database structuring concept. REST is an architectural style. It's like trying to explain how to ride a bike and you start asking what about wooden wheels? Are wooden wheels a good idea? They worked for covered wagons, right? Sure, but… horses.
@seeteegee@htmx_org That doesn't apply to Plan9, because their uniform file interface doesn't include hypertext as a constraint, for good reason. The goal is to design good systems, each according to their own needs, not to create a single universal style that applies to all systems.
@seeteegee@htmx_org No one, least of all me, argues that documentation isn't useful. External, application-specific documentation isn't necessary for a RESTful system because of self-documenting hypertext and an interface already documented through standards. That doesn't imply there are no docs.
Excited to talk with developers who are adding access controls to their applications, about Google's Zanzibar approach to managing users, groups, roles, and permissions ranging from social networks to cloud resources on a livestream Monday: https://t.co/gEBiGB66WS
Today is the ASF's 25th anniversary! Thank you to the countless contributors, committers, PMC members, and volunteers that enable The ASF to deliver software the world relies on. 💛
Join in the celebration: https://t.co/3S4DgPLoJx #ASF25Years#opensource
@devwrite_@techsavvytravvy@htmx_org I don't classify things under one buzzword or another (RESTful was minted by someone else), but what I wrote about is an architectural style for network-based applications that influenced an architecture for the Web (URI, HTTP, and HTML) which was implemented in many systems.
@devwrite_@techsavvytravvy@htmx_org I talk in my dissertation about network-based applications (applying computing to accomplish a user's task). E.g., access to a bank account would be one application (RESTful or not). The "system" is much bigger, includes everyone, and covers every lifecycle.
@yawaramin@alexbunardzic@devwrite_@MorriceGavin@htmx_org Well, not exactly, since those are both general-purpose data formats capable of describing hypermedia and non-hypermedia. They just need a little push in the form of a more specific media type that would tell us how to work with certain element or object names, hierarchy, etc.