[OASIS Issue Tracker] (UBL-212) Best way to deal with changes

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Yves Jordan created UBL-212:
-------------------------------

             Summary: Best way to deal with changes
                 Key: UBL-212
                 URL: https://issues.oasis-open.org/browse/UBL-212
             Project: OASIS Universal Business Language (UBL) TC
          Issue Type: Improvement
          Components: Documents and business objects
         Environment: UBL - 2.2 - Pre-Award

Â
            Reporter: Yves Jordan
            Assignee: Cecile Guasch


The challenge is the following:

When changes are applied to notices, some specific information has to be reported:
 * Â*Change Description: (text)*

ÂÂÂÂÂÂÂÂÂÂ The description of changes in the notice compared to the original notice.
 * *Change Procurement Documents: (indicator)*

ÂÂÂÂÂÂÂÂÂÂ The procurement documents have changed.
 * *Change Procurement Documents Date: (date)*

ÂÂÂÂÂÂÂÂÂ The date and time when the procurement documents have changed.
 * *Change Reason Code: (code)***

ÂÂÂÂÂÂÂÂÂÂ The main reason for the change in the notice compared to the original notice.
 * *Change Reason Description: (text)*

ÂÂÂÂÂÂÂÂÂ The description of the main reason for the change in the notice compared to the original notice.

It also has to refer to the notice object of the change.

We have different available options
 # Have necessary elements added to all notices (PIN, CN and CAN)
 # Create a new document type usable as a cover (could also be used for other document types)
 # Use existing elements:
 ** NoticeID,
 ** Notice VersionID, (New element as done for ESPD)
 ** ReplacedNoticeDocumentReference

Some guidance for this last option would be welcome as Iâm not certain there are already all required elements in the current schemas. Iâm also not certain having identified all relevant elements.

The need for the VersionID is justified mainly by the fact that there are different distribution channels and the reception sequence may not follow the submission one.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)