OP-TED ePO Discussions
Pinned Discussions
Discussions
-
You must be logged in to vote Should the Ontology Include an eforms SDK version concept
aux: mappingit is related to the TED-SWS mappings project type: questionsomething needs clarified, refined or decided aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote eforms BT-133 It might be a good idea to look into whether there are two options full address and url
aux: mappingit is related to the TED-SWS mappings project aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote every term must have a definition
type: feature requestsomething requested to be implemented in a future release module: ePO coreePO core -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote Remove unnecessary model-owl files from ePO repo
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 how to deal with Unpublished fields
aux: mappingit is related to the TED-SWS mappings project module: ePO coreePO core act: for WG discussionit needs to be discussed within the Working Group aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote widoco for dereferencing
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 Problem with BT-748
aux: mappingit is related to the TED-SWS mappings project module: ePO coreePO core act: for WG discussionit needs to be discussed within the Working Group aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote OPT concepts that should not be used anymore
aux: mappingit is related to the TED-SWS mappings project type: questionsomething needs clarified, refined or decided module: ePO coreePO core aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote Connect all dates fields to the correct ePO concepts
aux: mappingit is related to the TED-SWS mappings project module: ePO coreePO core act: for internal discussionit needs to be discussed within the team aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote BT-133 Public Opening Place is too vague.
aux: mappingit is related to the TED-SWS mappings project module: ePO coreePO core aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote Tenderer, Winner, Contractor, Seller what is the relation between these different concepts?
type: questionsomething needs clarified, refined or decided module: ePO coreePO core -
You must be logged in to vote How to model Tenderers consisting of multiple Organisations?
module: ePO coreePO core module: eSubmissioneSubmission aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote Investigate redundancy regarding criterion and Reserved-procurement authority tables
module: eSubmissioneSubmission aux: alignmentalignment between ESPD, eForms and ePO -
You must be logged in to vote -
You must be logged in to vote Unable to specify or represent an organisation part/department since ePO 4.0-rc.2
aux: mappingit is related to the TED-SWS mappings project type: feature requestsomething requested to be implemented in a future release module: ePO coreePO core -
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
