« Hide

1) Add a NEW method to the Navigation Service called "getFolderTree" -- This method will be functionally identical to calling getDescendants(depth=-1; type=Folder)
- Open question: We can choose to expose a "folderId" parameter, in which case it's really "getFolderSubtree", or we can say that there's no folder param and it always returns the folder tree starting at the root folder. (I prefer the latter approach but could go either way).
- Open question: Should this method ALSO be optional? (I'd prefer it it's required... but we should see if some repositories can't support this).

2) We will add a NEW repository-optional capability (in section 2.1.1) as follows:
- Name: capabilityDescendantNavigation
- Type: Boolean

If false, then the repository will throw the notSupported exception if the caller attempts to invoke the getDescendants method.

------------

In the ATOMPub binding, the services doc should be updated to expose this capability (as a link).

Show »

1) Add a NEW method to the Navigation Service called "getFolderTree" -- This method will be functionally identical to calling getDescendants(depth=-1; type=Folder) - Open question: We can choose to expose a "folderId" parameter, in which case it's really "getFolderSubtree", or we can say that there's no folder param and it always returns the folder tree starting at the root folder. (I prefer the latter approach but could go either way). - Open question: Should this method ALSO be optional? (I'd prefer it it's required... but we should see if some repositories can't support this). 2) We will add a NEW repository-optional capability (in section 2.1.1) as follows: - Name: capabilityDescendantNavigation - Type: Boolean If false, then the repository will throw the notSupported exception if the caller attempts to invoke the getDescendants method. ------------ In the ATOMPub binding, the services doc should be updated to expose this capability (as a link).