Versions Compared

Old Version 17

changes.mady.by.user Gabriel BERLICKI

Saved on

compared with

New Version Current

changes.mady.by.user Gabriel BERLICKI

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Section


Column

Table of Contents
maxLevel5
typeflat

Figure A: Notification of document availabilityFigure B: OSF checking document availability
The following diagram describes the exchange flows for registration and retrieval of documents hosted in WIPO DAS by notification to OSF

The following diagram describes the exchange flows for registration and retrieval of documents hosted in WIPO DAS and the OSF checking on regular basis statuses of retrievals requests

draw.io Diagram
bordertrue
diagramNameDocuments-hosted-by-WIPO-DAS
simpleViewertrue
linksauto
tbstyletop
diagramDisplayNameFigure A
lboxtrue
diagramWidth659
revision1

draw.io Diagram
bordertrue
diagramNameDAS Retrievals by checking document availability
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth659
revision1



maxLevel

Column
width40%

a.- New DAS exchange API

Table of Contents
5
Page Tree
roota.- New DAS exchange API
pagea.- Initial private_key_jwt registration process


...

Exchange flow to register document

Section


Column
width60%


StepAPI RequestNotes
(1a) - OFF requests a pre-signed URL from WIPO DAS to upload a file identified by a file idPOST /das/v1/requests/files/url-uploads
note

Not required if OFF keeps the actual document file content in its own digital library

(1b) - OFF uploads the document file content using a pre-signed URL given in step (step 1a)File upload via PUT
(1c) - OFF requests document registration to WIPO DAS by referring to the uploaded file content by the corresponding file idPOST /das/v1/requests/registrations



Column
width40%

Info
titlePostman demo test

d.1.1.- Registration process



...

Exchange flow to correct filing date or parent application details in which the foreign priority document is held 

Section


Column
width60%


StepAPI RequestNotes
(1c) - OFF requests document registration to WIPO DAS by specifying the new document attributesPUT /das/v1/requests/registrations



Column
width40%


Info
titlePostman demo test

d.1.3.- Update registration



...

Exchange flow to replace document content for correction purpose 

Section


Column
width60%


StepAPI RequestNotes
(1a) - OFF requests a pre-signed URL from WIPO DAS to upload a file identified by a file id POST /das/v1/requests/files/url-uploads

(1b) - OFF uploads the corrected document file content using a pre-signed URL given in step (1a)



(1c) - OFF requests document registration to WIPO DAS by referring to the uploaded file content by the corresponding file idPUT /das/v1/requests/registrations



Column
width40%


Info
titlePostman demo test

d.1.3.- Update registration



...

Exchange flow to retrieve document hosted in WIPO DAS

Section


Column
width60%


StepAPI RequestNotes
(2a) - OSF sends a document retrieval request to WIPO DAS and receives a request acknowledgement id POST /das/v1/requests/retrievals
(2b) - WIPO DAS prepares the requested document for download and notifies the OSF of the document availability (i.e. Figure A) by referring to the request acknowledgement id returned in step (2a)POST /das/v1/requests/notificationsAlternatively , OSF may use the check status (i.e. Figure B) to download the document content when it is reported as available by WIPO DAS (i.e. GET /das/v1/requests/retrievals) 

(2c) - OSF retrieves file location URL from WIPO DAS to download the document file content

POST /das/v1/requests/url-downloads

Downloads can be repeated while the requested document is not deleted from WIPO DAS

(2d) - OSF downloads file from WIPO DAS 



(2e) - Optionally OSF deletes the download files from the DAS transit zoneDELETE /das/v1/requests/filesIf OSF does not delete the downloaded file, WIPO DAS will delete it after a pre-defined period (e.g. 1 week)



Column

d.2.1.- Successful retrieval example

Section
Column
width40%


Image Added

Image Added

Fig. AFig. B
Column
Section
Postman demo test
Column

Exchange flow to retrieve document hosted in WIPO DAS

  • (2a) - OSF sends a document retrieval request to WIPO DAS and receives a request acknowledgement id (i.e. POST /das/v1/requests/retrievals)
  • (2b) - WIPO DAS prepares the requested document for download and notifies the OSF of the document availability (i.e. Figure A) by referring to the request acknowledgement id returned in step (2a) (i.e. POST /das/v1/requests/notifications) 
Note
Alternatively , OSF may use the check status (i.e. Figure B) to download the document content when it is reported as available by WIPO DAS (i.e. GET /das/v1/requests/retrievals) 
  • (2c) - OSF retrieves file location URL from WIPO DAS to download the document file content (i.e. POST /das/v1/requests/url-downloads). Downloads can be repeated while the requested document is not deleted from WIPO DAS
  • (2d) - OSF downloads file from WIPO DAS 
  • (2e) - Optionally OSF deletes the download files from the DAS transit zone (i.e. DELETE /das/v1/requests/files) 
Note
If OSF does not delete the downloaded file, WIPO DAS will delete it after a pre-defined period (e.g. 1 week)
Info
title

d.2.1.- Successful retrieval example