[OASIS Issue Tracker] (UBL-226) ContractFolderID - "Internal Identifier" vs "Procedure Identifier"

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

Yves Jordan created UBL-226:
-------------------------------

             Summary: ContractFolderID - "Internal Identifier" vs "Procedure Identifier"
                 Key: UBL-226
                 URL: https://issues.oasis-open.org/browse/UBL-226
             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


_*ContractFolderID*_ is commonlyÂused to mark the "_Procedure Identifier_" while following its definition, it looks closer to the Internal Identifier than to the procedure identifier:
 * +*ContractFolderID*+: "An identifier, +assigned by the sender+, for the process file (i.e., record) to which this document belongs." (UBL definition)
 * +*Internal Identifier*+: "The internal identifier used for files regarding the procurement procedure or lot before a procedure identifier is given (e.g. coming from the buyer's document management system or procurement planning system)."
 * +*Procedure Identifier*+: "The European Public Procurement Procedure Identifier, a unique identifier of a procurement procedure. Including this identifier in all published versions of this notice (e.g. published on TED, national publication portals, regional publication portals) allows unique identification of procurement procedures around the EU."

What would be the best approach?
 * have a new element for Internal Identifier,
 * Use the same element for "Internal Identifier" until a "Procedure Identifier" is assigned, then use it for the Procedure ID,
 * have a new element for the Procedure Identifier.



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