[billconan]

no

<div class="abstract-container">

<div class="abstract">

<pre><code> abstract text ... </code></pre>

</div>

<div class="author-list">

<ol>

<li>author one</li>

<li>author two</li>

<ol>

</div>

should be just:

[abstract]

abstract text

[authors]

author one | email | affiliation

author two | email | affiliation

[afavour]

Sounds like XML and XSL would be a great fit here. Shame it’s being deprecated.

But you could still use HTML. Elements with a dash in are reserved for custom elements (that is, a new standardised element will never take that name) so you could do:

    <paper-author-list>
      <paper-author />
    </paper-author-list>

And it would be valid HTML. Then you’d style it with CSS, with

    paper-author {
      display: list-item;
    }

And so on.

[bawolff]

Nothing is stopping you from using server side XSL. I personally dont think its a great fit, but people need to stop acting like xsl has been wiped from the face of the earth.

[xworld21]

Indeed, LaTeXML (the software used by arXiv) converts LaTeX to a semantic XML document which is turned to HTML using primarily XSLT!

[panzi]

There is <article> <section> <figure> <legend>, but yes, <abstract> and <authors> is missing as such. But there are meta tags for such things. Then there is RDF and Thing. Not quite the same, I know, but it's not completely useless.

[kevindamm]

and you could shim these gaps with custom components, hypothetically