Social network Qualifio

We would need Arc to natively integrate the Qualifio social network. This social network provides oembed service as requested.

https://oembed.com/

https://api.qualif.io/v1/campaignfeed/oembed?format=json&url=https://prisanoticias.qualifioapp.com/20/0EE00B87-9AE2-45D7-B082-D9A6ADD0F37F/v1.cfm?id=0EE00B87-9AE2-45D7-B082-D9A6ADD0F37F&pdomain=https://as.com

Which is generated from: https://prisanoticias.qualifioapp.com/20/0EE00B87-9AE2-45D7-B082-D9A6ADD0F37F/v1.cfm?id=0EE00B87-9AE2-45D7-B082-D9A6ADD0F37F&pdomain=https://as.com

In our current editor, Journalist paste this URL from the Qualifio platform and the embed HTML that the Qualifio tool provides (attached screenshot)

Diario As Example: https://as.com/futbol/2020/07/01/primera/1593592608_379632.html

Stories right now have a proper data structure where the Qualifio extensions are typed correctly as we need to ensure the following use cases:

Render correctly the Qualifio embed feature in the story
Let third party content consumers to know what's a Qualifio extension in the body of an article to make a native integration like the iOS and Android APP, RSS Feeds, JSON Feeds consumed by Diario AS partners.

As we are going to migrate stories into ARC platform, we will need to be sure which structure are these extensions going to have in the ANS Model of the story. At the same time, when Composer starts working, the journalist will have to be able to integrate Qualifio embeds in the story. Both data structures should be the same to ensure the Code does not have flaws of migration concerns.

To ensure the data structure is properly done in the Migration we will need to know how this information is going to be introduced in Composer. We have the following options:

Use plain HTML: Cons is mainly we won't be able to identify what's a Plain HTML and what's a Qualifio embed to ensure all the use cases (AMP integration, APPs native integration).
Use oEmbed integration in Composer: This is something the Composer team must implement as Composer does not understand the oEmbed integration for Qualifio although Qualifio provides that integration.
Use custom embed: This would be the integration chosen if the Composer team cannot provide a solution through oEmbed in the short term (before migration).