JbPasquier
commented
8 months ago I missed this one. Now that I have a clearer idea on what is a Supporting Evidence, what is an Assurance and what is a Certification, I can see an issue with this.
We can't mix content with different properties in the same display. This is a framework limitation based on the specification. You can see it like trying to put a plane in a cardboard box made for trains.
We should have handled this one beforehand the implementation. It was unclear to us that those two things where related.
How can we implement that now?
- Quick one, we could have a third entrypoint on a producer, with the mixed content merged in.
- Or, cleanest one would be to merge certification and supporting evidence while keeping their separate @type. But that'll require a lot of work to re-do the component with this new behaviour.
- Or, easiest one would be to split it in two on the display. You'll always have supporting evidence on top then certifications on the bottom.
- Or, maybe certifications aren't plane, maybe they're trains too?
It's still unclear to me what's the relation between a certification and a supporting evidence. Shouldn't a Certification be a Supporting Evidence with an ofn:Classification - ofn:label of Certification?
Could this work?
Edit: Let me try another way with a custom implementation on front-end side. We may want to rethink this later if ~10x more producers enter the ring.
Edit 2 : Looks good. Forget about what I said at first. While it's a bit tricky, my custom implementation does the trick for your use case without any modification on your api model. I'll aim to deliver it today.
kirstenalarsen
Kirsten has added a certification to Pukawidgee, has been confirmed, so there is now test data