[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Discuss new pre-award issues
Event Title: Discuss new pre-award issues Date: Wednesday, 09 January 2019, 05:00pm to 06:00pm CET Description Dear all, There will be two topics to be discussed in the pre-award subcommittee. 1- Need: add new types in the TenderingCriterionProperty ABIE. ExpectedURL, ExpectedIndicator) The ResponseValue ABIE that was developed in the post award context caters for all the generic needs of the TenderingCriterionProperty. There is an opportunity to streamline pre and post award. Yet the backward compatibility constraint prevent from deprecating the TenderingCriterionProperty. Do we wish to add an ExpectedResponse component of type ResponseValue while creating confusion as some information will have more information carriers by doing so? 2- Need : allow for expressing multiple CPV codes as one requirement Increasing the cardinality ExpectedCode or ResponseCode from 0..1 to 0..n would support this requirement. Yet there seem to be a NDR rule that prevents to add a cardinality n on a BBIE. This is because attributes apply to the information itself and would there be more elements in one BBIE it would not be possible to qualify those with different attributes. Do we wish to break this rule for the sake of managing CPV codes requirements or which other option do we have? KRs, Cécile GUASCH
RSVP Owner: Cecile Guasch Group: UBL Pre-Award Procurement Subcommittee Sharing: This event is shared with the OASIS Open (General Membership), and General Public groups. Public Event Link |
Attachment:
ical_48358.ics
Description: application/ics
BEGIN:VCALENDAR CALSCALE:GREGORIAN METHOD:REQUEST VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:Europe/Paris BEGIN:STANDARD DTSTART:20001029T030000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 TZNAME:CET TZOFFSETFROM:+0200 TZOFFSETTO:+0100 END:STANDARD BEGIN:DAYLIGHT DTSTART:20000326T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3 TZNAME:CEST TZOFFSETFROM:+0100 TZOFFSETTO:+0200 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT STATUS:CONFIRMED TRANSP:OPAQUE DTSTAMP:20190108T165031Z DTSTART;VALUE=DATE-TIME;TZID=Europe/Paris:20190109T170000 DTEND;VALUE=DATE-TIME;TZID=Europe/Paris:20190109T180000 SEQUENCE:0 SUMMARY:Discuss new pre-award issues LAST-MODIFIED:20190108T165031Z ORGANIZER:workgroup_mailer@lists.oasis-open.org ATTENDEE;CUTYPE=GROUP:MAILTO:ubl-pre-award@lists.oasis-open.org DESCRIPTION:Dear all\,\n\nThere will be two topics to be discussed in th e pre-award subcommittee.\n\n1- Need: add new types in the T enderingCriterionProperty ABIE. ExpectedURL\, ExpectedIndica tor)\n\nThe ResponseValue ABIE that was developed in the pos t award context caters for all the generic needs of the Tend eringCriterionProperty.\n\nThere is an opportunity to stream line pre and post award.\n\nYet the backward compatibility c onstraint prevent from deprecating the TenderingCriterionPro perty.\n\nDo we wish to add an ExpectedResponse component of type ResponseValue while creating confusion as some informa tion will have more information carriers by doing so?\n\n2- Need : allow for expressing multiple CPV codes as one requir ement \n\nIncreasing the cardinality ExpectedCode or Respon seCode from 0..1 to 0..n would support this requirement.\n\n Yet there seem to be a NDR rule that prevents to add a cardi nality n on a BBIE. This is because attributes apply to the information itself and would there be more elements in one B BIE it would not be possible to qualify those with different attributes.\n\nDo we wish to break this rule for the sake o f managing CPV codes requirements or which other option do w e have?\n\nKRs\,\n\nCé\;cile GUASCH\n\n \n\nGroup: UBL Pre-Award Procurement Subcommittee\nCreator: Cecile Guasch URL:https://www.oasis-open.org/apps/org/workgroup/ubl-pre-award/event.php?event_id=48358 UID:https://www.oasis-open.org/apps/org/workgroup/ubl-pre-award/event.php?event_id=48358 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM END:VEVENT END:VCALENDAR
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]