right on, but you raise the question: "What is RESTful?" and then subsequently give a definition that does not consider the constraints of REST or specifically HATEOAS.
you say:
"RESTful is an architectural style of designing an end-point in which software can retrieve data using the HTTP protocol."
this is an incomplete definition. as Roy fielding suggests, if you want to use a buzz word, stick with CRUD and HTTP, but you do not need to confuse the reader by mentioning REST if you are not interested in developing, describing, interpreting or explaining REST architectural style.
we want to focus on the essentials and allow developers to learn the right concepts
right on, but you raise the question: "What is RESTful?" and then subsequently give a definition that does not consider the constraints of REST or specifically HATEOAS.
you say:
"RESTful is an architectural style of designing an end-point in which software can retrieve data using the HTTP protocol."
this is an incomplete definition. as Roy fielding suggests, if you want to use a buzz word, stick with CRUD and HTTP, but you do not need to confuse the reader by mentioning REST if you are not interested in developing, describing, interpreting or explaining REST architectural style.
we want to focus on the essentials and allow developers to learn the right concepts
I have rephrased the sentence, thanks for helping me out. Tell me if I need to change to anything else. I'd appreciate it.