/rest/fcr:sitemap
/rest/fcr:search
/rest/fcr:namespaces

Describe

/rest/{path}/fcr:describe
- GET profile or description [repo describe at root, profiles by type]
- POST unsupported?
- PUT unsupported?
- DELETE unsupported?

e.g.:

GET /rest/fcr:describe

• describe the fcrepo4 repository

GET /rest/sufia:123456789/fcr:describe

• describe the object sufia:123456789 (equivalent to the fcrepo 3.x "object profile") 

GET /rest/sufia:123456789/content/fcr:describe

•  describe the datastream sufia:123456789/content (equivalent to the fcrepo 3.x "datastream profile")
  

GET /rest/some/arbitrary/jcr\:path/to/sufia:123456789/the/tree/continues/fcr:describe

• describe the node at /rest/some/arbitrary/jcr\:path/to/sufia:123456789/the/tree/continues (equivalent to the fcrepo3.x "datastream profile"). If the node resolves to a JCR "nt:file", we treat it as a datastream. Else, an object (or collection)

Other stuff

/rest/fcr:nextPID
- POST mints an ID

/rest/{path}
- GET lists children, with optional filter by mixin
- POST create a new node of QueryParam "mixin" at {path}
- PUT mutate the object at {path}
- DELETE remove the object at {path}

/rest/{path}/fcr:new
- POST create a new child of QueryParam "mixin" under {path}

/rest/{path}/fcr:new/fcr:content
- POST create a new nt:file under {path} with a binary value of the request entity

/rest/{path}/fcr:content
- GET the bytes from {path}/jcr:content/jcr:data
- POST create a new nt:file at {path} with a binary value of the request entity
- PUT mutate the binary value of the nt:file at {path}
- DELETE remove the jcr:content child from the node at {path}

/rest/{path}/fcr:datastreams is batch DS operations
- GET
- POST
- DELETE

/rest/{path}/fcr:fixity
- GET get the fixity report for the nt:file at {path}

/rest/{path}/fcr:versions
- GET the version history of the nt:file or the nt:folder (as appropriate) at {path}