From 7e31597b6da7a9f58519077e9f4bf736ceaae893 Mon Sep 17 00:00:00 2001 From: Georg Dangl Date: Mon, 5 May 2025 11:25:57 +0200 Subject: [PATCH 1/2] Add missing entry for topic delete entry and update docs about authorization --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 6d4977c..8548c7d 100644 --- a/README.md +++ b/README.md @@ -450,6 +450,7 @@ level by default (i.e. unless overridden by specific topics) The available actio * *updateFiles* - The ability to update the file header (see [3.3.3 PUT Files (Header) Service](#333-put-files-header-service)) * *createComment* - The ability to create a comment (see [3.4.2 POST Comment Service](#342-post-comment-service)) * *createViewpoint* - The ability to create a new viewpoint (see [3.5.2 POST Viewpoint Service](#352-post-viewpoint-service)) +* *delete* - The ability to delete a topic (see [3.2.5 DELETE Topic Service](#325-delete-topic-service)) #### 3.1.5.3 Comment @@ -705,7 +706,7 @@ Modify a specific topic, description similar to POST. This operation is only pos DELETE /bcf/{version}/projects/{project_id}/topics/{topic_guid} -Deletes a single topic. This operation is only possible when the server returns the `delete` flag in the Topic authorization, see section [3.2.8](#328-determining-allowed-topic-modifications) +Deletes a single topic. This operation is only possible when the server returns the `delete` flag in the Topic authorization, see section [3.2.6](#326-determining-allowed-topic-modifications) **Example Request** @@ -1930,9 +1931,8 @@ Note: If there is a comment associated to the viewpoint, the server might reject ### 3.5.11 Determining allowed Viewpoint modifications -The global default Viewpoint authorizations are expressed in the project schema and when Viewpoint(s) are requested with the -query parameter "includeAuthorization" equal to "true" Viewpoints will include an "authorization" field containing any local -overrides for each Viewpoint. +The global default viewpoint authorizations are expressed in the project schema and when viewpoint(s) are requested, they will include an "authorization" field containing any local permissions for each viewpoint. +You can get the `createViewpoint` authorization from the parent topic, and the `deleteViewpoint` authorization from a viewpoint itself. ## 3.6 Related Topics Services From fdaa695fb6a2797848a86dbee56bdb2e62aaf0d2 Mon Sep 17 00:00:00 2001 From: Georg Dangl Date: Mon, 5 May 2025 11:31:16 +0200 Subject: [PATCH 2/2] Update comment about where to find viewpoint actions --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8548c7d..4da42ba 100644 --- a/README.md +++ b/README.md @@ -1931,7 +1931,7 @@ Note: If there is a comment associated to the viewpoint, the server might reject ### 3.5.11 Determining allowed Viewpoint modifications -The global default viewpoint authorizations are expressed in the project schema and when viewpoint(s) are requested, they will include an "authorization" field containing any local permissions for each viewpoint. +The global default viewpoint authorizations are expressed in the project schema (`topic_actions` will list whether or not it's possible to perform the `createViewpoint` action) and when viewpoint(s) are requested, they will include an "authorization" field containing any local permissions for each viewpoint. You can get the `createViewpoint` authorization from the parent topic, and the `deleteViewpoint` authorization from a viewpoint itself. ## 3.6 Related Topics Services