Issue Details (XML | Word | Printable)

Key: CMIS-18
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: David Nuescheler
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
OASIS Content Management Interoperability Services (CMIS) TC

Rename REST-Bindings to "AtomPub Bindings" or "AtomPub Extensions"

Created: 05/Dec/08 11:16 AM   Updated: 04/Jan/10 11:33 PM
Component/s: REST/AtomPub Binding
Affects Version/s: Draft 0.50
Fix Version/s: Draft 0.60


 Description  « Hide
Based on the fact that REST [1] is not a protocol but an architectural style the term "binding" is definitely wrong.


I think we could also choose to call it something more vague with restful in its name.


Generally, I would like to propose that in addition to changing the name throughout the specification we should
also try to adhere to the design principles of AtomPub.


[1] http://en.wikipedia.org/wiki/Representational_State_Transfer

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Julian Reschke added a comment - 17/Dec/08 07:53 AM
I think that the use of the term "ReST" is minimally confusing, and definitively causing political discussions I'd prefer to avoid.

If what we want is *some* HTTP binding, call it "HTTP binding". If we're sue it's gonna be based in AtomPub, then let's called it that way.

Al Brown added a comment - 28/Jan/09 05:45 PM - edited
How about 'RESTful AtomPub binding' since the goal of the TC is to provide a REST-ful binding.

David Choy added a comment - 28/Jan/09 05:47 PM
"RESTful AtomPub binding"

Al Brown added a comment - 04/Jan/10 11:33 PM
JIRA Cleanup