(missing)
(missing)
(missing)
Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Marc Nieper-Wißkirchen (06 Mar 2019 10:12 UTC)
Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Ciprian Dorin Craciun (07 Mar 2019 20:18 UTC)

Re: Proposal to add HTML class attributes to SRFIs to aid machine-parsing Ciprian Dorin Craciun 07 Mar 2019 20:17 UTC

On Thu, Mar 7, 2019 at 12:01 PM Ciprian Dorin Craciun
<xxxxxx@gmail.com> wrote:
> I'll try to work on SRFI 1 today.  (I have a few ideas where I want to
> take a different approach.)

I've made a fork of SRFI-1 and started chopping and transforming the
HTML into XHTML, at the same time eliminating some "boilerplate"
elements (to focus only on the actual text), and changing some HTML.
The changes can be seen at:

  https://github.com/scheme-requests-for-implementation/srfi-1/compare/master...cipriancraciun:master

If one would open the HTML file (but you must clone first the
repository), it opens with a CSS that highlights all HTML markup.

As it stands I have tried to eliminate as much HTML as possible (which
was used mainly for formatting purposes).  In the next days I'll take
a look at how I can change the annotations to make it more maleable to
exports and indexing.

Just a note on my approach:  my focus is mainly on how we can use
XHTML to obtain the following:
* easy indexing and back-referencing of the elements;
* easy export into other formats (like Markdown), thus the used
(X)HTML elements should be kept to a minimum;
* easy splitting of the text into sections and definitions so that one
can programatically extract only that section;

Because I still maintain my position that trying to extract more than
basic metadata about the procedures described within, I'll simplify
and remove extra classes or elements (if they exist).

Ciprian.