-
Notifications
You must be signed in to change notification settings - Fork 18
OP-TED ePO Ideas Discussions
Pinned Discussions
Sort by:
Latest activity
Categories, most helpful, and community links
Categories
Community links
💡 Ideas Discussions
Share ideas for new features
-
You must be logged in to vote 💡 Glossary - Catalogue Request
type: feature requestsomething requested to be implemented in a future release module: eCatalogueeCatalogue -
You must be logged in to vote 💡 Catalogue Response
module: eCatalogueeCatalogue type: use caseUse Case (User story) -
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 💡 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 💡 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 💡 -
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 -
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 requestFunctionalProperty
annotationssomething 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, rov
something 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 💡 hasLegalFormType
should 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, rangeIncludes
something 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 💡 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 💡 GLOSSARY - Bargain Purchase Value
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 💡 Level of details of the class "Value"
type: feature requestsomething requested to be implemented in a future release module: eInvoicingeInvoicing act: for internal discussionit needs to be discussed within the team