Summary
The Third Session of the DAS Working Group held from July 12 to 14, 2011 in WIPO gave the mandate to the International Bureau to implement the extension and improvements of DAS as summarized in the Summary by the Chair (Document WIPO/DAS/PD/WG/3/7).
The requirement specifications relating to the extension and improvements of DAS (2.0) is posted in this page for reviews by the DAS Consultative Group.
Some changes relating to DAS exchange betwwen Offices over the TDA/PDX and PCT-EDI protocols will be required to support Route D. Proposal for changes in TDA/PDX will be discussed through the TDA forum. PCT-EDI related changes are discussed below.
Review of DAS 2.0 requirements specification
The requirements specification was finalized and posted on April 10, 2012 with the revision 2.4 (version with tracking changes). It includes a few minor corrections by removing two inappropriate descriptions of ACL. The specifications (revision 1.0) of the DAS 2.0 Applicant Portal was made available.
Proposed implementation timelines from 2012 to 2013
The International Bureau would like to propose the following revised timelines for the implementation DAS 2.0. Current participating Offices are welcome to comment on the proposed timelines and on the migration plan of each inividual Offices.
System Component | Specifications Review | Office and End-user Testing | Production Release |
|---|---|---|---|
Route D migration in respect of DAS TDA/PDX (e.g. 1.7.3) for patent applications only A new change request to add a dasRegister operation needs to be raised in the TDA forum. | June 29, 2012 | 2013 | 2013 |
Route D migration in respect of DAS PCT-EDI protocol for all types of applications including (Industrial Designs, Patents, Trademarks and Utility Models) | February16, 2012 | from March 1, 2012 to June 22, 2012 | July 1, 2012 |
Account-based Applicant portal for Industrial Designs, Patents and Utility Models applications (Trademark applications are not supported by the portal) | February 16, 2012 | September 2012 | When Route C Offices migrate to the new Route |
The proposed change and schedule support backward system compatibility for Routes "A" and "C" Offices and would allow the Offices to implement the changes at their own pace.
Improvements released in January 2012
The following changes were released in January 2012.
Security Improvements
DAS security improvements to add cross-check of the priority filing date were released in January 2012 and supported by exchange via TDA/PDX 1.7.2 and PCT-EDI.
System Component | Office Testing | Production Release |
|---|---|---|
DAS upgrade to TDA/PDX 1.7.2 | from September 12, 2011 to December 28, 2011 | January 4, 2012 |
DAS PCT-EDI changes to generate error code ='-4' in response due to mismatch of priority filing date (library-transaction-v1-2.dtd) | from October 24, 2011 to December 28, 2011 | January 4, 2012 |
The proposed change and schedule support backward system compatibility for "Route A" Offices and would allow the Offices to implement this upgarde individually.
Change in Priority Request function
The security improvement brings in an additional check to ensure correctness of the priority filing date, if it is provided by the requesting Office (OSF) during the Priority Document request.
The current Route C Offices (JP, KR and US) would be moving to a new version TDA/PDX 1.7.2 starting next year (04-JAN-2012) to implement this cross-check as OFF whenever applicable and to supply the priority filing date as OSF.
The change taking into account comments posted by the JPO on November 11, 2011 will be made as follows:
In respect of priority documents held in WIPO for current Route A Offices (AU, ES, DK, FI, GB, IB, SE), the following conditions apply:
- DAS holds the priority filing date with the priority document, the DAS core system will perform the cross check:
- (a) - If the OSF supplies a wrong priority filing date, retrieval will not be allowed and the OSF will receive an appropriate response error specific to protocol TDA (i.e. status 13) or EDI (error -4).
- (b) - If the OSF does not provide any priority filing date, no cross check will be performed by DAS.
- DAS does not hold the priority filing date with the priority document, the DAS core system will not perform this cross check.
The IB would like to suggest the following for your consideration:
- (i) - Shall we put a restriction in the upload operation so that the priority filing dates are always provided and the system generates error if it is not the case.
- (ii) - If we don’t implement the restriction for registering the priority document with its filing date (like the current situation), there are cases where the priority filing dates are not provided and therefore cross-check cannot be performed by DAS.
- (iii) - Would there be cases where the priority filing dates get changed after DAS registration? If so, there should be a provision for the OFF to update the date record in DAS. The DAS system should notify OSFs which have already retrieved successfully the priority document about the date change. This is unlikely to happen because within the time window when a correction of the priority filing date may be made (e.g. two months) there would be no retrieval.
With regard to priority documents held in Route C Offices (JP, KR and US), the following conditions apply:
- If DAS holds the priority filing date, the cross-check as mentioned in (a) and (b) apply
- If DAS does not hold the priority filing date, the cross-check will be performed by the depositing Office.
Comments made by Offices have been included in the revised versions of the requirements specification of DAS 2.0 a prototype showing future pages of the Applicant and Office portals is attached (If you wish to see it, click here to download the Zip file and unzip it to your local desktop).