Waiting on the ticket to move to the current Sprint (parser TXXX).

Apart from migrating "Section" logic, this ticket has more sub-tasks. I need clarification on specific coding tasks:

• Is there a technical part to "First of all: investigate whether we need to include html (links, references) into sections or just headings and plain text."?
• The dependency with "Credibility work", should this ticket add parsed references to structured-contents API, or is underway by Prabhat in other tickets?
• What is the scope of work with "Investigate schema options"? What options are in and out of scope? What is the customer deliverable from this sub-task?

@prabhat for the "credibility work", there is a bit of overlap here with parsing Wikipedia reference links. Shall we do the reference parsing in this ticket? If we add the reference parsing to parser.go we can re-use it in the structured-contents API.

@ROdonnell-WMF do you have your answers already?

THe outstanding question is the credibility signals use of Reference links. Should we extract HTML references in the ticket or leave it for another ticket? The Section demo code does have reference extraction, so it's not much work to include it in the code migration ticket

We talked to @SDelbecque-WMF yesterday, my understanding is: if its low effort to add it, let's do it!

OK, I will include it

@SDelbecque-WMF can you please update the description with the OKR thins one belongs to? Thanks!