OP-TED ePO Discussions
Pinned Discussions
Discussions
-
You must be logged in to vote Suggestions for Release-notes
module: noneno module in particular because the issue is of technical or documentation nature -
You must be logged in to vote allow multiple legal names
type: feature requestsomething requested to be implemented in a future release module: noneno module in particular because the issue is of technical or documentation nature -
You must be logged in to vote -
You must be logged in to vote Request of new code in "Reserved procurement" controlled vocabulary (PPDS)
aux: ppdsit is related to the PPDS project -
You must be logged in to vote instead of busy term definitions use structured metadata fields
type: feature requestsomething requested to be implemented in a future release act: for closingit can be closed but an additional confirmation is needed act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote Identification of Out of Directive contracts in the ePO
type: questionsomething needs clarified, refined or decided -
You must be logged in to vote Computed information from previous notice information
type: questionsomething needs clarified, refined or decided module: ePO coreePO core act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote -
You must be logged in to vote Rename "Purchase Contract" as "Specific Contract"
type: feature requestsomething requested to be implemented in a future release module: eContracteContract act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote Questions on Durations for Lot and Contract To Be Checked
type: questionsomething needs clarified, refined or decided module: ePO coreePO core act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote consider using W3C CUBE patterns for representing counts
type: feature requestsomething requested to be implemented in a future release act: for internal discussionit needs to be discussed within the team module: noneno module in particular because the issue is of technical or documentation nature -
You must be logged in to vote add more
type: feature requestFunctionalPropertyannotationssomething requested to be implemented in a future release act: for implementationit can be implemented and closed, all is clear module: noneno module in particular because the issue is of technical or documentation nature -
You must be logged in to vote reuse props from
type: feature requestorg, rovsomething requested to be implemented in a future release module: ePO coreePO core act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote How to express company Status?
type: feature requestsomething requested to be implemented in a future release module: ePO coreePO core act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote
type: feature requesthasLegalFormTypeshould be concept not literalsomething requested to be implemented in a future release module: ePO coreePO core act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote add more subprops ( epo:leadBy<epo:hasMember)
type: feature requestsomething requested to be implemented in a future release module: noneno module in particular because the issue is of technical or documentation nature -
You must be logged in to vote consider using
type: feature requestschema:domainIncludes, rangeIncludessomething requested to be implemented in a future release act: for internal discussionit needs to be discussed within the team module: noneno module in particular because the issue is of technical or documentation nature -
You must be logged in to vote Subunits of an Organisation
type: feature requestsomething requested to be implemented in a future release module: ePO coreePO core -
You must be logged in to vote Other means of proof than label to comply to requirements
module: ePO coreePO core type: use caseUse Case (User story) -
You must be logged in to vote v3.0 inverse of properties needed to identify contracts from one single tender
type: feature requestsomething requested to be implemented in a future release module: ePO coreePO core act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote Social Procurement Definition
type: feature requestsomething requested to be implemented in a future release module: ePO coreePO core act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote Predicate harmonisation
type: feature requestsomething requested to be implemented in a future release module: ePO coreePO core -
You must be logged in to vote Don't use too many namespaces
type: feature requestsomething requested to be implemented in a future release act: for closingit can be closed but an additional confirmation is needed act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote questions about Amount and Value
type: questionsomething needs clarified, refined or decided module: ePO coreePO core act: for internal discussionit needs to be discussed within the team -
You must be logged in to vote How are the attributes of class Value used depending of the various predicates?
type: questionsomething needs clarified, refined or decided module: ePO coreePO core
