Depracating milestone documents

[timgdavies]

This is under consideration for the 1.1 upgrade

The issue

At the moment we allow document objects to be associated with individual milestone objects.

As the implementation of properties analysis (#70) has shown, we have not seen any use of this feature in the standard, and it means that consuming applications have to look in a number of places to find all the documents that might be available.

The proposal

In line with the proposal in #70 to regularly review, and the deprecation proposals in #189 we should consider deprecation of milestone/documents in 1.1.

Documents can still be attached at the tender, award, contract and contract/implementation levels.

Engagement

Please indicate support or opposition for this proposal using the +1 / -1 buttons or a comment. If opposing the proposal, please give clear justifications, and where possible, make an alternative proposals.

Please leave a comment indicating whether you think this proposal should form part of the core standard or whether it should be an extension.

[timgdavies]

This was discussed on today's OCDS community call.

Angelos Hatzikyriacos from European Dynamics explained that their contract management modules can capture documents related to milestones, hence rather that complete deprecation of milestone/documents this could move from core to an extension.

(I.e. deprecate, but introduce extension)