nodes
GET nodes gets the top level nodes
input: none
output: xml representations for a list of top level nodes
GET nodes/node/\[node id\] get all the child nodes under the parent node specified by id input: none output: xml representations for a list of nodes under the specified parent node |
POST nodes searches for nodes
input: xml representations for search criteria
output: xml representations for a list of nodes match the search criteria
*node* GET node/\[node id\] gets the node specified by the node id input: none output: xml representations for the specified node |
GET node/\[node id\]/content get the content of the specified node (it should be an atom node) input: none \\ output: url of the content or the content itself |
POST node create a new node
input: xml representation of the node
output: xml representation of the node with the newly created node id
POST node/\[node id\]/content save the content of the specified node (it should be an atom node) input: multi-part content output: status of the operation |
DELETE node/\[node id\] deletes the node specified by the node id input: none output: status of the operation |
PUT node/\[node id\] modifies the node specified by the node id input: xml representation of the node output: status of the operation |
questions:
Stellars needs child nodes to be ordered. The ordering info should be in the input xml when creating a node. After node creation, will Stellar need a way to change the order of a node?
Does Stellar do tagging or any kind of classfication?
Since we are not sure if we will use the api to do authentication or authorization as well as user/group management, the draft doesn't cover those functionalities. Stellar will authenticate to the REST api using application certs. Once authenticated, the api will run as an admin user to Alfresco.