Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Class "Lot" under "Call For Tender" #24

Closed
eprocurementontology opened this issue May 19, 2017 · 3 comments
Closed

Class "Lot" under "Call For Tender" #24

eprocurementontology opened this issue May 19, 2017 · 3 comments

Comments

@eprocurementontology
Copy link
Collaborator

Claude Schmit proposed the creation of a new class "Lot".
The notion of class "lot" is important and often implicit. It does not appear under "call for tender", it's a 1..n cardinality and many classes will fall under each "lot" like "tender" and "contract". Also one "lot" can have several "contracts" (cascade).

@eprocurementontology eprocurementontology changed the title "Lot" class under "Call For Tender" Class "Lot" under "Call For Tender" May 19, 2017
@JachymHercher
Copy link

(Don't overlook: when the same contractor won several lots, then one "contract" can have several "lots" . I.e. the lot-contract relationship can be many to many.)

@makxdekkers
Copy link

In the latest version of the conceptual model (to be provided ahead of the WG meeting of 24 May 2017) there is a comment in the definition of the Call For Tender: "The relationship between Call For Tender and Lots needs to be further detailed".
If a Contract can refer to more than one Lot, and multiple Contracts can refer to one Lot, then the relationship between Contract and Lot indeed needs to be n..n.
This is an issue that needs to be further discussed by the Working Group.

@eprocurementontology
Copy link
Collaborator Author

After discussion contracts refer to 1..n lots

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants