Replies: 3 comments 4 replies
-
Beta Was this translation helpful? Give feedback.
-
Hello I'm reviewing this table and I just want to confirm a few things. Are the URIs listed here the corresponding URIs for the columns in the table?
Could you kindly update these names to precise prefixed URIs for the corresponding concepts? Also, I came across a property named preparesForPotentianProcurementObject. Is "Potentian" a typo? Should it be "Potential"? If available, could you also point me to any documentation that explains what is the purpose of having different verbs? Lastly, do all of these verbs inherit from epo:refersTo? Many thanks ! |
Beta Was this translation helpful? Give feedback.
-
I'm having trouble interpreting this table. It shows that for the tuple |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When mapping eForms to ePO, we encountered several situations where it was not clear, or not easy to define, when to use "announces" vs. "refersTo" properties to link procedure, lot, planned part, various roles and review objects to different type of notices. The problem had a reasonably clear solution when we dealt with only competition and result notices, but it got very difficult when we had to adopt our mappings to handle correctly the use of these properties for all these 7 notice types:
We need help to specify precisely the correct property to use in case of all the above notice types, for the following field
Beta Was this translation helpful? Give feedback.
All reactions